Home » Server Options » Data Guard » RAC - DG (Red Hat Enterprise Linux Server release 5.8 (Tikanga))
RAC - DG [message #671051] Mon, 13 August 2018 05:32 Go to next message
dirish
Messages: 223
Registered: November 2006
Senior Member
We have a 2 Node RAC on Dataguard. Log files are being shipped but not applied.

From Primary Node 1
SQL> archive log list
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /archive/mtmeddb
Oldest online log sequence     233073
Next log sequence to archive   233083
Current log sequence           233083

From Primary Node 2
SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /archive/mtmeddb
Oldest online log sequence     118877
Next log sequence to archive   118880
Current log sequence           118880

From Standby Database
   INST_ID PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS
---------- --------- ------------ ---------- ---------- ---------- ----------
         1 ARCH      CONNECTED             0          0          0          0
         1 ARCH      CONNECTED             0          0          0          0
         1 ARCH      CONNECTED             0          0          0          0
         1 ARCH      CONNECTED             0          0          0          0
         1 RFS       IDLE                  0          0          0          0
         1 RFS       IDLE                  1     233083     480820          2
         1 RFS       IDLE                  0          0          0          0
         1 RFS       IDLE                  0          0          0          0
         1 MRP0      WAIT_FOR_LOG          2     118441          0          0
Re: RAC - DG [message #671052 is a reply to message #671051] Mon, 13 August 2018 05:34 Go to previous messageGo to next message
dirish
Messages: 223
Registered: November 2006
Senior Member
From the Standby Server which was dead for quite some time

ORA11g_DR>cd /ORARNC1/archive/

ORA11g_DR>ls -l *118441*
ls: *118441*: No such file or directory
Re: RAC - DG [message #671053 is a reply to message #671051] Mon, 13 August 2018 05:36 Go to previous messageGo to next message
John Watson
Messages: 8075
Registered: January 2010
Location: Global Village
Senior Member
If you run your gv$managed_standby query on the primary, the problem may become clear.
Re: RAC - DG [message #671054 is a reply to message #671053] Mon, 13 August 2018 05:47 Go to previous messageGo to next message
dirish
Messages: 223
Registered: November 2006
Senior Member
From Primary Node 1
SQL> select INST_ID,PROCESS,STATUS,THREAD#,SEQUENCE#,BLOCK#,BLOCKS from gv$managed_standby;

   INST_ID PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS
---------- --------- ------------ ---------- ---------- ---------- ----------
         1 ARCH      CLOSING               1     233085     864256       1507
         1 ARCH      CLOSING               1     232731       2570       2569
         1 ARCH      CLOSING               1     233083     851968        703
         1 ARCH      CLOSING               1     233084     851968       1874
         1 LNS       WRITING               1     233086     398927          1
         2 ARCH      CLOSING               2     118881     872448        810
         2 ARCH      CLOSING               2     118879     876544       1071
         2 ARCH      CONNECTED             0          0          0          0
         2 ARCH      CLOSING               2     118880     876544       1201

9 rows selected.



From Primary Node2
SQL> select INST_ID,PROCESS,STATUS,THREAD#,SEQUENCE#,BLOCK#,BLOCKS from gv$manag    ed_standby;

   INST_ID PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS
---------- --------- ------------ ---------- ---------- ---------- ----------
         2 ARCH      CLOSING               2     118881     872448        810
         2 ARCH      CLOSING               2     118879     876544       1071
         2 ARCH      CONNECTED             0          0          0          0
         2 ARCH      CLOSING               2     118880     876544       1201
         1 ARCH      CLOSING               1     233085     864256       1507
         1 ARCH      CLOSING               1     232731       2570       2569
         1 ARCH      CLOSING               1     233083     851968        703
         1 ARCH      CLOSING               1     233084     851968       1874
         1 LNS       WRITING               1     233086     399016          1

9 rows selected.
Re: RAC - DG [message #671055 is a reply to message #671054] Mon, 13 August 2018 05:50 Go to previous messageGo to next message
John Watson
Messages: 8075
Registered: January 2010
Location: Global Village
Senior Member
So inst_id 2 is not transmitting any redo. Better look at v$archive_dest to see why not. Or you could look at the alert log, that will tell you too.

And note that there is no point in querying a gv$ view on both nodes. I hope you understand why: if you do not, you need to do some studying about RAC.

[Updated on: Mon, 13 August 2018 05:51]

Report message to a moderator

Re: RAC - DG [message #671056 is a reply to message #671055] Mon, 13 August 2018 05:59 Go to previous messageGo to next message
dirish
Messages: 223
Registered: November 2006
Senior Member
yes i know for the gv$ view...thanks for your suggestion.

since archive logs from inst_id 2 is not available (since node was dead for quite some time), can i make the DG to work only with Primary Node1 (inst_id 1) and the Standby Server?
Re: RAC - DG [message #671057 is a reply to message #671056] Mon, 13 August 2018 06:01 Go to previous message
John Watson
Messages: 8075
Registered: January 2010
Location: Global Village
Senior Member
You need to determine why the redo has not been transmitted. I have already told you how to do that.
Previous Topic: RMAN and Dataguard
Next Topic: Error: ORA-12154 when add standby
Goto Forum:
  


Current Time: Sun Dec 08 17:46:29 CST 2019