1 2 3 Previous Next 39 Replies Latest reply: Nov 25, 2013 4:02 AM by Anar Godjaev Go to original post RSS
      • 30. Re: I am not getting archive files in standby Error "Heartbeat failed to connect to standby ' database'. Error is 12514.
        MHAIDAR

        DGMGRL> edit configuration set protection mode as maxavailability;
        Error: ORA-16627: operation disallowed since no standby databases would remain to support protection mode

        Failed.
        DGMGRL> edit database epprod1 set property LogxptMOde='ASYNC';
        Error: ORA-16805: change of LogXptMode property violates overall protection mode

         

        I check the connectivity

         

        I try to tnsping both with reply

        I try to connect@ I connected

         

        But there is somthing I dont know

         

        I did

         

        sqlplus / as sysdba@epprod2

        connected

        But when I did

        select instnace_name from v$instance;

        epprod1 it should be epprod2

         

        But  when I connecto username/username@epprod2

        connected

        select instnace_name from v$instance;

        epprod1

        • 31. Re: I am not getting archive files in standby Error "Heartbeat failed to connect to standby ' database'. Error is 12514.
          Anar Godjaev

          HI again ,

           

          Please read:

           

          ORA-16627:
          operation disallowed since no standby databases would remain to support protection mode
          Cause:  This status is returned in the following situations:
          - The broker rejects an attempt to change the configuration's overall protection mode since it could not find any online, enabled standby databases that support the proposed protection mode.

          - The broker rejects an attempt to enable the configuration if it determines there are no online, enabled standby databases that support the overall protection mode.

          - The broker rejects an attempt to disable or remove a database that, if disabled or deleted, would result in no remaining standby databases that can support the configuration's overall protection mode.

          - The broker rejects an attempt to set the configuration offline if doing so would violate the configuration's overall protection mode.

          - The broker rejects an attempt to set a standby database offline if doing so would violate the configuration's overall protection mode.

          - The broker rejects a switchover attempt if doing so would violate the configuration's overall protection mode.

          - The broker returns this error during a health check.


          Action:  - If changing the overall protection mode, confirm that at least one standby database satisfies the new protection mode.
          - For enable failures, confirm that at least one standby database has a LogXptMode configuration property setting that supports the current overall protection mode.

          - For delete and disable failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode.

          - For state change failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode. If setting the configuration OFFLINE you may have to downgrade the protection mode setting to maximum performance beforehand.

          - For switchover failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode. If your configuration contains a primary database and a single standby database, ensure that the LogXptMode configuration property established for the primary database supports the overall protection mode. After the switchover, the old primary database will become the standby database and its LogXptMode configuration property setting must support the overall protection mode.

          - For health check error, confirm that at least one standby database has a LogXptMode configuration property setting that supports the current overall protection mode.

           


          • 32. Re: I am not getting archive files in standby Error "Heartbeat failed to connect to standby ' database'. Error is 12514.
            Mahir M. Quluzade

            MHAIDAR wrote:

             

            DGMGRL> edit configuration set protection mode as maxavailability;
            Error: ORA-16627: operation disallowed since no standby databases would remain to support protection mode

            Failed.
            DGMGRL> edit database epprod1 set property LogxptMOde='ASYNC';
            Error: ORA-16805: change of LogXptMode property violates overall protection mode

             

            Follow this commands:

             

            DGMGRL> edit database epprod2 set property LogxptMOde='SYNC';

            DGMGRL> edit configuration set protection mode as maxavailability;

             

            if there have error or warning try before my reply

            • 33. Re: I am not getting archive files in standby Error "Heartbeat failed to connect to standby ' database'. Error is 12514.
              MHAIDAR

              Dear

              Mahir

              I can't apply

              DGMGRL> edit database epprod2 set property LogxptMOde='SYNC';

              DGMGRL> edit configuration set protection mode as maxavailability;

               

              Becuase it's standyby it's on read only ... I tried before not accepted.

               

              But Now I did the configuration again , I think i did correct  now as you can see below ... but still  I have warning in primary ... but succed in secondary I need to solve this issue

               

              DGMGRL> SHOW DATABASE EPPROD1

              Database - epprod1

                Role:            PRIMARY
                Intended State:  TRANSPORT-ON
                Instance(s):
                  epprod1

                Database Warning(s):
                  ORA-16629: database reports a different protection level from the protection mode

              Database Status:
              WARNING

              DGMGRL>
              DGMGRL>
              DGMGRL> SHOW DATABASE EPPROD2

              Database - epprod2

                Role:            PHYSICAL STANDBY
                Intended State:  APPLY-ON
                Transport Lag:   0 seconds
                Apply Lag:       0 seconds
                Real Time Query: OFF
                Instance(s):
                  epprod2

              Database Status:
              SUCCESS

              DGMGRL> SHOW DATABASE VERBOSE EPPROD1

              Database - epprod1

                Role:            PRIMARY
                Intended State:  TRANSPORT-ON
                Instance(s):
                  epprod1

              Database Warning(s):
                  ORA-16629: database reports a different protection level from the protection mode

                Properties:
                  DGConnectIdentifier             = 'epprod1'
                  ObserverConnectIdentifier       = ''
                  LogXptMode                      = 'SYNC'
                  DelayMins                       = '0'
                  Binding                         = 'optional'
                  MaxFailure                      = '0'
                  MaxConnections                  = '1'
                  ReopenSecs                      = '300'
                  NetTimeout                      = '30'
                  RedoCompression                 = 'DISABLE'
                  LogShipping                     = 'ON'
                  PreferredApplyInstance          = ''
                  ApplyInstanceTimeout            = '0'
                  ApplyParallel                   = 'AUTO'
                  StandbyFileManagement           = 'AUTO'
                  ArchiveLagTarget                = '0'
                  LogArchiveMaxProcesses          = '8'
                  LogArchiveMinSucceedDest        = '2'
                  DbFileNameConvert               = 'D:\DATABASES\EPPROD\, D:\DATABASES\EPPROD\, E:\DATABASES\EPPROD\, E:\DATABASES\EPPROD\'
                  LogFileNameConvert              = 'D:\Databases\epprod\PrimaryRedolog\, D:\Databases\epprod\PrimaryRedolog\, D:\Databases\epprod\StandbyRedoLog\, D:\Databases\epprod\StandbyRedoLog\'
                  FastStartFailoverTarget         = ''
                  InconsistentProperties          = '(monitor)'
                  InconsistentLogXptProps         = '(monitor)'
                  SendQEntries                    = '(monitor)'
                  LogXptStatus                    = '(monitor)'
                  RecvQEntries                    = '(monitor)'
                  SidName                         = 'epprod1'
                  StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=CORSKMBBOR01)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=epprod1_DGMGRL)(INSTANCE_NAME=epprod1)(SERVER=DEDICATED)
                  StandbyArchiveLocation          = 'E:\Fast_Recovery_Area\Archive\Epprod\Dest1\'
                  AlternateLocation               = ''
                  LogArchiveTrace                 = '127'
                  LogArchiveFormat                = 'epprod_t%t_s%S_r%r.arc'
                  TopWaitEvents                   = '(monitor)'

              Database Status:
              WARNING

              DGMGRL> SHOW DATABASE VERBOSE EPPROD2

              Database - epprod2

                Role:            PHYSICAL STANDBY
                Intended State:  APPLY-ON
                Transport Lag:   0 seconds
                Apply Lag:       0 seconds
                Real Time Query: OFF
                Instance(s):
                  epprod2

                Properties:
                  DGConnectIdentifier             = 'epprod2'
                  ObserverConnectIdentifier       = ''
                  LogXptMode                      = 'ASYNC'
                  DelayMins                       = '0'
                  Binding                         = 'OPTIONAL'
                  MaxFailure                      = '0'
                  MaxConnections                  = '1'
                  ReopenSecs                      = '300'
                  NetTimeout                      = '30'
                  RedoCompression                 = 'DISABLE'
                  LogShipping                     = 'ON'
                  PreferredApplyInstance          = ''
                  ApplyInstanceTimeout            = '0'
                  ApplyParallel                   = 'AUTO'
                  StandbyFileManagement           = 'AUTO'
                  ArchiveLagTarget                = '0'
                  LogArchiveMaxProcesses          = '8'
                  LogArchiveMinSucceedDest        = '2'
                  DbFileNameConvert               = 'D:\DATABASES\EPPROD\, D:\DATABASES\EPPROD\, E:\DATABASES\EPPROD\, E:\DATABASES\EPPROD\'
                  LogFileNameConvert              = 'D:\Databases\epprod\PrimaryRedolog\, D:\Databases\epprod\PrimaryRedolog\, D:\Databases\epprod\StandbyRedoLog\, D:\Databases\epprod\StandbyRedoLog\'
                  FastStartFailoverTarget         = ''
                  InconsistentProperties          = '(monitor)'
                  InconsistentLogXptProps         = '(monitor)'
                  SendQEntries                    = '(monitor)'
                  LogXptStatus                    = '(monitor)'
                  RecvQEntries                    = '(monitor)'
                  SidName                         = 'epprod2'
                  StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.2.5.51)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=EPPROD2_DGMGRL)(INSTANCE_NAME=epprod2)(SERVER=DEDICATED)))'
                  StandbyArchiveLocation          = 'E:\Fast_Recovery_Area\Archive\Epprod\Dest1\'
                  AlternateLocation               = ''
                  LogArchiveTrace                 = '127'
                  LogArchiveFormat                = 'epprod_t%t_s%S_r%r.arc'
                  TopWaitEvents                   = '(monitor)'

              Database Status:
              SUCCESS

              • 34. Re: I am not getting archive files in standby Error "Heartbeat failed to connect to standby ' database'. Error is 12514.
                MHAIDAR

                Hi Anar

                 

                The standby database is configure and funcotion logs generated and implemented , I think I have problem with protection mode....what you suggest? since I am doing all of thses to facilitate the switch ove and failover ...

                • 35. Re: I am not getting archive files in standby Error "Heartbeat failed to connect to standby ' database'. Error is 12514.
                  Anar Godjaev

                  HI MHAIDAR,

                   

                  I advise you to read it through Oracle Support :  ORA-16629 database reports a different protection level from the protection mode (Doc ID 1319903.1)

                   

                  Thank you

                  • 36. Re: I am not getting archive files in standby Error "Heartbeat failed to connect to standby ' database'. Error is 12514.
                    MHAIDAR

                    Hi Aanar

                     

                    I read the documen carfully,,,, I have one standby confirm the protection mode. and configured to maximum availabilty and LogXptMode should Async

                    • 37. Re: I am not getting archive files in standby Error "Heartbeat failed to connect to standby ' database'. Error is 12514.
                      Mahir M. Quluzade

                      You protection mode is different between database and broker configuration.

                      Please try

                       

                      1. Chnage protection mode:

                       

                      DGMGRL> edit configuration set protection mode as MAXPERFORMACE;

                      DGMGRL> edit database epprod1 set property LogxptMOde='ASYNC';

                       

                      DGMGRL> show configuration;

                       

                      2. Change Protection mode from MAX Performance to AVAILABILITY

                       

                      DGMGRL> edit database epprod1 set property LogxptMOde='SYNC';

                      DGMGRL> edit database epprod2 set property LogxptMOde='SYNC';

                       

                      DGMGRL> edit configuration set protection mode as MAXAVAILABILITY;

                       

                       

                      Paste here results

                       

                      Mahir

                      • 38. Re: I am not getting archive files in standby Error "Heartbeat failed to connect to standby ' database'. Error is 12514.
                        MHAIDAR

                        Oh sorry now I am getting other error

                        ORA-16143: RFS connections not allowed during or after terminal

                        recovery

                        let me solve this problme first

                         

                        I will come back with your advice ...... sorry for that


                        • 39. Re: I am not getting archive files in standby Error "Heartbeat failed to connect to standby ' database'. Error is 12514.
                          Anar Godjaev

                          Please read Support id :

                           

                          OERR: ORA-16143 RFS connections not allowed during or after terminal recovery  [Article ID 172869.1]

                          ORA-16143 While Redo Transport to Standby (Doc ID 834817.1)

                           

                          Thank you

                          1 2 3 Previous Next