Home » Server Options » Data Guard » Dataguard Issue - Logs get shipped but not Applied - Due to Primary DB reset (merged) (Oracle 11.2.0.3 . WIndows 2008)
icon5.gif  Dataguard Issue - Logs get shipped but not Applied - Due to Primary DB reset (merged) [message #590721] Mon, 22 July 2013 11:00 Go to next message
Morgs
Messages: 21
Registered: October 2010
Location: South AFrica
Junior Member

HI

I have a Sap Primry Database and also a standby db that was working perfectly.. We migrated the primary db from windows 2003 to windows 2008 and brought the primary db up.. I had to create a controlfile and do a system copy and had to reset the logs on the Primary.. All came up and when i checked the standby it was receiving the logs but after a month. i see that it was not applying the logs as I think because of the sequence number .. it stopped.

I did the ffg as per the attachement

My logs have been shipped across but not applied, But What worrries me is the log sequence number on my Primary

SQL> select max(sequence#),thread# from gv$archived_log group by thread#;

MAX(SEQUENCE#) THREAD#
-------------- ----------
27727 1

[Updated on: Mon, 22 July 2013 13:07] by Moderator

Report message to a moderator

Re: Dataguard Not Applying Logs [message #590731 is a reply to message #590721] Mon, 22 July 2013 11:18 Go to previous messageGo to next message
Michel Cadot
Messages: 59814
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Copy and paste what is text in text INLINE AND FORMATTED.
Please read OraFAQ Forum Guide and How to use [code] tags and make your code easier to read.
Make sure that lines of code do not exceed 80 characters when you format.
Indent the code, use code tags and align the columns in result.
Use the "Preview Message" or "Preview Quick Reply" button to verify.
Also always post your Oracle version, with 4 decimals.

Your images are too small I can't read them.

And FEEDBACK to those that help you and those that post you questions.
We are waiting in your previous topics.

Regards
Michel
Re: Dataguard Not Applying Logs [message #590736 is a reply to message #590731] Mon, 22 July 2013 11:25 Go to previous messageGo to next message
Morgs
Messages: 21
Registered: October 2010
Location: South AFrica
Junior Member

Thanks

Can You delete this message and I will try again and I am not sure how to delete what is there ..

[Updated on: Mon, 22 July 2013 11:25]

Report message to a moderator

Re: Dataguard Not Applying Logs [message #590738 is a reply to message #590721] Mon, 22 July 2013 11:35 Go to previous messageGo to next message
Morgs
Messages: 21
Registered: October 2010
Location: South AFrica
Junior Member

See Text Attachments
Re: Dataguard Not Applying Logs [message #590742 is a reply to message #590738] Mon, 22 July 2013 12:27 Go to previous messageGo to next message
Michel Cadot
Messages: 59814
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
INLINE means NO ATTACHMENT.
Many of us can't or don't want to download files, so post them inline in text mode and post them formatted.

Regards
Michel
Re: Dataguard Not Applying Logs [message #590745 is a reply to message #590742] Mon, 22 July 2013 12:56 Go to previous messageGo to next message
Morgs
Messages: 21
Registered: October 2010
Location: South AFrica
Junior Member

Primary DB
-----------------

SQL> connect /as sysdba
Connected.
SQL> select max(sequence#) Last_Archived_Log_Applied from v$archived_log where Applied='YES';

LAST_ARCHIVED_LOG_APPLIED
-------------------------
27727



SQL> ARCHIVE LOG LIST
Database log mode Archive Mode
Automatic archival Enabled
Archive destination E:\oracle\WU1\oraarch\WU1arch
Oldest online log sequence 2080
Next log sequence to archive 2083
Current log sequence 2083



Standby DB
-----------------------------------------------------------

SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;

PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS
--------- ------------ ---------- ---------- ---------- ----------
ARCH      CONNECTED             0          0          0          0
ARCH      CLOSING               1       1613          1        129
RFS       IDLE                  0          0          0          0
MRP0      WAIT_FOR_LOG          1      27727          0          0
RFS       IDLE                  1       2083      21524          3



SQL> select max(sequence#) Last_Archived_Log_Applied from v$archived_log where Applied='YES';

LAST_ARCHIVED_LOG_APPLIED
-------------------------
27726

SQL> select * from v$archive_gap;

no rows selected

SQL> ARCHIVE LOG LIST
Database log mode Archive Mode
Automatic archival Enabled
Archive destination E:\oracle\WU1\oraarch\WU1arch
Oldest online log sequence 27724
Next log sequence to archive 0
Current log sequence 27727
SQL>
Re: Dataguard Not Applying Logs [message #590747 is a reply to message #590745] Mon, 22 July 2013 13:08 Go to previous messageGo to next message
Michel Cadot
Messages: 59814
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Michel Cadot wrote on Mon, 22 July 2013 18:18
Copy and paste what is text in text INLINE AND FORMATTED.
Please read OraFAQ Forum Guide and How to use [code] tags and make your code easier to read.
Make sure that lines of code do not exceed 80 characters when you format.
Indent the code, use code tags and align the columns in result.
Use the "Preview Message" or "Preview Quick Reply" button to verify.
Also always post your Oracle version, with 4 decimals.

Your images are too small I can't read them.

And FEEDBACK to those that help you and those that post you questions.
We are waiting in your previous topics.


Regards
Michel

Dataguard Issue - Logs get shipped but not Applied - Due to Primary DB reset [message #590792 is a reply to message #590721] Tue, 23 July 2013 00:11 Go to previous messageGo to next message
Morgs
Messages: 21
Registered: October 2010
Location: South AFrica
Junior Member

HI

I have a Sap Primry Database and also a standby db that was working perfectly.. We migrated the primary db from windows 2003 to windows 2008 and brought the primary db up.. I had to create a controlfile and do a system copy and had to reset the logs on the Primary.. All came up and when i checked the standby it was receiving the logs but after a month. i see that it was not applying the logs as I think because of the sequence number .. it stopped.



My logs have been shipped across but not applied, But What worrries me is the log sequence number on my Primary is still thw same number as teh day i reset the db..


Check status on Priamry DB
---------------------------

SQL> select max(sequence#),thread# from gv$archived_log group by thread#;

MAX(SEQUENCE#) THREAD#
-------------- ----------
27727 1


But when I do a arch log list..i.e .on the primary it says 2083 but on the standby it says 27727 and on the primary ( old sequence number_


SQL> ARCHIVE LOG LIST
Database log mode Archive Mode
Automatic archival Enabled
Archive destination E:\oracle\WU1\oraarch\WU1arch
Oldest online log sequence 2080
Next log sequence to archive 2083
Current log sequence 2083

I have check evrything on the standby i.e

Standby DB
-----------------------------------------------------------

SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;

PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS
--------- ------------ ---------- ---------- ---------- ----------
ARCH      CONNECTED             0          0          0          0
ARCH      CLOSING               1       1613          1        129
RFS       IDLE                  0          0          0          0
MRP0      WAIT_FOR_LOG          1      27727          0          0
RFS       IDLE                  1       2083      21524          3



SQL> select max(sequence#) Last_Archived_Log_Applied from v$archived_log where Applied='YES';

LAST_ARCHIVED_LOG_APPLIED
-------------------------
27726

SQL> select * from v$archive_gap;

no rows selected

SQL> ARCHIVE LOG LIST
Database log mode Archive Mode
Automatic archival Enabled
Archive destination E:\oracle\WU1\oraarch\WU1arch
Oldest online log sequence 27724
Next log sequence to archive 0
Current log sequence 27727
SQL>


On The standbu and it shoudl say 2083..

Appreciate any help
Thanks
Re: Dataguard Issue - Logs get shipped but not Applied - Due to Primary DB reset [message #590794 is a reply to message #590792] Tue, 23 July 2013 00:15 Go to previous messageGo to next message
Michel Cadot
Messages: 59814
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Michel Cadot wrote on Mon, 22 July 2013 20:08
Michel Cadot wrote on Mon, 22 July 2013 18:18
Copy and paste what is text in text INLINE AND FORMATTED.
Please read OraFAQ Forum Guide and How to use [code] tags and make your code easier to read.
Make sure that lines of code do not exceed 80 characters when you format.
Indent the code, use code tags and align the columns in result.
Use the "Preview Message" or "Preview Quick Reply" button to verify.
Also always post your Oracle version, with 4 decimals.

Your images are too small I can't read them.

And FEEDBACK to those that help you and those that post you questions.
We are waiting in your previous topics.


Regards
Michel


Re: Dataguard Issue - Logs get shipped but not Applied - Due to Primary DB reset (merged) [message #590800 is a reply to message #590721] Tue, 23 July 2013 01:07 Go to previous messageGo to next message
John Watson
Messages: 4806
Registered: January 2010
Location: Global Village
Senior Member
I would remove the entire standby configuration and set it up again.
Re: Dataguard Issue - Logs get shipped but not Applied - Due to Primary DB reset (merged) [message #590820 is a reply to message #590800] Tue, 23 July 2013 05:07 Go to previous messageGo to next message
Morgs
Messages: 21
Registered: October 2010
Location: South AFrica
Junior Member

H john

Thansk for that.. Just want to know how can i change this on the primary server. Should it not show 2083 or 2080


SQL> select max(sequence#) Last_Archived_Log_Applied from v$archived_log where Applied='YES';

LAST_ARCHIVED_LOG_APPLIED
-------------------------
27726



AS the log shows this on the primary server

SQL> ARCHIVE LOG LIST
Database log mode Archive Mode
Automatic archival Enabled
Archive destination E:\oracle\WU1\oraarch\WU1arch
Oldest online log sequence 2080
Next log sequence to archive 2083
Current log sequence 2083


Re: Dataguard Issue - Logs get shipped but not Applied - Due to Primary DB reset (merged) [message #590822 is a reply to message #590820] Tue, 23 July 2013 05:14 Go to previous messageGo to next message
John Watson
Messages: 4806
Registered: January 2010
Location: Global Village
Senior Member
Are you saying that you want to change reality? It seems to me that the last log applied was 27726. You haven't applied any more, so presumably you are missing 27727. Was that the one that was active when you did the resetlogs? If you have a copy of it somewhere, you can try to apply it, and then apply the 2083 archives generated since. But if Data Guard can't sort this out automatically, I think you have broken it.
Re: Dataguard Issue - Logs get shipped but not Applied - Due to Primary DB reset (merged) [message #590823 is a reply to message #590822] Tue, 23 July 2013 05:24 Go to previous messageGo to next message
Morgs
Messages: 21
Registered: October 2010
Location: South AFrica
Junior Member

Hi John

Must apolgise of I am not makign myself clear.. On The real primary db. The last log that was applied according to the statement is 27726 . This was the time I brougt up the db on the primary system after i migrated it from winodows 2003..

Everythign is working.. on the primary DB.. But shoudl i worry about that statement on the primary db where it shows last log applied is 27726 or not. as when i check the logs sequence on the primary it shows i.e 2083.

SQL> ARCHIVE LOG LIST
Database log mode Archive Mode
Automatic archival Enabled
Archive destination E:\oracle\WU1\oraarch\WU1arch
Oldest online log sequence 2080
Next log sequence to archive 2083
Current log sequence 2083


Just want to know if this is a concern on the Priamry db.. Should not be as evrythign is working

Re: Dataguard Issue - Logs get shipped but not Applied - Due to Primary DB reset (merged) [message #590825 is a reply to message #590823] Tue, 23 July 2013 05:29 Go to previous messageGo to next message
John Watson
Messages: 4806
Registered: January 2010
Location: Global Village
Senior Member
Now you are not thinking. To where are archivelogs applied? To the primary or to the standby?
Re: Dataguard Issue - Logs get shipped but not Applied - Due to Primary DB reset (merged) [message #590826 is a reply to message #590825] Tue, 23 July 2013 05:36 Go to previous messageGo to next message
Morgs
Messages: 21
Registered: October 2010
Location: South AFrica
Junior Member

Hi

Thanks.. Archivelogs are applied to the standby..for dr purposes

Just want to know what should the statement in the priamry be showing ( Or should I not run that stament in teh Primary).
Re: Dataguard Issue - Logs get shipped but not Applied - Due to Primary DB reset (merged) [message #590829 is a reply to message #590826] Tue, 23 July 2013 05:51 Go to previous message
John Watson
Messages: 4806
Registered: January 2010
Location: Global Village
Senior Member
You still refuse to think, man! Four more questions:
What was the last archive log applied?
What does Oracle tell you was the last archive log applied?
Is Oracle telling you the truth?
Why would you want Oracle to tell you anything else?
Previous Topic: Logical Standby
Next Topic: Can a logical database be applied from a physical standby
Goto Forum:
  


Current Time: Thu Nov 27 15:49:26 CST 2014

Total time taken to generate the page: 0.11826 seconds