##########################
## Error
##########################
ORA-00600: internal error code, arguments: [kccscf_1], [9], [72704], [65535], [], [], [], []
### Full Error
check rman_dup_proddb_uatdb_08062013.log for RMAN Duplication Log.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 08/06/2013 23:26:29
RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-00600: internal error code, arguments: [kccscf_1], [9], [72704], [65535], [], [], [], []
##########################
# Error Occurred
##########################
Error occured while RMAN Duplication is performed, once duplication is done and when oracle tried to create controlfile in 10.2.0.3.0 version of database
##########################
## Command Executed
##########################
In sqlplus,
Create Controlfile Statment,
##########################
## Issue Description.
##########################
### 10.2.0.3.0
Error occurred RMAN duplication of create controlfile statement in 10.2.0.3.0 version.
Problem is related to parameter MAXLOGHISTORY specified in create controlfile command. It's complaining that maximum should be 65535. whereas in the create controlfile statement its 72704. due to which its failing.
This seems to be a Bug
Bug:
-------
This is unpublished bug 4877360
Abstract: APPSST SRV 10G :ORA-600: INTERNAL ERROR CODE, ARGUMENTS: [KCCSCF_1], [9], [65732], [65535]
##########################
## Solution
##########################
A possible workaround is to manually recreate the control file, and change the maxloghistory set to 65535 or lower in the script.
The bug is fixed in 10.2.0.4 and 11.1.0.6 versions.
No comments:
Post a Comment