This content has been marked as final. Show 6 replies
Status Level: Newbie
Registered: Dec 20, 2012
Total Posts: 397
Total Questions: 57 (32 unresolved)
How do I ask a question on the forums?
SQL and PL/SQL FAQ
How do I know if a certain database has a standby db created?Check init parameter, LOG_ARCHIVE_CONFIG.
How do I break-up their links/connection if there is, so that the PROD will go free and will standalone?
If set, You have standby database as config name.
And you unset this parameter then log transfer will stop.
Also You have to check LOG_ARCHIVE_DEST_n parameter.
They have PROD and Standby database as mentioned verbally. Ii was mentioned also that standby was not working anymore or has failed or has been put to active accidentally.When standby is behind and inconsistency in recovery, then you cannot put database in open(read-only) + Recovery.
In this regard, is the PROD still have dependencies on the "failed" standby Db? I mean is it holding back some files for the benefit of the standby Db?In maximum performance, there will be no dependency on standby database, of course it tries to do send redo/archives from primary to the all standby databases, In case of Maximum protection/availability then primary database is depended on the standby database, Because transaction has to commit at least one standby database then it will be applicable on primary database, BTW there is some differences in maximum protection and availability, I mentioned in brief.
How do I know if a certain database has a standby db created? How do I break-up the tie or their links/connection if there is, so that the PROD will go free and will standalone?You have to find out, when the last sequence applied on standby. you can check by below query
SQL> select max(sequence#) from v$archived_log where applied='YES';
Based on that sequence number, check the completion_time on primary database. Lets suppose you have all the archives from the above sequence number to till sequence, Then you are safe. By configuring properly you can fix.
Lets suppose, you do not have any archives or even in backups, you have to perform incremental roll forward technique you can check this link from my blog
If the differences between primary and standby is huge, Then you can also consider the option to rebuild the standby database again.
check v$database,v$archived_log,v$log_history views...you may get the details of standby db info......
please check ....below metalink notes for more info
How to remove a Data Guard Configuration from Primary Database [ID 733794.1]
Edited by: dbc001 on Mar 21, 2013 9:50 AM