If you cannot recover data by yourself, ask Parnassusdata, the professional ORACLE database recovery team for help.

Parnassusdata Software Database Recovery Team

Service Hotline: +86 13764045638 E-mail: [email protected]

SYMPTOMS

o Create controlfile fails with the following errors:

CREATE CONTROLFILE REUSE SET DATABASE ... RESETLOGS FORCE LOGGING

ARCHIVELOG

*

ERROR at line 1:

ORA-1503: CREATE CONTROLFILE failed

ORA-600: internal error code, arguments: [kccscf_1], [9], [65732], [65535], [], [], [], []

o Database duplication using RMAN fails with the following errors

ORA-00600: internal error code, arguments: [kccscf_1], [9], [74752], [65535], [], [], [], []

ORA-1503 signalled during: CREATE CONTROLFILE REUSE SET DATABASE ... RESETLOGS

CHANGES

The problem occurs if compatible parameter is set to 10.2 or higher

CAUSE

This is unpublished bug 4877360
Abstract: APPSST SRV 10G :ORA-600: INTERNAL ERROR CODE, ARGUMENTS: [KCCSCF_1], [9], [65732], [65535]

Problem is related to parameter MAXLOGHISTORY specified in create controlfile command. It’s complaining that maximum should be 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.

For some platforms a backport fix is available. Please check availability of Patch 4877360 on MOS.

Oracle ORA-600 [kccscf_1] ORA-00600 [kccscf_1]