1 2 Previous Next 19 Replies Latest reply: Apr 25, 2014 11:31 AM by yoonas Go to original post RSS
      • 15. Re: Heartbeat failed to connect to standby . Error is 16058
        yoonas

        After recreating the password file you still have same error in alert log?

        from primary can you run same sql you run before to see the stus of primary/standby database

        Connect to primary

        conn / as sysdba
        select open_mode from v$database;
        

        Connect to standby

        conn sys@p_stdy as sysdba
        select open_mode from v$database;
        

         

         

        Make sure p_stdy service is actually pointing to standby server,

        post

        p_stdy tns entry on primary server

        pfile from both  

         

        Regards

        Yoonas

        • 16. Re: Heartbeat failed to connect to standby . Error is 16058
          user10341747

          Please check the following points;

           

          1) check whether your listener is running on both primary and standby also restart the listeners once

          2) tnsping both primary and standby database on both the machine

          3) check log_archive_dest_2 on primary whether it is configured and enable

          4)check the passwordfile is created on standby. if not copy the password file from primary to standby and rename it.

           

          if above all are in place and working

           

          5) last option: restart the standby database

          • 17. Re: Heartbeat failed to connect to standby . Error is 16058
            User348341

            Hello All,

            So grateful for your response so far and also sorry for the late response.

            I slightly unbundled the standby database by removing all the datafiles and controlfiles. Then recopy these again from Primary Database.

             

            Afterwards, i am now facing different error which is as shown below:

             

            Error from Primary DB Alert Log

            computer name:/pcard18/admin/pcard/bdump>vi  /pcard18/admin/pcard/bdump/pcard_lns1_5984.trc
            LNS1: initialized successfully ASYNC=1
            Destination is specified with ASYNC=61440
            *** 2014-04-25 05:24:05.679 74846 kcrr.c
            Sending online log thread 1 seq 3078 [logfile 1] to standby
            Redo shipping client performing standby login
            *** 2014-04-25 05:24:25.786
            *** 2014-04-25 05:24:25.786 68056 kcrr.c
            Logged on to standby successfully
            Client logon and security negotiation successful!
            Archiving to destination p_stdy ASYNC blocks=20480
            Allocate ASYNC blocks: Previous blocks=0 New blocks=20480
            Log file opened [logno 1]
            *** 2014-04-25 05:29:23.858
            *** 2014-04-25 05:29:23.858 74846 kcrr.c
            Sending online log thread 1 seq 3079 [logfile 2] to standby
            Archiving to destination p_stdy ASYNC blocks=20480
            Log file opened [logno 2]
            *** 2014-04-25 05:41:02.850
            *** 2014-04-25 05:41:02.850 74846 kcrr.c
            Sending online log thread 1 seq 3080 [logfile 3] to standby
            Archiving to destination p_stdy ASYNC blocks=20480
            Log file opened [logno 3]
            *** 2014-04-25 05:55:59.977
            *** 2014-04-25 05:55:59.977 74846 kcrr.c
            Sending online log thread 1 seq 3081 [logfile 4] to standby
            Archiving to destination p_stdy ASYNC blocks=20480
            Log file opened [logno 4]
            *** 2014-04-25 05:58:21.009
            RFS network connection lost at host 'p_stdy'
            Error 3113 writing standby archive log file at host 'p_stdy'
            ORA-03113: Message 3113 not found; No message file for product=RDBMS, facility=ORA
            *** 2014-04-25 05:58:21.022 64213 kcrr.c
            LGWR: I/O error 3113 archiving log 4 to 'p_stdy'
            *** 2014-04-25 05:58:21.022 62481 kcrr.c
            kcrrfail: dest:2 err:3113 force:0 blast:1
            *** 2014-04-25 21:10:48.121
            *** 2014-04-25 21:10:48.121 74846 kcrr.c
            Sending online log thread 1 seq 3082 [logfile 5] to standby
            Redo shipping client performing standby login
            *** 2014-04-25 21:11:08.246
            *** 2014-04-25 21:11:08.246 68056 kcrr.c
            Logged on to standby successfully
            Client logon and security negotiation successful!
            Archiving to destination p_stdy ASYNC blocks=20480
            Log file opened [logno 5]
            

             

            Error from Standby DB log

             

            /pcard18/admin/p_stdy/bdump/p_stdy_mrp0_3461.trc
            Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
            With the Partitioning, OLAP, Data Mining and Real Application Testing options
            ORACLE_HOME = /oracle/product/10.2.0
            System name:    Linux
            Node name:      pwcd-stage-dr
            Release:        2.6.9-11.ELsmp
            Version:        #1 SMP Fri May 20 18:26:27 EDT 2005
            Machine:        i686
            Instance name: p_stdy
            Redo thread mounted by this instance: 1
            Oracle process number: 19
            Unix process pid: 3461, image: oracle@pwcd-stage-dr (MRP0)
            
            
            *** 2014-04-25 21:03:10.170
            Warning: keltnfy call to ldmInit failed with error 46
            *** SERVICE NAME:() 2014-04-25 21:03:10.171
            *** SESSION ID:(206.1) 2014-04-25 21:03:10.171
            ARCH: Connecting to console port...
            *** 2014-04-25 21:03:10.171 64213 kcrr.c
            MRP0: Background Managed Standby Recovery process started
            *** 2014-04-25 21:03:15.171 1180 krsm.c
            Managed Recovery: Initialization posted.
            *** 2014-04-25 21:03:15.171 64213 kcrr.c
            Managed Standby Recovery not using Real Time Apply
            *** 2014-04-25 21:03:15.172 64213 kcrr.c
            MRP0: Background Media Recovery terminated with error 264
            ORA-00264: Message 264 not found; No message file for product=RDBMS, facility=ORA
            *** 2014-04-25 21:03:15.172 1180 krsm.c
            Managed Recovery: Not Active posted.
            ORA-00264: Message 264 not found; No message file for product=RDBMS, facility=ORA
            ARCH: Connecting to console port...
            *** 2014-04-25 21:03:15.172 64213 kcrr.c
            MRP0: Background Media Recovery process shutdown
            *** 2014-04-25 21:03:15.172 1180 krsm.c
            

             

            Please, kindly advise.

            • 18. Re: Heartbeat failed to connect to standby . Error is 16058
              User348341

              Hello All,

              Does the above really mean a network issue

              • 19. Re: Heartbeat failed to connect to standby . Error is 16058
                yoonas

                Hi,

                1. RFS network connection lost at host 'p_stdy' 
                2. Error 3113 writing standby archive log file at host 'p_stdy' 

                That's what the above error says

                 

                See MOS notes

                ORA-03113 on Unix - What Information to Collect(Doc ID 17613.1)

                Master Note: Troubleshooting ORA-03113 (Doc ID 1506805.1)

                 

                Regards

                Yoonas

                1 2 Previous Next