Home » Server Options » Data Guard » Error 12154 received logging on to the standby (split from hijacked topic)
Error 12154 received logging on to the standby (split from hijacked topic) [message #674362] Wed, 23 January 2019 00:43 Go to next message
gerardachrist
Messages: 1
Registered: January 2019
Junior Member
Hi,

I'm facing the same kinda issue but with different error code on my Primary DB.

Error 12154 received logging on to the standby
Wed Jan 23 01:30:11 2019
Error 12154 received logging on to the standby
Wed Jan 23 01:31:11 2019


We had a network outage on our primary DB server side, and post that issue rectified by DG broker went out for a stroll. Till now I'm unable to bring up the DG broker to a persistent state.

But before that I need to initially resolve the DR Sync issue.

Kindly help me resolve the same. Request your kind advice on urgent basis.
Re: PING[ARCX]: Heartbeat failed to connect to standby 'XXX'. Error is 1034 [message #674363 is a reply to message #674362] Wed, 23 January 2019 00:45 Go to previous messageGo to next message
Michel Cadot
Messages: 66719
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
ORA-12154: TNS:could not resolve the connect identifier specified
 *Cause:  A connection to a database or other service was requested using
 a connect identifier, and the connect identifier specified could not
 be resolved into a connect descriptor using one of the naming methods
 configured. For example, if the type of connect identifier used was a
 net service name then the net service name could not be found in a
 naming method repository, or the repository could not be
 located or reached.
 *Action:
   - If you are using local naming (TNSNAMES.ORA file):
      - Make sure that "TNSNAMES" is listed as one of the values of the
        NAMES.DIRECTORY_PATH parameter in the Oracle Net profile
        (SQLNET.ORA)
      - Verify that a TNSNAMES.ORA file exists and is in the proper
        directory and is accessible.
      - Check that the net service name used as the connect identifier
        exists in the TNSNAMES.ORA file.
      - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA
        file.  Look for unmatched parentheses or stray characters. Errors
        in a TNSNAMES.ORA file may make it unusable.
   - If you are using directory naming:
      - Verify that "LDAP" is listed as one of the values of the
        NAMES.DIRETORY_PATH parameter in the Oracle Net profile
        (SQLNET.ORA).
      - Verify that the LDAP directory server is up and that it is
        accessible.
      - Verify that the net service name or database name used as the
        connect identifier is configured in the directory.
      - Verify that the default context being used is correct by
        specifying a fully qualified net service name or a full LDAP DN
        as the connect identifier
   - If you are using easy connect naming:
      - Verify that "EZCONNECT" is listed as one of the values of the
        NAMES.DIRETORY_PATH parameter in the Oracle Net profile
        (SQLNET.ORA).
      - Make sure the host, port and service name specified
        are correct.
      - Try enclosing the connect identifier in quote marks.

   See the Oracle Net Services Administrators Guide or the Oracle
   operating system specific guide for more information on naming.
Re: PING[ARCX]: Heartbeat failed to connect to standby 'XXX'. Error is 1034 [message #674364 is a reply to message #674362] Wed, 23 January 2019 01:18 Go to previous messageGo to next message
akbardba
Messages: 3
Registered: January 2019
Junior Member
yes i do that copy from one machine to another machine
Re: Error 12154 received logging on to the standby (split from hijacked topic) [message #674365 is a reply to message #674362] Wed, 23 January 2019 03:01 Go to previous message
John Watson
Messages: 8077
Registered: January 2010
Location: Global Village
Senior Member
You need to show the log_archive_dest_% parameters you have set and your tnsnames.ora files.

And, to do the moderator bit:

Welcome to the forum. Please read the OraFAQ Forum Guide and How to use code tags and make your code easier to read
Previous Topic: DATAGUARD SWITCHOVER_STATUS -------------------- NOT ALLOWED
Next Topic: ORA-00257 archiver error. Connect internal only until freed
Goto Forum:
  


Current Time: Mon Dec 09 18:41:38 CST 2019