Dropped Object Still Accessible In RAC ADG Non-apply Instance
(Doc ID 2953703.1)
Last updated on JUNE 06, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 19.16.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 19.16.0.0.0 version, Oracle Data Guard
Dropped object still accessible in RAC ADG non-apply instance
In an Active Dataguard environment ( Primary RAC and Standby RAC ), we follow the next sequence :
- create table in primary and insert a few rows
- a select count(1) to the table from 2 Standby RAC instances ( the one applying the redo and the one that doesn't ), gives the correct number of rows.
- drop the table in the primary
- run the select count(1) in the Standby instance which is applying redo, we get an error because the object does not exist ( ORA-00942 )
SQL> select * from <owner>.<table_name>;
select * from <owner>.<table_name>
*
ERROR at line 1:
ORA-00942: table or view does not exist
SQL>
- run the select count(1) in the Standby instance which is not applying redo, we get a "0", not an error :
SQL> select count(1) from <owner>.<table_name>;
COUNT(1)
----------
0
We have traced the select, and noticed that the failing instance still looks for the old object_id of the dropped object.
Customer wants the Active Dataguard feature to work consistently as otherwise it is not usable for their purpose.
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 |
Cause |
Solution |
References |