This discussion is archived
12 Replies Latest reply: Jan 5, 2013 11:12 AM by 857396 RSS

Datagaurd swithover from rac to non rac.

857396 Newbie
Currently Being Moderated
Hello Team,

1.we have created single DR db for the RAC primary database, and we need to perform a swithover to the DR from RAC by DGMGRL, in this case how can we place an entry for both listeners for automatic restart by DGMGRL during the switchover activity ?

2.in this case which one better performing maunal switchover on sql prompt or by DGMGRL ?

3.do we need shutdown one instance during switchover to non rac or will be automatically taken care of DGMGRL???

4. once the non rac converted to primary which rac instance will be applying the logs on RAC standby from non rac?? No oracle docs saying this clearly pls help.


Thanks in advance.
  • 1. Re: Datagaurd swithover from rac to non rac.
    857396 Newbie
    Currently Being Moderated
    Hello Team,

    1.we have created single DR db for the RAC primary database, and we need to perform a swithover to the DR from RAC by DGMGRL, in this case how can we place an entry for both listeners for automatic restart by DGMGRL during the switchover activity ?

    2.in this case which one better performing maunal switchover on sql prompt or by DGMGRL ?

    3.do we need shutdown one instance during switchover to non rac or will be automatically taken care of DGMGRL???

    4. once the non rac converted to primary which rac instance will be applying the logs on RAC standby from non rac?? No oracle docs saying this clearly pls help.

    Thanks in advance.
  • 2. Re: Datagaurd swithover from rac to non rac.
    Victor Armbrust Oracle ACE
    Currently Being Moderated
    Hi

    Please, inform what platform and version you are using.

    In a mean time, Follow some answers


    *1.we have created single DR db for the RAC primary database, and we need to perform a swithover to the DR from RAC by DGMGRL, in this case how can we place an entry for both listeners for automatic restart by DGMGRL during the switchover activity ?*

    ANSWER: You should configure BOTH listeners on RAC and DG Single. All listeners should Attend GLOBAL_NAMES (This ins required to remote startup an instance from listener "as sysdba". Also you need to use "EDIT INSTANCE" to specify the correct address list:

    Eg:
    EDIT INSTANCE oradb1 SET PROPERTY StaticConnectIdentifier='(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.1 68.1.6)(PORT=1522))(CONNECT_DATA=(SERVICE_NAME=oradb_DGMGRL)(INSTANCE_NA ME=oradb1)(SERVER=DEDICATED)))';
    *2.in this case which one better performing maunal switchover on sql prompt or by DGMGRL ?*

    ANSWER: BROKER (DGMGRL) is designed to make your life easy during SWITCHOVER and FAILOVER/REINSTATE tasks. But, it is your call. To do a SWITCHOVER via SQLPLUS you should use follow steps (not all here, but just to help you out)
    ON PRIMARY
    
    SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN
    
    
    MAKE SWITCHOVER EFFECTIVE on SWITCHOVER
    
    SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WITH SESSION SHUTDOWN;
    
    
    OPEN THE STANDBY
    
    SQL> ALTER DATABASE OPEN;
    *3.do we need shutdown one instance during switchover to non rac or will be automatically taken care of DGMGRL???*
    ANSWER: No. BROKER will take care of all tasks (if its configured correctly, of course)


    *4. once the non rac converted to primary which rac instance will be applying the logs on RAC standby from non rac?? No oracle docs saying this clearly pls help.*
    ANSWER: well, its directly depends on your DG configuration. You should configure both your RAC (PRIMARY) nodes to point to SINGLE DG DR (using log_archive_dest_)
    On your DG, you should point to both or all nodes of your PRIMARY, then after a SWITCHOVER or FAILOVER your DG/DR will point to all nodes of pRIMARY RAC. All depends on your configuration.

    Here is a COMPLETE DOCUMENTATION that I made for 11gR2 RAC Primary x Single DR Data guard. This doc has all information you need. BUT, ONLY ONE CONCERN
    IT IS IN PORTUGUESE/BR (Since I'm from BRAZIL) :(
    http://www.profissionaloracle.com.br/gpo/phocadownload/banco/DG11_install_MP.pdf

    Good Luck

    Victor
  • 3. Re: Datagaurd swithover from rac to non rac.
    857396 Newbie
    Currently Being Moderated
    Dear victor,

    Thanks for ur answers for all of my clarifications,


    1. here we using PROD is the db name and prod1 and prod2 is the instance name so in the below service name entry can we use prod_DGMGRL ? or we can create prod1 and pror2 as service on the parameter file and provide that service name in the service entry ??

    our version is - 11.2.0.1
    os - HP unix 11.31

    and one more clarification.

    2. before cloned the RAC DB to single DR, we created standby redo logs on primary for thered 1 and 2 with comparing online redo of primary.( 7 + 7 = 14 online redo) on rac primary, so we created 8 standby redolog for each instance with similar size of rac redo, 8+8=16 SRL.... so finally when we backup and restored to the DR site on single node these entries of online redo and SRL almost 14 online redo, and 16 Standby redo came and automatically created on single DB(DR) now, so do we need to house keep or add anyting on the single standby now,?? or this all will be automatically used ???

    3. in future if u want to add some online redo logs/ standby redo logs on single node DR, how to add it ? as file_management set to auto ?

    pls help ... !!!
  • 4. Re: Datagaurd swithover from rac to non rac.
    Victor Armbrust Oracle ACE
    Currently Being Moderated
    Helo my friend


    1. here we using PROD is the db name and prod1 and prod2 is the instance name so in the below service name entry can we use prod_DGMGRL ? or we can create prod1 and pror2 as service on the parameter file and provide that service name in the service entry ??

    A: Since you are using 11gR2 you should use "_DGB" instead "_DGMGRL"... look at the sample below:
    (Im assuming your DG DB_UNIQUE_NAME is proddr)
    TNSNAMES.ORA ON RAC (service for DR STANDBY DG - should be configured on both nodes)
    
    PRODDR =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = server_dr_name)(PORT = 1522))
        (CONNECT_DATA =
          (SERVICE_NAME = proddr)
        )
      )
    
    
    PROD =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = racnode1)(PORT = 1522))
    (ADDRESS = (PROTOCOL = TCP)(HOST = racnode2)(PORT = 1522))
    (CONNECT_DATA =
    (SERVICE_NAME = prod_DGB)
    (FAILOVER_MODE =
    (TYPE = SELECT)
    (METHOD = BASIC)
    (RETRIES = 20)
    (DELAY = 5)
    )
    )
    )
    
    LISTENER.ORA ON RAC (Used by DR/STANDBY DG to connect to RAC- should by configured in node1 and node2)
    
    --NODE1
    
    LISTENER_PROD_DG =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = racnode1)(PORT = 1522))
    )
    )
    SID_LIST_LISTENER_PROD_DG =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DBNAME = prod_DGB)
    (SERVICE_NAME = prod)
    (SID_NAME = prod1)
    (ORACLE_HOME = /u01/app/oracle/product/11.2.0.3/db_1)))
    ADR_BASE_LISTENER_ORMTP1_DG = /u01/app/oracle
    
    
    --NODE2
    
    LISTENER_PROD_DG =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = racnode2)(PORT = 1522))
    )
    )
    SID_LIST_LISTENER_PROD_DG =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DBNAME = prod_DGB)
    (SERVICE_NAME = prod)
    (SID_NAME = prod2)
    (ORACLE_HOME = /u01/app/oracle/product/11.2.0.3/db_1)))
    ADR_BASE_LISTENER_ORMTP1_DG = /u01/app/oracle
    
    
    TNSNAMES.ORA ON DR/DG (service for DR STANDBY DG)
    
    
    PRODDR =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = server_dr_name)(PORT = 1522))
        (CONNECT_DATA =
          (SERVICE_NAME = proddr)
        )
      )
    
    
    PROD =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = racnode1)(PORT = 1522))
    (ADDRESS = (PROTOCOL = TCP)(HOST = racnode2)(PORT = 1522))
    (CONNECT_DATA =
    (SERVICE_NAME = prod_DGB)
    (FAILOVER_MODE =
    (TYPE = SELECT)
    (METHOD = BASIC)
    (RETRIES = 20)
    (DELAY = 5)
    )
    )
    )
    
    LISTENER.ORA ON DR/DG (Used by RAC/PRIMARY to connect to DG-)
    
    LISTENER_PROD_DG =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST =server_dr_name)(PORT = 1522))
    )
    )
    SID_LIST_LISTENER_PROD_DG =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DBNAME = proddr_DGB)
    (SERVICE_NAME = proddr)
    (SID_NAME = proddr)
    (ORACLE_HOME = /u01/app/oracle/product/11.2.0.3/db_1)))
    ADR_BASE_LISTENER_ORMTP1_DG = /u01/app/oracle
    2. before cloned the RAC DB to single DR, we created standby redo logs on primary for thered 1 and 2 with comparing online redo of primary.( 7 + 7 = 14 online redo) on rac primary, so we created 8 standby redolog for each instance with similar size of rac redo, 8+8=16 SRL.... so finally when we backup and restored to the DR site on single node these entries of online redo and SRL almost 14 online redo, and 16 Standby redo came and automatically created on single DB(DR) now, so do we need to house keep or add anyting on the single standby now,?? or this all will be automatically used ???

    A: You should use the same STANDBY REDOLOGS from Duplicate of PRIMARY


    3. in future if u want to add some online redo logs/ standby redo logs on single node DR, how to add it ? as file_management set to auto ?

    A: You can add new REDOS or STANDBY REDOS using "ALTER DATABASE ADD LOGFILE" command
    if you have problems doing it, just change "standby_file_management" from AUTO to MANUAL

    Hope have Helped

    Victor
  • 5. Re: Datagaurd swithover from rac to non rac.
    user11969666 Newbie
    Currently Being Moderated
    Dear Victor,

    Really thanks for anwering all of our questions,

    we added some more online redo log and standby redolog on standby db by setting file_management=manual on primary, but now we receiving a below error on standby DB alert log,and log shipping also very slow now.

    Errors in file /oracle/oracledr/diag/rdbms/proddr/proddr/trace/proddr_mrp0_17371.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    Errors in file /oracle/oracledr/diag/rdbms/proddr/proddr/trace/proddr_mrp0_17371.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    Errors in file /oracle/oracledr/diag/rdbms/proddr/proddr/trace/proddr_mrp0_17371.trc:
    ORA-00313: open failed for members of log group 3 of thread 2
    Errors in file /oracle/oracledr/diag/rdbms/proddr/trace/proddr_mrp0_17371.trc:
    ORA-00313: open failed for members of log group 4 of thread 2
    Errors in file /oracle/oracledr/diag/rdbms/proddr/proddr/trace/proddr_mrp0_17371.trc:
    ORA-00313: open failed for members of log group 5 of thread 1
    Errors in file /oracle/oracledr/diag/rdbms/proddr/proddr/trace/proddr_mrp0_17371.trc:
    ORA-00313: open failed for members of log group 6 of thread 1
    Errors in file /oracle/oracledr/diag/rdbms/proddr/proddr/trace/proddr_mrp0_17371.trc:
    ORA-00313: open failed for members of log group 7 of thread 1
    Errors in file /oracle/oracledr/diag/rdbms/proddr/proddr/trace/proddr_mrp0_17371.trc:
    ORA-00313: open failed for members of log group 8 of thread 1
    Errors in file /oracle/oracledr/diag/rdbms/proddr/proddr/trace/proddr_mrp0_17371.trc:
    ORA-00313: open failed for members of log group 9 of thread 1
    Errors in file /oracle/oracledr/diag/rdbms/proddr/proddr/trace/proddr_mrp0_17371.trc:
    ORA-00313: open failed for members of log group 10 of thread 2
    Errors in file /oracle/oracledr/diag/rdbms/proddr/proddr/trace/proddr_mrp0_17371.trc:
    ORA-00313: open failed for members of log group 11 of thread 2
    Errors in file /oracle/oracledr/diag/rdbms/proddr/proddr/trace/proddr_mrp0_17371.trc:
    ORA-00313: open failed for members of log group 12 of thread 2
    Errors in file /oracle/oracledr/diag/rdbms/proddr/proddr/trace/proddr_mrp0_17371.trc:
    ORA-00313: open failed for members of log group 13 of thread 2
    Errors in file /oracle/oracledr/diag/rdbms/proddr/proddr/trace/proddr_mrp0_17371.trc:
    ORA-00313: open failed for members of log group 14 of thread 2
    Media Recovery Waiting for thread 1 sequence 34936 (in transit)
    Recovery of Online Redo Log: Thread 1 Group 16 Seq 34936 Reading mem 0


    Thanks in advance..!!!
  • 6. Re: Datagaurd swithover from rac to non rac.
    Victor Armbrust Oracle ACE
    Currently Being Moderated
    You should use the same number of standby redo logs of PRIMARY. I can't see any reason to add more...

    What's the size of your database? You can use onlye the same redos from PRIMARY.
  • 7. Re: Datagaurd swithover from rac to non rac.
    857396 Newbie
    Currently Being Moderated
    Thanks victor,,,

    almost 400GB,

    one more, we did a switchover in sql from rac to Non rac (test setup), so after switching over the single node DR start using/following a thread1 redo's and log sequence, in such a case the rac become standby now and we started only instance 2 on rac and placed it on recover mode now, and its start applying logs from the single DR now,so can we start a another rac node also and place it on recover mode? is it possible,or do we need to disable any online log thread or standby log thread on new primary (single DR node) ???

    also we can see the new primary control file says still some of archived log not applied, also the rac standby control file says now, there are two log file still not applied but those are in disk now... but during a switchover we followed below method and all completed successfully. the way only we confusing rac to single. all online log file and stand by redo on use for both the threads, pls help. why its showing below not applied.


    from new Primary.(non rac)

    SQL> select SEQUENCE#,thread#,APPLIED,ARCHIVED,DELETED,STATUS from v$archived_log;

    SEQUENCE# THREAD# APPLIED ARC DEL S
    ---------- ---------- --------- --- --- -
    15 2 YES YES YES D
    35 1 YES YES NO A
    17 2 YES YES NO A
    16 2 YES YES NO A
    19 2 YES YES NO A
    23 2 YES YES NO A
    20 2 YES YES NO A
    18 2 YES YES NO A
    21 2 YES YES NO A
    22 2 YES YES NO A
    38 1 YES YES NO A

    SEQUENCE# THREAD# APPLIED ARC DEL S
    ---------- ---------- --------- --- --- -
    36 1 YES YES NO A
    39 1 YES YES NO A
    37 1 YES YES NO A
    24 2 YES YES NO A
    25 2 YES YES NO A
    26 2 YES YES NO A
    27 2 YES YES NO A
    28 2 YES YES NO A
    29 2 YES YES NO A
    30 2 YES YES NO A
    31 2 YES YES NO A

    SEQUENCE# THREAD# APPLIED ARC DEL S
    ---------- ---------- --------- --- --- -
    32 2 YES YES NO A
    33 2 YES YES NO A
    35 2 YES YES NO A
    34 2 YES YES NO A
    36 2 YES YES NO A
    37 2 YES YES NO A
    38 2 YES YES NO A
    39 2 YES YES NO A
    40 2 YES YES NO A
    41 2 YES YES NO A
    42 2 YES YES NO A

    SEQUENCE# THREAD# APPLIED ARC DEL S
    ---------- ---------- --------- --- --- -
    43 2 YES YES NO A
    44 2 YES YES NO A
    45 2 NO YES NO A
    40 1 NO YES NO A
    46 2 NO YES NO A
    47 2 NO YES NO A
    41 1 NO YES NO A
    42 1 NO YES NO A
    43 1 NO YES NO A
    44 1 NO YES NO A
    45 1 NO YES NO A

    SEQUENCE# THREAD# APPLIED ARC DEL S
    ---------- ---------- --------- --- --- -
    46 1 NO YES NO A
    42 1 YES YES NO A
    40 1 YES YES NO A
    45 2 NO YES NO A
    46 2 NO YES NO A
    43 1 YES YES NO A
    44 1 YES YES NO A
    41 1 YES YES NO A
    45 1 YES YES NO A
    47 2 NO YES NO A
    46 1 NO YES NO A

    55 rows selected.

    SQL>

    =======================================================================

    *From new standby rac --below*


    SQL> /

    SEQUENCE# THREAD# APPLIED ARC DEL S
    ---------- ---------- --------- --- --- -
    13 2 YES YES NO A
    14 2 YES YES NO A
    25 1 YES YES NO A
    26 1 YES YES NO A
    27 1 YES YES NO A
    28 1 YES YES NO A
    29 1 YES YES NO A
    30 1 YES YES NO A
    31 1 YES YES NO A
    32 1 YES YES NO A
    33 1 YES YES NO A

    SEQUENCE# THREAD# APPLIED ARC DEL S
    ---------- ---------- --------- --- --- -
    34 1 YES YES NO A
    35 1 YES YES NO A
    15 2 YES YES NO A
    16 2 YES YES NO A
    17 2 YES YES NO A
    36 1 YES YES NO A
    18 2 YES YES NO A
    19 2 YES YES NO A
    37 1 YES YES NO A
    20 2 YES YES NO A
    38 1 YES YES NO A

    SEQUENCE# THREAD# APPLIED ARC DEL S
    ---------- ---------- --------- --- --- -
    39 1 YES YES NO A
    21 2 YES YES NO A
    22 2 YES YES NO A
    23 2 YES YES NO A
    17 2 YES YES NO A
    16 2 YES YES NO A
    19 2 YES YES NO A
    23 2 YES YES NO A
    18 2 YES YES NO A
    20 2 YES YES NO A
    21 2 YES YES NO A

    SEQUENCE# THREAD# APPLIED ARC DEL S
    ---------- ---------- --------- --- --- -
    22 2 YES YES NO A
    24 2 YES YES NO A
    36 1 YES YES NO A
    38 1 YES YES NO A
    39 1 YES YES NO A
    37 1 YES YES NO A
    24 2 YES YES NO A
    25 2 YES YES NO A
    25 2 YES YES NO A
    26 2 YES YES NO A
    26 2 YES YES NO A

    SEQUENCE# THREAD# APPLIED ARC DEL S
    ---------- ---------- --------- --- --- -
    27 2 YES YES NO A
    27 2 YES YES NO A
    28 2 YES YES NO A
    28 2 YES YES NO A
    29 2 YES YES NO A
    29 2 YES YES NO A
    30 2 YES YES NO A
    30 2 YES YES NO A
    31 2 YES YES NO A
    31 2 YES YES NO A
    32 2 YES YES NO A

    SEQUENCE# THREAD# APPLIED ARC DEL S
    ---------- ---------- --------- --- --- -
    32 2 YES YES NO A
    33 2 YES YES NO A
    33 2 YES YES NO A
    34 2 YES YES NO A
    35 2 YES YES NO A
    36 2 YES YES NO A
    35 2 YES YES NO A
    34 2 YES YES NO A
    36 2 YES YES NO A
    37 2 YES YES NO A
    37 2 YES YES NO A

    SEQUENCE# THREAD# APPLIED ARC DEL S
    ---------- ---------- --------- --- --- -
    38 2 YES YES NO A
    38 2 YES YES NO A
    39 2 YES YES NO A
    39 2 YES YES NO A
    40 2 YES YES NO A
    40 2 YES YES NO A
    41 2 YES YES NO A
    41 2 YES YES NO A
    42 2 YES YES NO A
    42 2 YES YES NO A
    43 2 NO YES NO A

    SEQUENCE# THREAD# APPLIED ARC DEL S
    ---------- ---------- --------- --- --- -
    43 2 YES YES NO A
    44 2 YES YES NO A
    44 2 NO YES NO A
    42 1 YES YES NO A
    40 1 YES YES NO A
    45 2 YES YES NO A
    46 2 YES YES NO A
    43 1 YES YES NO A
    44 1 YES YES NO A
    41 1 YES YES NO A
    45 1 YES YES NO A

    SEQUENCE# THREAD# APPLIED ARC DEL S
    ---------- ---------- --------- --- --- -
    47 2 YES YES NO A
    46 1 IN-MEMORY YES NO A

    90 rows selected.

    SQL>
  • 8. Re: Datagaurd swithover from rac to non rac.
    857396 Newbie
    Currently Being Moderated
    from new primary after switchover.


    SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
    WHERE APPLIED='NO'; 2

    SEQUENCE# APPLIED
    ---------- ---------
    45 NO
    40 NO
    46 NO
    47 NO
    41 NO
    42 NO
    43 NO
    44 NO
    45 NO
    46 NO
    45 NO

    SEQUENCE# APPLIED
    ---------- ---------
    46 NO
    47 NO
    47 NO
    47 NO

    15 rows selected.

    SQL>





    from new standby (RAC after switchover)

    SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
    WHERE APPLIED='NO'; 2

    SEQUENCE# APPLIED
    ---------- ---------
    43 NO
    44 NO

    SQL>



    even standby status says resolvable gab, but... the below log says waiting for other new logs.


    NOTE: dependency between database RAC and diskgroup resource ora.FRA.dg is established
    Media Recovery Log +FRA/rac/archivelog/2013_01_05/thread_2_seq_46.309.803948755
    Media Recovery Log +FRA/rac/archivelog/2013_01_05/thread_1_seq_40.303.803948745
    Media Recovery Log +FRA/rac/archivelog/2013_01_05/thread_2_seq_47.307.803948753
    Media Recovery Log +FRA/rac/archivelog/2013_01_05/thread_1_seq_41.308.803948753
    Media Recovery Log +FRA/rac/archivelog/2013_01_05/thread_1_seq_42.304.803948745
    Media Recovery Log +FRA/rac/archivelog/2013_01_05/thread_1_seq_43.305.803948749
    Media Recovery Log +FRA/rac/archivelog/2013_01_05/thread_1_seq_44.310.803948755
    Media Recovery Log +FRA/rac/archivelog/2013_01_05/thread_1_seq_45.306.803948749
    Sat Jan 05 23:35:17 2013
    Media Recovery Log +FRA/rac/archivelog/2013_01_05/thread_1_seq_46.312.803948761
    Media Recovery Waiting for thread 1 sequence 47 (in transit)
    Recovery of Online Redo Log: Thread 1 Group 15 Seq 47 Reading mem 0
    Mem# 0: +DATA/rac/onlinelog/group_15.276.803940205
    Sat Jan 05 23:52:02 2013
    RFS[1]: Selected log 16 for thread 1 sequence 48 dbid -1935449590 branch 771535694
    Sat Jan 05 23:52:06 2013
    Media Recovery Waiting for thread 1 sequence 48 (in transit)
    Sat Jan 05 23:52:06 2013
    Time drift detected. Please check VKTM trace file for more details.
    Recovery of Online Redo Log: Thread 1 Group 16 Seq 48 Reading mem 0
    Mem# 0: +DATA/rac/onlinelog/group_16.277.803940213
    Sat Jan 05 23:52:10 2013
    Archived Log entry 91 added for thread 1 sequence 47 ID 0x8e927d4c dest 1:



    pls help..... how to resolve this and do switch back...
  • 9. Re: Datagaurd swithover from rac to non rac.
    857396 Newbie
    Currently Being Moderated
    when try to register it manually its says already registered.

    43 2 NO YES NO A

    SEQUENCE# THREAD# APPLIED ARC DEL S
    ---------- ---------- --------- --- --- -
    43 2 YES YES NO A
    44 2 YES YES NO A
    44 2 NO YES NO A
    42 1 YES YES NO A
    40 1 YES YES NO A
    45 2 YES YES NO A
    46 2 YES YES NO A
    43 1 YES YES NO A
    44 1 YES YES NO A
    41 1 YES YES NO A
    45 1 YES YES NO A

    SEQUENCE# THREAD# APPLIED ARC DEL S
    ---------- ---------- --------- --- --- -
    47 2 YES YES NO A
    46 1 YES YES NO A
    47 1 IN-MEMORY YES NO A

    91 rows selected.

    SQL> alter system register logfile '+FRA/rac/archivelog/2013_01_05/thread_1_seq_43.305.803948749';
    alter system register logfile '+FRA/rac/archivelog/2013_01_05/thread_1_seq_43.305.803948749'
    *
    ERROR at line 1:
    ORA-00933: SQL command not properly ended


    SQL> select max(sequence#) from v$archived_log;

    MAX(SEQUENCE#)
    --------------
    47

    SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
    WHERE APPLIED='NO'; 2

    SEQUENCE# APPLIED
    ---------- ---------
    43 NO
    44 NO

    SQL> ALTER DATABASE REGISTER LOGFILE '+FRA/rac/archivelog/2013_01_05/thread_1_seq_43.305.803948749';
    ALTER DATABASE REGISTER LOGFILE '+FRA/rac/archivelog/2013_01_05/thread_1_seq_43.305.803948749'
    *
    ERROR at line 1:
    ORA-16089: archive log has already been registered


    SQL>
  • 10. Re: Datagaurd swithover from rac to non rac.
    Victor Armbrust Oracle ACE
    Currently Being Moderated
    You can use both nodes to apply logs, however you need to configure it via Service/Log_archive_dest (as I mentioned before)

    400Gb is not a big size, so you can use the standby logs as I mentioned.

    You can look at v$log to check you logs applied, also you can check alert.log
    select max(sequence#), thread from v$log group by thread;
    The sequences should be the same (but it is not means it synchronized, so you need to check alert.log and look for applied logs)

    Switchover will only be succeded if all logs are applied. You can also check the SWITCHOVER_STATUS from v$database before do the switchover
    select switchover_status from v$database;
    Victor
  • 11. Re: Datagaurd swithover from rac to non rac.
    857396 Newbie
    Currently Being Moderated
    Thanks a lot victor......
  • 12. Re: Datagaurd swithover from rac to non rac.
    857396 Newbie
    Currently Being Moderated
    thanks

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points