On Standby, DBV Shows Pages Failing with Check Code 6056
(Doc ID 1523623.1)
Last updated on OCTOBER 08, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.2 [Release 11.2 to 12.1]Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
On 11.2.0.2 and 11.2.0.3, dbverify reports the a logical SCN inconsistency with error like:
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
Other symptoms:
- No data corruption found in the block <Block#>.
- Running dbverify a few times against all Standby datafiles, the quantity of errors is increasing.
- There errors are only raised by run of dbverify against Standby datafiles.
- The Primary DB is OK, and dbv (not patched) shows no errors.
Changes
<Patch 13350245> has been applied and did not help to prevent these errors.
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 |