ORA-1555 Zero Duration/ ORA-600 [ktbdchk1: bad dscn] / ORA-600 [2663] / after Physical Standby switchover
(Doc ID 1577824.1)
Last updated on JULY 05, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.1.0.7 to 11.2.0.1 [Release 11.1 to 11.2]Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
Symptoms
The Following Errors May Occur in a Physical Standby database after a switchover :
ORA-1555 With Query Duration=0
ORA-600 [ktbdchk1: bad dscn]
ORA-600 [2663]
ORA-600 [ktbdchk1: bad dscn]
ORA-600 [2663]
Sometimes the following errors are also reported
ORA-00700: soft internal error, arguments: [EVENT_CREATED_INCIDENT], [1555]
Also With the fix of Bug 7517208 which is included by default in 10.2.0.5 Patch Set and versions >= 11.2.0.1 (Base Release), the DBVERIFY utility reports this SCN inconsistency with error:
itl[<itl_id>] has higher commit scn(aaaa.bbbb) than block scn (xxxx.yyyy)
Page <Block#> failed with check code 6056
Page <Block#> failed with check code 6056
There is NO DATA CORRUPTION in the block , The DBVERIFY utility falsely reports SCN corruption.
Changes
Physical Standby switchover
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |