Oracle ORA-600 [2663]

Posted by PDSERVICE on Nov 15, 2015 In

Oracle ORA-600 [2663]

Note: For additional ORA-600 related information please read Note:146580.1

PURPOSE:

This article discusses the internal error "ORA-600 [2663]", what

it means and possible actions. The information here is only applicable

to the versions listed and is provided only for guidance.

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:

NB Bug Fixed Description

+ 8895202 11.2.0.2, 12.1.0.1 ORA-1555 / ORA-600 [ktbdchk1: bad dscn] ORA-600 [2663] in Physical Standby after switch-over

Check Note 30681.1, EVENT:ADJUST_SCN

You are here

Oracle ORA-600 [2663]

Oracle ORA-600 [2663]