2 Replies Latest reply: Apr 13, 2014 8:50 AM by Paul M. RSS

    oradim

    OABUEID

      dear All

      when I create the service by using oradim in CMD command

       

      oradim -new -sid PSH91DMO -intpwd manager -startmode auto -pfile C:\app\Administrator\product\11.2.0\dbhome_1\database\initPSH91DMO.ora


      every thing is ok but when I connect with cmd > sqlplus/nolog  and cnnect to the userid/passwrd@database I receive the message


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


      Best Regards

        • 1. Re: oradim
          Paul M.
          ORA-12154 TNS: could not resolve the connect identifier  specified

          $ oerr ora 12154

          12154, 00000, "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.

          $

          • 2. Re: oradim
            sb92075

            ORA-12154 ALWAYS only occurs on SQL Client & no SQL*Net packets ever leave client system

            ORA-12154 [B]NEVER[/B] involves the listener, the database itself or anything on the DB Server.

            ORA-12154 occurs when client requests a connection to some DB server system using some connection string.

            TNS-03505 is thrown by tnsping & is same error as ORA-12154 thrown by sqlplus or others.

            The lookup operation fails because the name provided can [B]NOT[/B] be resolved to any remote DB.

            The analogous operation would be when you wanted to call somebody, but could not find their name in any phonebook.

            The most frequent cause for the ORA-12154  error is when the connection alias can not be found in tnsnames.ora.

            The lookup operation of the alias can be impacted by the contents of the sqlnet.ora file; specifically DOMAIN entry.

            TROUBLESHOOTING GUIDE: ORA-12154 & TNS-12154 TNS:could not resolve service name [ID 114085.1]

            http://edstevensdba.wordpress.com/2011/02/26/ora-12154tns-03505/