Re: Database Link to check Standby Database

Mark thanks a lot for your response.
Sorry for not mentioning: The release is 8.1.7.4

I have two seperate servers PROD and STANDBY so I gues u mean Physical standby.

What I like to achieve is to check the production & Standby server to check both squence numbers of the last create and applied redo log files. I want to do this " from " the production server by comparing the sequence numbers of both servers. This has to be done autmatic.

What will happen if I create a DB link to a Standby server. Because the redo log with the create DB link command wil also be applied on the standby server.  

Thanks,

Ton

n Mon, 23 Aug 2004 14:36:43 GMT, Mark Bole <makbo_at_pacbell.net> wrote:

>Ton wrote:
>> I want to to create a Database Link from the production database to
>> its Standby database.
>>
>> Purpose: Checking " V$LOG_HISTORY " on the Production and Standby
>> server to idenity if all available production redo log files have been
>> applied on the Standby datase.
>>
>> Questions:
>>
>> 1. Is it sensible to create and drop the Database Link connection
>> everytime I run the script?
>>
>> 2. What will be consequences for the Standby server by creating a DB
>> link by the Production server?
>> In other words: During applying the redo log files from the production
>> to the standby database will the Standby database also try to create
>> database link (to itself)?
>>
>> 3. Is there a handier solution to check automatically if the both
>> (Prod. & Standby) are in sequence?
>>
>> Thanks
>
>You didn't mention a version. Are you asking about a physical standby
>or a logical standby?
>
>In a physical standby, the Dataguard documentation specifically mentions
>V$ARCHIVE_DEST_STATUS as a way to determine managed recovery progress
>and gives a sample query. This view is (should be) identical on both the
>primary and the standby, so you could just check it on the primary and
>forget the link.
>
>The documentation gives several other examples using V$ARCHIVED_LOG and
>V$LOG_HISTORY as well, in case you are doing manual recovery. You don't
>need a DB link for this, you could connect directly from SQL*Plus or
>some other client -- but link or otherwise, only if the standby is
>opened temporarily in read-only mode (which is the only way to open a
>physical standby without destroying its standby status).
>
>A different view (dba_logstdby_progress) exists for the same purpose in
>a logical standby. With a logical standby database, the documentation
>calls for creating various links between the primary and standby in case
>a table needs to be re-instantiated or in case you are doing a
>switchover for disaster recovery (the latter is considered to be
>somewhat buggy and unreliable for version 9iR2).
>
>--Mark Bole
Received on Tue Aug 24 2004 - 13:31:31 CDT