7 Replies Latest reply: Nov 18, 2012 1:07 AM by user3714906 RSS

    Error 12154 received logging on to the standby

    user3714906
      Hi,

      We have standby for our production database,
      since yesterday, we are getting below error in alert log file of production and the redo's are not getting shipped

      Error 12154 received logging on to the standby
      Sun Oct 14 13:47:46 2012
      Error 12154 received logging on to the standby
      Sun Oct 14 13:48:46 2012
      Error 12154 received logging on to the standby
      Sun Oct 14 13:49:46 2012
      Error 12154 received logging on to the standby
      Sun Oct 14 13:50:46 2012
      Error 12154 received logging on to the standby
      Sun Oct 14 13:51:46 2012
      Error 12154 received logging on to the standby



      SQL> select error from v$archive_dest;

      ERROR
      -----------------------------------------------------------------

      ORA-12154: TNS:could not resolve the connect identifier specified


      I could tnsping the STANDBY from production

      Regards
        • 1. Re: Error 12154 received logging on to the standby
          mseberg
          Until you can do the following:

          sqlplus sys/password@Standby as sysdba (from the primary system)

          and

          sqlplus sys/password@primary as sysdba (from the standby system)

          You will not be able to ship redo. You have an error in your tnsnames and listener configuration.

          Most likely your tnsname is missing an entry or has an incorrect entry.

          Also see :

          Troubleshooting - Heartbeat failed to connect to standby [ID 1432367.1]
          ORA-12514 on ARCn-Process after changing TNS-Alias [ID 1367311.1]

          Common Causes

          LOG_ARCHIVE_DEST_2 pointing to a tnsnames.ora entry with incorrect SERVICE_NAME

          Listener setup for Data Guard incorrect

          tnsnames.ora missing entry or incorrect entry


          Best Regards

          mseberg
          • 2. Re: Error 12154 received logging on to the standby
            user3714906
            sqlplus sys/password@Standby as sysdba (from the primary system)

            and

            sqlplus sys/password@primary as sysdba (from the standby system)


            Both above strings works fine, but still redos are not getting shipped, I checked other things as well, but it looks ok

            In Prod alert log file, I see error
            Error 12154 received logging on to the standby
            Sun Oct 14 14:51:53 2012
            Errors in file /u01/oraprod/db/tech_st/10.2.0/admin/PROD_prod/bdump/prod_arc8_29206.trc:
            ORA-12154: TNS:could not resolve the connect identifier specified
            PING[ARC8]: Heartbeat failed to connect to standby 'STBY'. Error is 12154.
            but when I tnsping STBY, it is ok

            Please suggest

            Regards
            • 4. Re: Error 12154 received logging on to the standby
              JohnWatson
              OK, I'll try. You need to provide the following:

              The log_archive_dest_n parameters on the primary.
              The tnsnames.ora file on the primary (if you are using tnsnames for name resolution)
              the result of the tnspings
              The result of 'lsnrctl status' on the standby
              The service_names and local_listener parameters on the standby

              That may be enough to diagnose the problem. Or it may not be.
              • 5. Re: Error 12154 received logging on to the standby
                saurabh
                have you created the password file on the standby database. The following error is due to password file not present on the standby database. The password file should be same as primary so you can copy the password file from primary and paste on the standby and then check if it works.
                • 6. Re: Error 12154 received logging on to the standby
                  sanikv
                  this error means that it cannot resolve the connect string given in log_archive_dest_2, have you set NAMES.DEFAULT_DOMAIN in your sqlnet.ora ?
                  1) ensure that you are checking the correct tnsnames.ora, should be in $ORACLE_HOME/network/admin unless TNS_ADMIN is defined.
                  2) try suffixing the tns_alias with a domain name in log_archive_dest_2 and tnsnames.ora.
                  3) you can directly specify the connect string instead of alias in the parameter log_archive_dest_2, something like below ( if this works then you can confirm that the the issue is with tnsnames.ora)
                  alter system set log_archive_dest_2='SERVICE="(description=(address_list=(address=(protocol=TCP)(host=r00979)(port=1521)))(connect_data=(service_name=desk_std)))", LGWR ASYNC NOAFFIRM' scope=both;