metalink上的解释如下：
Errors
ORA 600 "internal error code, arguments: [%s],[%s],[%s], [%s], [%s],
[KCRRLCK.1]
Symptoms
Failover fails with [ORA-600 [kcrrlck.1]
Alert.log
======
Alter database recover managed standby database finish skip standby logfile
Thu Feb 5 16:54:25 2004
Database not recovered through End-Of-REDO
Attempt to do a Terminal Incomplete Recovery
Media Recovery Start: Managed Standby Recovery
Starting datafile 1 recovery in thread 1 sequence 31
Datafile 1: '/dev/vx/rdsk/aotsdrdg/AOTSDRSYSTEM1'
Starting datafile 2 recovery in thread 1 sequence 31
Datafile 2: '/dev/vx/rdsk/aotsdrdg/AOTSDRUNDO1'
Starting datafile 3 recovery in thread 1 sequence 31
.......
.......
Media Recovery Log
Media Recovery Waiting for thread 1 seq# 31
Terminal Incomplete Recovery: UNTIL CHANGE 70021
Terminal Incomplete Recovery: End-Of-Redo log allocation
Terminal Incomplete Recovery: log 101 reserved for thread 1 seq# 31
Thu Feb 5 16:54:40 2004
Errors in file /opt/oracle/AOTSDR/admin/udump/aotsdr_ora_16260.trc:
ORA-00600: internal error code, arguments: [kcrrlck.1], [0], [0], [0], [], [], [], []
Recovery interrupted.
Media Recovery failed with error 600
Cause
This error would generally be returned when you are testing Failover. This is because the RFS process on the standby has locks on the standby redo logs.
Fix
You need to either shutdown the Primary or bounce the standby to release the RFS lock on the standby redo log.
References |
