How does Oracle determine which objects in a logical standby should be protected by Data Guard
edited Mar 14, 2010 1:41AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 3 commentsAnswered
After I issue "alter database guard standby", how does Oracle determine which objects should be protected by Data Guard (yielding ORA-16224 in response to DDL versus those that should not be protected by Data Guard and can be altered without ORA-16224?
I have a dev, QA, and production instance of a logical standby, using 10.2.0.4. In all three standby databases, I manually created a schema that is not part of the replica maintained by SQL Apply. In two of the database, I can split partitions in that schema at will. In the production database, splitting a partition yields ORA-16224. The guard mode is STANDBY in all three. Where should I look for differences? Why did Data Guard decide to protect objects in the schema that I created outside of Logical Standby.
I have a dev, QA, and production instance of a logical standby, using 10.2.0.4. In all three standby databases, I manually created a schema that is not part of the replica maintained by SQL Apply. In two of the database, I can split partitions in that schema at will. In the production database, splitting a partition yields ORA-16224. The guard mode is STANDBY in all three. Where should I look for differences? Why did Data Guard decide to protect objects in the schema that I created outside of Logical Standby.
0