Oracle ORA-600 [2663]

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

Parnassusdata Software Database Recovery Team

Service Hotline:  +86 13764045638 E-mail: service@parnassusdata.com

ERROR:

Format: ORA-600 [2663] [a] [b] [c] [d]

VERSIONS:

versions 10.1 to 11.1

DESCRIPTION:

A data block SCN is ahead of the current SCN.

The ORA-600 [2663] occurs when an SCN is compared to the dependent SCN stored in a UGA variable.

If the SCN is less than the dependent SCN then we signal the ORA-600 [2663] internal error.

ARGUMENTS:

Arg [a]  Current SCN WRAP Arg [b]  Current SCN BASE Arg [c] dependent SCN WRAP Arg [d]  dependent SCN BASE

FUNCTIONALITY:

Kernel Cache Redo File Redo Generation

IMPACT:

INSTANCE FAILURE

POSSIBLE PHYSICAL CORRUPTION

SUGGESTIONS:

There are different situations where ORA-600 [2663] can be raised.

It can be raised on startup or duing database operation.

If not using RAC, Real Application Clusters,, check that 2 instances have not mounted the same database.

Check for SMON traces and have the alert.log and trace files ready to send to support.

Check the SCN difference [argument d]-[argument b].

If the SCNs in the error are very close, then try to shutdown and startup the instance several times.

In some situations, the SCN increment during startup may permit the database to open. Keep track of the number of times you attempted a startup.

If the Known Issues section below does not help in terms of identifying

a solution, please submit the trace files and alert.log to Oracle Support Services for further analysis.

Known Issues: