1 2 Previous Next 26 Replies Latest reply: Jul 31, 2012 12:01 PM by 9233598 RSS

    log_archive_dest_1 got changed each time after switchover through dgmgrl

    9233598
      I was testing different scenarios to switchover from a to b, a to c, c to b, b to c, b to a for my one primary with 2 standby configuration.

      In some cases, the log_archive_dest_1 got changed.

      alert .log will have those errors:

      ARC7: Archiving not possible: no primary destinations
      ARC7: Failed to archive thread 1 sequence 2692 (4)

      drc*.log shows:
      07/29/2012 02:06:37
      SQL Execution error=604, sql=[ALTER SYSTEM ARCHIVE LOG CURRENT]. See error stack below.
      ORA-00604: error occurred at recursive SQL level 1
      ORA-16014: log 1 sequence# 2692 not archived, no available destinations
      ORA-00312: online log 1 thread 1: '+DAT/prd/onlinelog/group_1.342.785963735'
      ORA-00312: online log 1 thread 1: '+FRA
      RSM0 failed to reset Redo Transport Services, error ORA-16778
      Deferring associated archivelog destinations of sites permanently disabled due to Switchover
      Notifying Oracle Clusterware to buildup primary database after SWITCHOVER
      Data Guard notifying Oracle Clusterware to start services and other instances change
      Command SWITCHOVER TO prdl completed

      Then I checked log_archive_dest_1 it changed to standby_roles as below without db_unique_name.

      log_archive_dest_1 location="USE_DB_RECOVERY_FILE_DEST", valid_for=(STANDBY_LOGFILE,STANDBY_ROLE)

      Why this behavior happen? how to prevent it in real life during role transitions?

      Thanks in advance.
        • 1. Re: log_archive_dest_1 got changed each time after switchover through dgmgrl
          9233598
          more informaiton: every time dgmgrl show configuration has no error, and every switchover finished successfully.
          • 2. Re: log_archive_dest_1 got changed each time after switchover through dgmgrl
            CKPT
            9233598 wrote:
            I was testing different scenarios to switchover from a to b, a to c, c to b, b to c, b to a for my one primary with 2 standby configuration.

            In some cases, the log_archive_dest_1 got changed.

            alert .log will have those errors:

            ARC7: Archiving not possible: no primary destinations
            ARC7: Failed to archive thread 1 sequence 2692 (4)

            drc*.log shows:
            07/29/2012 02:06:37
            SQL Execution error=604, sql=[ALTER SYSTEM ARCHIVE LOG CURRENT]. See error stack below.
            ORA-00604: error occurred at recursive SQL level 1
            ORA-16014: log 1 sequence# 2692 not archived, no available destinations
            ORA-00312: online log 1 thread 1: '+DAT/prd/onlinelog/group_1.342.785963735'
            ORA-00312: online log 1 thread 1: '+FRA
            RSM0 failed to reset Redo Transport Services, error ORA-16778
            Deferring associated archivelog destinations of sites permanently disabled due to Switchover
            Notifying Oracle Clusterware to buildup primary database after SWITCHOVER
            Data Guard notifying Oracle Clusterware to start services and other instances change
            Command SWITCHOVER TO prdl completed

            Then I checked log_archive_dest_1 it changed to standby_roles as below without db_unique_name.

            log_archive_dest_1 location="USE_DB_RECOVERY_FILE_DEST", valid_for=(STANDBY_LOGFILE,STANDBY_ROLE)

            Why this behavior happen? how to prevent it in real life during role transitions?

            Thanks in advance.
            You having Broker, Then probably you have set FRA also.. Then check what is the location of FRA
            SQL> show parameter db_recovery

            Then by default DGMGRL is taking archive destination as FRA.

            Also, when you said log_archive_dest_1 above, it referring to STANDBY_LOGFILE is it standby database where Real time apply is active?
            These attributes are applicable if it is standby database and SRL's are active.
            • 3. Re: log_archive_dest_1 got changed each time after switchover through dgmgrl
              9233598
              When i switch primary to standby,it should switch to active read only standby.the problem is log arch dest1 got changed then arc process fail and db not function.
              • 4. Re: log_archive_dest_1 got changed each time after switchover through dgmgrl
                mseberg
                Hello;

                Given your plan this might apply :

                Archive Log Creation Fails With Errors ORA-16014, ORA-00312 [ID 1373314.1]

                Best Regards

                mseberg
                • 5. Re: log_archive_dest_1 got changed each time after switchover through dgmgrl
                  CKPT
                  9233598 wrote:
                  When i switch primary to standby,it should switch to active read only standby.the problem is log arch dest1 got changed then arc process fail and db not function.
                  use below commands from the location where the parameters are changing.

                  DGMGRL> show database <db> logxptstatus;
                  DGMGRL> SHOW DATABASE <db> InconsistentProperties;
                  DGMGRL> show database <db> InconsistentLogXptProps;
                  • 6. Re: log_archive_dest_1 got changed each time after switchover through dgmgrl
                    9233598
                    Ok i wll provide those later. Have not turned work computer yet
                    • 7. Re: log_archive_dest_1 got changed each time after switchover through dgmgrl
                      9233598
                      Here is the query results:

                      DGMGRL> show configuration

                      Configuration - prd_dg

                      Protection Mode: MaxPerformance
                      Databases:
                      prd - Primary database
                      prds - Physical standby database
                      prdl - Physical standby database

                      Fast-Start Failover: DISABLED

                      Configuration Status:
                      SUCCESS

                      DGMGRL> show database remeprd logxptstatus;
                      LOG TRANSPORT STATUS
                      PRIMARY_INSTANCE_NAME STANDBY_DATABASE_NAME STATUS
                      PRD1 prds
                      PRD1 prdl
                      PRD2 prds
                      PRD2 prdl

                      DGMGRL> show database remeprd inconsistentproperties;
                      INCONSISTENT PROPERTIES
                      INSTANCE_NAME PROPERTY_NAME MEMORY_VALUE SPFILE_VALUE BROKER_VALUE

                      DGMGRL> show database remeprd inconsistentLogXptProps;
                      INCONSISTENT LOG TRANSPORT PROPERTIES
                      INSTANCE_NAME STANDBY_NAME PROPERTY_NAME MEMORY_VALUE BROKER_VALUE
                      • 8. Re: log_archive_dest_1 got changed each time after switchover through dgmgrl
                        CKPT
                        I dont see any issue here.

                        post
                        SQL> show parameter db_reco
                        SQL> archive log list
                        • 9. Re: log_archive_dest_1 got changed each time after switchover through dgmgrl
                          9233598
                          Sorry was in meeting all morning.

                          Here is the results:

                          SQL> show parameter db_reco

                          NAME TYPE VALUE
                          ------------------------------------ ----------- ------------------------------
                          db_recovery_file_dest string +FRA
                          db_recovery_file_dest_size big integer 737000M
                          SQL> archive log list
                          Database log mode Archive Mode
                          Automatic archival Enabled
                          Archive destination USE_DB_RECOVERY_FILE_DEST
                          Oldest online log sequence 2700
                          Next log sequence to archive 2702
                          Current log sequence 2702
                          SQL>
                          • 10. Re: log_archive_dest_1 got changed each time after switchover through dgmgrl
                            CKPT
                            9233598 wrote:
                            Sorry was in meeting all morning.

                            Here is the results:

                            SQL> show parameter db_reco

                            NAME TYPE VALUE
                            ------------------------------------ ----------- ------------------------------
                            db_recovery_file_dest string +FRA
                            db_recovery_file_dest_size big integer 737000M
                            SQL> archive log list
                            Database log mode Archive Mode
                            Automatic archival Enabled
                            Archive destination USE_DB_RECOVERY_FILE_DEST
                            Oldest online log sequence 2700
                            Next log sequence to archive 2702
                            Current log sequence 2702
                            SQL>
                            So as per the FRA location, archive destination was set by default.
                            RSM0 failed to reset Redo Transport Services, error ORA-16778
                            Deferring associated archivelog destinations of sites permanently disabled due to Switchover
                            For archive location set to "DEFER" ? thats why unable to set that location and unable to archive?
                            Have you tried using NET_TIMEOUT parameter?
                            • 11. Re: log_archive_dest_1 got changed each time after switchover through dgmgrl
                              9233598
                              no, the problem is during some switchover operation, some database log_archive_dest_1 changed by oracle from valid_for=(all_roles, all_logfiles) to valid_for=(standby_role, standby_logfiles). This caused db not been able to connected. I have to manually change the valid_for attribute to all_roles, all_logfiles.

                              Why this happned?
                              • 12. Re: log_archive_dest_1 got changed each time after switchover through dgmgrl
                                9233598
                                This happened again. When I tried to switch over to one db from a primary, the log_archive_dest_1 was changed from valid_for=(all_logfiles, all_roles) to valid_for=(standby_roles, standby_logfiles) and db_unique_name got deleted.

                                and log_archive_dest2 got deleted.

                                WHy this kind of behavior happened?
                                • 13. Re: log_archive_dest_1 got changed each time after switchover through dgmgrl
                                  mseberg
                                  Hello;

                                  No idea what is going on. Did find a note :

                                  Broker overrides local LOG_ARCHIVE_DEST_n destination on Bystander Standby [ID 1364467.1]


                                  Based on what you are reporting same except "Bystander Standby". Maybe bug is larger than Oracle thinks.

                                  Best Regards

                                  mseberg
                                  • 14. Re: log_archive_dest_1 got changed each time after switchover through dgmgrl
                                    9233598
                                    This note seems like closest to my issue, it matches my db version also.

                                    I just don't understand its solution.

                                    basically it asked to recreate dg configuraiton using log_archive_dest_1=Locaiton= only, no valid_for, no db_unique_name.

                                    Am I right here?
                                    1 2 Previous Next