Home » Server Options » Data Guard » Apply archivedlog log in Standby
Apply archivedlog log in Standby [message #214782] Thu, 18 January 2007 01:14 Go to next message
enkhbold
Messages: 36
Registered: July 2005
Location: Mongolia
Member

Hi all
please help me explaining in in below.

Background:-
I have primary and standby sites. both sites have 2 db nodes with storage.
Archived logs transfered to Standby from Primary. it is fine.
because, I have checked sequence# from v$archived_log. From this view, log is transfered.

Problem:-
In standby, i have run select sequence#, archived, applied from v$archived_log order by sequence#.
But in result, some records applied value is "NO".
How i can change it to "YES"?

Thanks,
Re: Apply archivedlog log in Standby [message #214886 is a reply to message #214782] Thu, 18 January 2007 06:27 Go to previous messageGo to next message
email.sandeepnaik
Messages: 121
Registered: August 2006
Senior Member
archive log which are not applied yet on standby will appear as NO. Once they are applied they should be reflected as YES.

Sandeep
Re: Apply archivedlog log in Standby [message #215020 is a reply to message #214886] Fri, 19 January 2007 00:17 Go to previous messageGo to next message
enkhbold
Messages: 36
Registered: July 2005
Location: Mongolia
Member

Thanks Sandeep

I have checked v$sequence table in both sites.
Please advise me, what is mean.

In Primary
Seq# First_time Next_time Archived Applied Standby_dest
1906 18-Jan-2007 18-Jan-2007 YES NO YES
1906 18-Jan-2007 18-Jan-2007 YES NO NO
1907 18-Jan-2007 18-Jan-2007 YES NO YES
1907 18-Jan-2007 18-Jan-2007 YES NO NO
1908 18-Jan-2007 18-Jan-2007 YES NO YES
1908 18-Jan-2007 18-Jan-2007 YES NO NO
1909 18-Jan-2007 18-Jan-2007 YES NO YES
1909 18-Jan-2007 18-Jan-2007 YES NO NO

In Standby
Seq# First_time Next_time Archived Applied Standby_dest
1906 18-Jan-2007 18-Jan-2007 YES NO NO
1907 18-Jan-2007 18-Jan-2007 YES NO NO
1908 18-Jan-2007 18-Jan-2007 YES NO NO
1909 18-Jan-2007 18-Jan-2007 YES NO NO

Re: Apply archivedlog log in Standby [message #215113 is a reply to message #214782] Fri, 19 January 2007 06:27 Go to previous messageGo to next message
email.sandeepnaik
Messages: 121
Registered: August 2006
Senior Member
v$sequence is only available when database is in open mode.

Your standby should have been in mount mode.

Have you followed all steps to create standby database as per oracle documentation?

Sandeep
Re: Apply archivedlog log in Standby [message #215121 is a reply to message #215113] Fri, 19 January 2007 06:57 Go to previous messageGo to next message
enkhbold
Messages: 36
Registered: July 2005
Location: Mongolia
Member

Sorry it is not v$sequence. It is v$archived_log.

Re: Apply archivedlog log in Standby [message #217715 is a reply to message #214782] Mon, 05 February 2007 00:33 Go to previous message
sharan alva
Messages: 57
Registered: November 1999
Member
From the primary it looks like the log were shipped twice, perhaps there was a disconnect, check the creator column

1906 18-Jan-2007 18-Jan-2007 YES NO YES
1906 18-Jan-2007 18-Jan-2007 YES NO NO
1907 18-Jan-2007 18-Jan-2007 YES NO YES
1907 18-Jan-2007 18-Jan-2007 YES NO NO

this can happen if fal has kicked in or if there was an rman backup.

Anyways, since this is a physical standby then you can place this back in managed recovery mode ie alter database recover managed standby database disconnect or you can do the following
sql>recover standby database;
==> this will ask for the next sequence .. say in your case 1906, if this log exists in the directory it is pointing to then hit enter and it should apply it and ask for the next sequence. Repeate this for all the sequences or if you have many of then simply type in auto, when all the logs in the destination have applied type cancel and exit out if it does not exit automatically and then place it in managed recovery mode. Then check the v$archived_log to see if it is applied and check this on the standby and the output from the primary and the standby can differ since the ack from the standby to the primary on the apply of the logs have low priority and can take some time to sync up.
Previous Topic: Dataguard info
Next Topic: max_sga
Goto Forum:
  


Current Time: Tue Dec 06 12:28:41 CST 2016

Total time taken to generate the page: 0.12757 seconds