ORA:1578 ORA-26040 On Active Data Guard
(Doc ID 1320878.1)
Last updated on FEBRUARY 10, 2019
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 11.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
FULL TABLE SCAN fails complaining about a block on ADG due to a NOLOGGING
operation on the primary.
Flashback has been on for both databases
A table TAB_A is created in NOLOGGING. Data is loaded into the table on primary.
Blocks are marked as NOLOGGING in the STANDBY . This is the expected behavior
The table TAB_A is dropped.
A new object is created, TAB_B, the new table is using LOGGING option
Data is loaded into the newly table.
While selecting from the new table TAB_B on ADG, the process can fail with
The error doesn't reproduce on STANDBY after converting it to PRIMARY
DATABASE is not set in FORCE LOGGING. A table is set with LOGGING
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