Home » RDBMS Server » Networking and Gateways » TNS Could not Found (PeopleSoft,winsows server 2003,)
TNS Could not Found [message #588496] Wed, 26 June 2013 04:27 Go to next message
samisoomro
Messages: 1
Registered: June 2013
Location: Hyderabad
Junior Member
hi i am working on people-soft, currently i am installing it but i found this error

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

/*---------------------------------------------*/
this is listener.ora
# listener.ora Network Configuration File: C:\oracle\product\10.2.0\db\network\admin\listener.ora
# Generated by Oracle configuration tools.

HRCS9 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = umhs-86cd1970f)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
)
)

SID_LIST_HRCS9 =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = C:\oracle\product\10.2.0\db)
(PROGRAM = extproc)
)
)

/*---------------------------------------------*/
tnsnames.ora
# tnsnames.ora Network Configuration File: C:\oracle\product\10.2.0\db\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.

HRCS9 =
(DESCRIPTION =

(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = umhs-86cd1970f)(PORT = 1521))

)

(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
)
)
/*----------------------------------------------------*/
sqlnet.ora
# This file is actually generated by netca. But if customers choose to
# install "Software Only", this file wont exist and without the native
# authentication, they will not be able to connect to the database on NT.

SQLNET.AUTHENTICATION_SERVICES = (NTS)

/*--------------------------------------------------------*/
sir these are my files how can i manage resolved it.
thanks





Re: TNS Could not Found [message #588502 is a reply to message #588496] Wed, 26 June 2013 05:09 Go to previous message
Michel Cadot
Messages: 58612
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.

Regards
Michel
Previous Topic: ORACLE DG4ODBC DETAILS
Next Topic: Erratic TNS behavior-errors
Goto Forum:
  


Current Time: Tue Jul 29 13:22:43 CDT 2014

Total time taken to generate the page: 0.05691 seconds