7 Replies Latest reply: May 19, 2013 11:29 PM by CKPT RSS

    switchover_status in standby database showing NOT ALLOWED

    Meenakshy singh
      Hi All,

      My oracle database version is Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit on windows platform.

      I need to perform switchover activity with dg_broker=TRUE.
      When I checked the status of DR database I found that switchover_status is NOT ALLOWED rather than SESSION ACTIVE or TO PRIMARY.I have doubt whether switchover can be done successfully or not with this configuration?

      *Parameters from spfile in production database
      =======================================
      maxprod.__db_cache_size=2046820352
      maxprod.__java_pool_size=16777216
      maxprod.__large_pool_size=16777216
      maxprod.__shared_pool_size=352321536
      maxprod.__streams_pool_size=0
      *.audit_file_dest='C:\oracle\product\10.2.0\admin\maxprod\adump'
      *.background_dump_dest='C:\oracle\product\10.2.0\admin\maxprod\bdump'
      *.compatible='10.2.0.1.0'
      *.control_files='D:\MaximoData\oradata\maxprod\CONTROL01.CTL','D:\MaximoData\oradata\maxprod\CONTROL02.CTL','D:\MaximoData\oradata\maxprod\CONTROL03.CTL'
      *.core_dump_dest='C:\oracle\product\10.2.0\admin\maxprod\cdump'
      *.cursor_sharing='EXACT'
      *.db_block_size=8192
      *.db_domain=''
      *.db_file_multiblock_read_count=16
      *.db_name='maxprod'
      *.db_recovery_file_dest='D:\MaximoData\flash_recovery_area'
      *.db_recovery_file_dest_size=2147483648
      *.dg_broker_start=TRUE
      *.dispatchers='(PROTOCOL=TCP) (SERVICE=maxprodXDB)'
      *.fal_client='MAXPROD'
      *.fal_server='EAMDR'
      *.job_queue_processes=10
      *.log_archive_config='DG_CONFIG=(MAXPROD,EAMDR)'
      *.log_archive_dest_1='location=D:\MaximoData\Archive_Log valid_for=(all_logfiles,all_roles)'
      *.log_archive_dest_2='SERVICE=EAMDR VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=EAMDR'
      *.log_archive_dest_state_2='ENABLE'
      *.log_archive_max_processes=30
      *.log_archive_start=true
      *.log_buffer=100000000
      *.nls_language='AMERICAN'
      *.open_cursors=8000
      *.pga_aggregate_target=848297984
      *.processes=300
      *.remote_login_passwordfile='EXCLUSIVE'
      *.session_cached_cursors=20
      *.sga_max_size=4294967296
      *.sga_target=2550136832
      *.sql92_security=TRUE
      *.standby_archive_dest='D:\MaximoData\Archive_Log\standby'
      *.standby_file_management='auto'
      *.undo_management='AUTO'
      *.undo_tablespace='UNDOTBS1'
      *.user_dump_dest='C:\oracle\product\10.2.0\admin\maxprod\udump'*


      *Parameters from spfile in DR database
      ============================
      maxprod.__db_cache_size=3187671040
      eamdr.__db_cache_size=1073741824
      maxprod.__java_pool_size=16777216
      eamdr.__java_pool_size=16777216
      maxprod.__large_pool_size=16777216
      eamdr.__large_pool_size=16777216
      maxprod.__shared_pool_size=1056964608
      eamdr.__shared_pool_size=486539264
      maxprod.__streams_pool_size=0
      eamdr.__streams_pool_size=0
      *.audit_file_dest='C:\oracle\product\10.2.0\admin\EAMDR\adump'
      *.background_dump_dest='C:\oracle\product\10.2.0\admin\EAMDR\bdump'
      *.compatible='10.2.0.1.0'
      *.control_files='D:\MAXIMODATA\ORADATA\MAXPROD\CONTROL01.CTL','D:\MAXIMODATA\ORADATA\MAXPROD\CONTROL02.CTL','D:\MAXIMODATA\ORADATA\MAXPROD\CONTROL03.CTL'#Restore Controlfile
      *.core_dump_dest='C:\oracle\product\10.2.0\admin\EAMDR\cdump'
      *.db_block_size=8192
      *.db_domain=''
      *.db_file_multiblock_read_count=16
      *.db_name='maxprod'
      *.db_recovery_file_dest_size=10737418240
      *.db_recovery_file_dest='D:\MaximoData\flash_recovery_area'
      *.DB_UNIQUE_NAME='EAMDR'
      *.dg_broker_start=TRUE
      *.dispatchers='(PROTOCOL=TCP) (SERVICE=maxprodXDB)'
      *.fal_client='EAMDR'
      *.fal_server='MAXPROD'
      *.job_queue_processes=10
      *.log_archive_config='DG_CONFIG=(MAXPROD,EAMDR)'
      *.log_archive_dest_1='LOCATION=D:\MaximoData\Archive_Log VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=EAMDR'
      *.log_archive_dest_2='service=maxprod valid_for=(online_logfiles,primary_role) db_unique_name=MAXPROD'
      *.log_archive_dest_state_2='ENABLE'
      *.log_archive_max_processes=30
      *.nls_language='AMERICAN'
      *.open_cursors=8000
      *.pga_aggregate_target=194967296
      *.processes=150
      *.remote_login_passwordfile='EXCLUSIVE'
      *.sga_max_size=4294967296
      *.sga_target=1594967296
      *.standby_archive_dest='D:\MaximoData\Archive_Log\standby'
      *.standby_file_management='AUTO'
      *.undo_management='AUTO'
      *.undo_tablespace='UNDOTBS1'
      *.user_dump_dest='C:\oracle\product\10.2.0\admin\EAMDR\udump'*

      I didn't find any DG_BROKER_CONFIG_FILE1, DG_BROKER_CONFIG_FILE2 parameters from spfile in both production and DR db?

      Is anything missing in spfile?

      When I am trying to connect with dgmgrl
      DGMGRL>connect sys;
      connected
      DGMGRL>show configuration;
      Error: ORA-16532: Data Guard broker configuration does not exist

      what does it mean when dgmgrl is set to true?
      I have attached PRODUCTION and DR queries outputs for better understanding.

      IN PRIMARY DATABASE

      SQL>select database_role from v$database;

      DATABASE_ROLE
      --------------
      PRIMARY

      SQL> select switchover_status from v$database;

      SWITCHOVER_STATUS
      --------------------
      SESSIONS ACTIVE

      SQL> select db_unique_name,database_role,open_mode,log_mode,protection_mode from v$database;

      DB_UNIQUE_NAME DATABASE_ROLE OPEN_MODE LOG_MODE PROTECTION_MODE
      ------------------------------------------------------------------------------ ---------------- ---------- ------------ --------------------
      maxprod PRIMARY READ WRITE ARCHIVELOG MAXIMUM PERFORMANCE



      SQL> select process,status,client_process,sequence# from v$managed_standby;

      PROCESS STATUS CLIENT_P SEQUENCE#
      --------- ------------ -------- ----------
      ARCH CLOSING ARCH 7820
      ARCH CLOSING ARCH 7835
      ARCH CLOSING ARCH 7835
      ARCH CLOSING ARCH 7821
      ARCH CLOSING ARCH 7822

      ARCH CLOSING ARCH 7822

      ARCH CLOSING ARCH 7793

      ARCH CLOSING ARCH 7823

      ARCH CLOSING ARCH 7824

      ARCH CLOSING ARCH 7824

      ARCH CLOSING ARCH 7825
      ARCH CLOSING ARCH 7825

      ARCH CLOSING ARCH 7826

      ARCH CLOSING ARCH 7826

      ARCH CLOSING ARCH 7827

      ARCH CLOSING ARCH 7827

      ARCH CLOSING ARCH 7828

      ARCH CLOSING ARCH 7828

      ARCH CLOSING ARCH 7829

      ARCH CLOSING ARCH 7829

      ARCH CLOSING ARCH 7830

      ARCH CLOSING ARCH 7830

      ARCH CLOSING ARCH 7831

      ARCH CLOSING ARCH 7831

      ARCH CLOSING ARCH 7832

      ARCH CLOSING ARCH 7832
      ARCH CLOSING ARCH 7833

      ARCH CLOSING ARCH 7833

      ARCH CLOSING ARCH 7834

      ARCH CLOSING ARCH 7834

      30 rows selected.

      SQL> sho parameter log_archive_config

      NAME TYPE VALUE
      ------------------------------------ ----------- ------------------------------
      log_archive_config string DG_CONFIG=(MAXPROD,EAMDR)


      SQL> spool off


      IN SECONDARY DATABASE


      SQL> select database_role from v$database;

      DATABASE_ROLE
      -----------------
      PHYSICAL STANDBY


      SQL> select switchover_status from v$database;

      SWITCHOVER_STATUS --------------------
      NOT ALLOWED



      SQL> select db_unique_name,database_role,open_mode,log_mode,protection_mode from v$database;

      DB_UNIQUE_NAME DATABASE_ROLE OPEN_MODE LOG_MODE PROTECTION_MODE

      ----------------------------------------------------------------------------------- ---------------- ---------- ------------ --------------------


      EAMDR PHYSICAL STANDBY MOUNTED ARCHIVELOG MAXIMUM PERFORMANCE



      SQL> select process,status,client_process,sequence# from v$managed_standby;

      PROCESS STATUS CLIENT_P SEQUENCE#
      --------- ------------ -------- ----------

      ARCH CLOSING ARCH 7809

      ARCH CLOSING ARCH 7810

      ARCH CLOSING ARCH 7812

      ARCH CLOSING ARCH 7813

      ARCH CLOSING ARCH 7814

      ARCH CLOSING ARCH 7815

      ARCH CLOSING ARCH 7816

      ARCH CLOSING ARCH 7817

      ARCH CLOSING ARCH 7818

      ARCH CLOSING ARCH 7819

      ARCH CLOSING ARCH 7820

      ARCH CLOSING ARCH 7821

      ARCH CLOSING ARCH 7822

      ARCH CLOSING ARCH 7823

      ARCH CLOSING ARCH 7824

      ARCH CLOSING ARCH 7825

      ARCH CLOSING ARCH 7826

      ARCH CLOSING ARCH 7827

      ARCH CLOSING ARCH 7828

      ARCH CLOSING ARCH 7829

      ARCH CLOSING ARCH 7830

      ARCH CLOSING ARCH 7831

      ARCH CLOSING ARCH 7832

      ARCH CLOSING ARCH 7833

      ARCH CLOSING ARCH 7835

      ARCH CLOSING ARCH 7804

      ARCH CLOSING ARCH 7805

      ARCH CLOSING ARCH 7806

      ARCH CLOSING ARCH 7807

      ARCH CLOSING ARCH 7808

      MRP0 WAIT_FOR_LOG N/A 7836

      RFS IDLE UNKNOWN 0

      RFS IDLE UNKNOWN 0

      RFS IDLE UNKNOWN 0

      RFS IDLE UNKNOWN 0

      RFS IDLE UNKNOWN 0

      RFS IDLE UNKNOWN 0

      RFS IDLE UNKNOWN 0

      RFS IDLE UNKNOWN 0

      RFS IDLE UNKNOWN 0

      RFS IDLE UNKNOWN 0

      RFS IDLE UNKNOWN 0

      RFS IDLE UNKNOWN 0

      RFS IDLE UNKNOWN 0

      RFS IDLE UNKNOWN 0

      RFS IDLE UNKNOWN 0

      RFS IDLE
        • 1. Re: switchover_status in standby database showing NOT ALLOWED
          Mahir M. Quluzade
          Meenakshy singh wrote:
          Hi All,

          My oracle database version is Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit on windows platform.

          I need to perform switchover activity.When I checked the status of DR database I found that switchover_status is NOT ALLOWED rather than SESSION ACTIVE or TO PRIMARY.I have doubt whether switchover can be done successfully or not?

          I have attached PRODUCTION and DR queries outputs for better understanding.

          IN PRIMARY DATABASE

          SQL>select database_role from v$database;

          DATABASE_ROLE
          --------------
          PRIMARY

          SQL> select switchover_status from v$database;

          SWITCHOVER_STATUS
          --------------------
          SESSIONS ACTIVE

          SQL> select db_unique_name,database_role,open_mode,log_mode,protection_mode from v$database;

          DB_UNIQUE_NAME DATABASE_ROLE OPEN_MODE LOG_MODE PROTECTION_MODE
          ------------------------------------------------------------------------------ ---------------- ---------- ------------ --------------------
          maxprod PRIMARY READ WRITE ARCHIVELOG MAXIMUM PERFORMANCE



          SQL> select process,status,client_process,sequence# from v$managed_standby;

          PROCESS STATUS CLIENT_P SEQUENCE#
          --------- ------------ -------- ----------
          ARCH CLOSING ARCH 7820
          ARCH CLOSING ARCH 7835
          ARCH CLOSING ARCH 7835
          ARCH CLOSING ARCH 7821
          ARCH CLOSING ARCH 7822

          ARCH CLOSING ARCH 7822

          ARCH CLOSING ARCH 7793

          ARCH CLOSING ARCH 7823

          ARCH CLOSING ARCH 7824

          ARCH CLOSING ARCH 7824

          ARCH CLOSING ARCH 7825
          ARCH CLOSING ARCH 7825

          ARCH CLOSING ARCH 7826

          ARCH CLOSING ARCH 7826

          ARCH CLOSING ARCH 7827

          ARCH CLOSING ARCH 7827

          ARCH CLOSING ARCH 7828

          ARCH CLOSING ARCH 7828

          ARCH CLOSING ARCH 7829

          ARCH CLOSING ARCH 7829

          ARCH CLOSING ARCH 7830

          ARCH CLOSING ARCH 7830

          ARCH CLOSING ARCH 7831

          ARCH CLOSING ARCH 7831

          ARCH CLOSING ARCH 7832

          ARCH CLOSING ARCH 7832
          ARCH CLOSING ARCH 7833

          ARCH CLOSING ARCH 7833

          ARCH CLOSING ARCH 7834

          ARCH CLOSING ARCH 7834

          30 rows selected.

          SQL> sho parameter log_archive_config

          NAME TYPE VALUE
          ------------------------------------ ----------- ------------------------------
          log_archive_config string DG_CONFIG=(MAXPROD,EAMDR)


          SQL> spool off


          IN SECONDARY DATABASE


          SQL> select database_role from v$database;

          DATABASE_ROLE
          -----------------
          PHYSICAL STANDBY


          SQL> select switchover_status from v$database;

          SWITCHOVER_STATUS --------------------
          NOT ALLOWED



          SQL> select db_unique_name,database_role,open_mode,log_mode,protection_mode from v$database;

          DB_UNIQUE_NAME DATABASE_ROLE OPEN_MODE LOG_MODE PROTECTION_MODE

          ----------------------------------------------------------------------------------- ---------------- ---------- ------------ --------------------


          EAMDR PHYSICAL STANDBY MOUNTED ARCHIVELOG MAXIMUM PERFORMANCE



          SQL> select process,status,client_process,sequence# from v$managed_standby;

          PROCESS STATUS CLIENT_P SEQUENCE#
          --------- ------------ -------- ----------

          ARCH CLOSING ARCH 7809

          ARCH CLOSING ARCH 7810

          ARCH CLOSING ARCH 7812

          ARCH CLOSING ARCH 7813

          ARCH CLOSING ARCH 7814

          ARCH CLOSING ARCH 7815

          ARCH CLOSING ARCH 7816

          ARCH CLOSING ARCH 7817

          ARCH CLOSING ARCH 7818

          ARCH CLOSING ARCH 7819

          ARCH CLOSING ARCH 7820

          ARCH CLOSING ARCH 7821

          ARCH CLOSING ARCH 7822

          ARCH CLOSING ARCH 7823

          ARCH CLOSING ARCH 7824

          ARCH CLOSING ARCH 7825

          ARCH CLOSING ARCH 7826

          ARCH CLOSING ARCH 7827

          ARCH CLOSING ARCH 7828

          ARCH CLOSING ARCH 7829

          ARCH CLOSING ARCH 7830

          ARCH CLOSING ARCH 7831

          ARCH CLOSING ARCH 7832

          ARCH CLOSING ARCH 7833

          ARCH CLOSING ARCH 7835

          ARCH CLOSING ARCH 7804

          ARCH CLOSING ARCH 7805

          ARCH CLOSING ARCH 7806

          ARCH CLOSING ARCH 7807

          ARCH CLOSING ARCH 7808

          MRP0 WAIT_FOR_LOG N/A 7836

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0

          RFS IDLE UNKNOWN 0



          56 rows selected.

          SQL> sho parameter log_archive_config

          NAME TYPE VALUE
          ------------------------------------ ----------- ------------------------------

          log_archive_config string DG_CONFIG=(MAXPROD,EAMDR)


          SQL> spool off

          1.In this case,is switchover is possible?
          No
          2.If not possible then what will be the next step?
          If the value in the SWITCHOVER_STATUS column is SESSIONS ACTIVE, identify and terminate active user or SQL sessions that might prevent a switchover from being processed.
          If, after performing these steps, the SWITCHOVER_STATUS column still displays SESSIONS ACTIVE, you can successfully perform a switchover by appending the WITH SESSION SHUTDOWN clause to the
          ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY statement.

          3.Is this will impact to our production database when switchover is not successfully perform?
          4.In DR RFS is idle,why?
          Can you paste here log_archive_dest_n paramete which is you are using for transport?
          Did you using DELAY attribute in log_archive_dest_n parameter?


          Mahir
          • 2. Re: switchover_status in standby database showing NOT ALLOWED
            Meenakshy singh
            Hi,

            Thanks for the reply.

            IN PRODUCTION
            ==============================

            SQL> sho parameter log_archive_dest_

            NAME TYPE VALUE
            ------------------------------------ ----------- ------------------------------
            log_archive_dest_1 string location=D:\MaximoData\Archive Log validfor=(all_logfiles,a ll_roles)
            log_archive_dest_10 string
            log_archive_dest_2 string SERVICE=EAMDR VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=EAMDR
            log_archive_dest_3 string
            log_archive_dest_4 string
            log_archive_dest_5 string
            log_archive_dest_6 string

            NAME TYPE VALUE
            ------------------------------------ ----------- ------------------------------
            log_archive_dest_7 string
            log_archive_dest_8 string
            log_archive_dest_9 string
            log_archive_dest_state_1 string enable
            log_archive_dest_state_10 string enable
            log_archive_dest_state_2 string ENABLE
            log_archive_dest_state_3 string enable
            log_archive_dest_state_4 string enable
            log_archive_dest_state_5 string enable
            log_archive_dest_state_6 string enable
            log_archive_dest_state_7 string enable

            NAME TYPE VALUE
            ------------------------------------ ----------- ------------------------------
            log_archive_dest_state_8 string enable
            log_archive_dest_state_9 string enable

            In SECONDARY
            ===================

            SQL> sho parameter log_archive_dest

            NAME TYPE VALUE
            ------------------------------------ ----------- ------------------------------
            log_archive_dest string
            log_archive_dest_1 string LOCATION=D:\MaximoData\Archive_Log VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=EAMDR
            log_archive_dest_10 string
            log_archive_dest_2 string service=maxprod valid_for=(online_logfiles,primary_role) db_unique_name=MAXPROD
            log_archive_dest_3 string
            log_archive_dest_4 string
            log_archive_dest_5 string

            NAME TYPE VALUE
            ------------------------------------ ----------- ------------------------------
            log_archive_dest_6 string
            log_archive_dest_7 string
            log_archive_dest_8 string
            log_archive_dest_9 string
            log_archive_dest_state_1 string enable
            log_archive_dest_state_10 string enable
            log_archive_dest_state_2 string ENABLE
            log_archive_dest_state_3 string enable
            log_archive_dest_state_4 string enable
            log_archive_dest_state_5 string enable
            log_archive_dest_state_6 string enable

            NAME TYPE VALUE
            ------------------------------------ ----------- ------------------------------
            log_archive_dest_state_7 string enable
            log_archive_dest_state_8 string enable
            log_archive_dest_state_9 string enable
            SQL> spool off

            Regards,
            Meena
            • 3. Re: switchover_status in standby database showing NOT ALLOWED
              CKPT
              My oracle database version is Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit on windows platform.

              I need to perform switchover activity with dg_broker=TRUE.
              When I checked the status of DR database I found that switchover_status is NOT ALLOWED rather than SESSION ACTIVE or TO PRIMARY.I have doubt whether switchover can be done successfully or not with this configuration?
              1)
              As Mahir said , Look for any users are still performing any DMLs, also You got chance to check any job queue processes are running? Ensure with setting parameter job_queue_processes to zero.

              2) What about the synchronization between primary and standby?
              check my posts in Not allowed status in primary db switch_over status
              3)
              You are using Borker, so do switchover only using Broker.
              • 4. Re: switchover_status in standby database showing NOT ALLOWED
                rarain
                Hi Meenakshy,

                You are getting Error: ORA-16532: Data Guard broker configuration does not exist because you have not setup the broker configuration but you enable the broker as your DG_BROKER_START parameter is set to true. I would advise you to setup the broker if you want to perform the switchover operation using Broker else disable the broker by setting DG_BROKER_START=FALSE and perform the manual switchover.

                Case 1) Setup the broker as stated in below example assuming dg01 is my primary database and dg02 is my physical standby database.

                Step 1) Register a service db_name.db_domain_DGMGRL statically with the listener for primary as well as for standby database on primary as well as standby server.
                SID_LIST_LISTENER =
                (SID_LIST =
                (SID_DESC =
                (GLOBAL_DBNAME = dg01_DGMGRL)
                (ORACLE_HOME = /u01/app/oracle/oracle/product/10.2.0/db_1)
                (SID_NAME = dg01)
                )
                (SID_DESC =
                (GLOBAL_DBNAME = dg02_DGMGRL)
                (ORACLE_HOME = /u01/app/oracle/oracle/product/10.2.0/asm)
                (SID_NAME = dg02)
                )
                )
                Note:- Reload the listener after modifying the setting. (LSNRCTL RELOAD)

                Step 2) Configure a parameter DG_BROKER_START=TRUE on primary as well as on standby side.
                ALTER SYSTEM SET DG_BROKER_START=TRUE SCOPE=BOTH;

                Step 3) Invoke DGMGRL and create the configuration
                $ dgmgrl
                DGMGRL> connect sys/oracle@dg01
                DGMGRL> CREATE CONFIGURATION DGCONFIG1 AS PRIMARY DATABASE IS DG01 CONNECT IDENTIFIER IS ‘DG01′;
                DGMGRL> ADD DATABASE DG02 AS CONNECT IDENTIFIER IS ‘DG02′ MAINTAINED AS PHYSICAL;

                Step 4) Enable the configuration and check their status
                DGMGRL> SHOW CONFIGURATION
                DGMGRL> ENABLE CONFIGURATION

                DGMGRL> SHOW CONFIGURATION

                Case 2) Follow the below steps for manual Switchover:-

                Step 1) Check the network connectivity between the Primary and Standby database before initiating the Switchover.

                Step 2) Verify that it is possible to perform a switchover operation...for this check SWITCHOVER_STATUS from V$DATABASE it should show TO_STANDBY

                Step 3) Initiate the switchover operation on the primary database. (ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN WAIT)

                Step 4) Shutdown and restart the primary database
                SQL> Shutdown immediate
                SQL> Startup mount

                Step 5) Verify the switchover status on the standby database by querying SWITCHOVER_STATUS from V$DATABASE..It should be showing TO_PRIMARY now.

                Step 6) Switch the database role from standby to primary. (ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY)

                Step 7) Shutdown and restart the database.

                SQL> Shutdown immediate
                SQL> Startup

                Step 8) Confirm Log Transport and Redo apply service is functioning properly.

                SQL> Alter system switch logfile

                Thanks
                Rajeev
                • 5. Re: switchover_status in standby database showing NOT ALLOWED
                  Meenakshy singh
                  Hi,

                  Reply was very helpful but still one doubt i.e, why this many RFS process is idle?

                  can we set RFS process to a lower value?

                  What will be the impact of too many RFS in standby database?

                  Regards,
                  Meena
                  • 6. Re: switchover_status in standby database showing NOT ALLOWED
                    CKPT
                    Reply was very helpful but still one doubt i.e, why this many RFS process is idle?
                    There are no redo is trasmitting from the primary to standby and of course at that time it may be idle. Even i verified in my database. No need to worry on RFS idle status.
                    SQL> SELECT THREAD#,SEQUENCE#,PROCESS,CLIENT_PROCESS,STATUS,BLOCKS FROM V$MANAGED_STANDBY;
                    
                       THREAD#  SEQUENCE# PROCESS   CLIENT_P STATUS           BLOCKS
                    ---------- ---------- --------- -------- ------------ ----------
                             1        2146 ARCH      ARCH     CLOSING            12868
                             1        2148 ARCH      ARCH     CLOSING               6
                             0          0 ARCH      ARCH     CONNECTED             0
                             1        2147 ARCH      ARCH     CLOSING               8
                             1        2149 RFS       LGWR     IDLE                  1
                             0          0 RFS       UNKNOWN  IDLE                  0
                             0          0 RFS       UNKNOWN  IDLE                  0
                             0          0 RFS       N/A      IDLE                  0
                             1        2149 MRP0      N/A      APPLYING_LOG     2204800
                    9 rows selected.
                    SQL>
                    can we set RFS process to a lower value?
                    What will be the impact of too many RFS in standby database?
                    What is the value of LOG_ARCHIVE_MAX_PROCESSES. you have assigned too many?
                    • 7. Re: switchover_status in standby database showing NOT ALLOWED
                      Mahir M. Quluzade
                      Can you check log_archive_max_processes parameter on primary database?
                      Please paste here.

                      If you want lower value, I think you must change it.


                      Mahir