Last updated on MAY 24, 2011
Applies to:Oracle Server - Enterprise Edition - Version: 188.8.131.52
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
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
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms