This content has been marked as final. Show 10 replies
Whats the errors that show to you?
REAL TIME QUERY is only active with Active Data Guard. Since you are opening the Database and make the RTA active.
If you do not want to use REAL TIME QUERY, you should keep your database in MOUNT state.
Do you need to start your database with STARTUP command? Why don't use only STARTUP MOUNT? Is this Standby configured in SINGLE or RAC?
it is for standalone database (not RAC)
yes, users can start the database with mount option, but they have to keep in mind that they do not have to issue a "STARTUP",
so it is a production rule that oracle doesn't handle.
Second, it will give a little more complexity in startup scripts (first mount, identify the role, and then open if it is a primary.
In 10gr2 just startup in all cases ....
that's why i'd like to know if there is a possibility to permanently disable REAL TIME APPLY ...
Important thing is "Active Data Guard" is an Extra Option (Means Licensed Version it is not free).
Keep the database in 'Recovery Managed Mode'. I mean normal Oracle Data Guard becos this option is free feature of Oracle EE
this is the reason why, i'd like to permanently deactivate REAL TIME APPLY ....
I don't believe Real Time Apply will work if you don't have Standby Redo Logs.
Will double check my notes.
Yes that would work.
Data Guard Real-Time Apply FAQ [ID 828274.1]
Edited by: mseberg on Dec 11, 2012 10:53 AM
If you disable RTA you'll need to manually recover the standby db. Do you really need to allow users to STARTUP the STANDBY DB?
I mean, this is an adm taks, for DBAs.. correct?
Can you help me understand what you mean by:
"If you disable RTA you'll need to manually recover the standby db"
yes ... "dba" is what i call user ....
so i finally understand, that it is not possible to disable properly RTA.
and we have to live with ...
ultimately if the users aka dba has the ability to start the database. Restrict them to a sudo command by set something in place to only allow the database to start up in read only or edit the configuration on the standby dgmgrl that way if it is started the the redo apply is off.
worst case educate those that keep starting it :)
DGMGRL> edit database <name> set state=apply-off;
sql> alter database open read only;