Ora 12154 error

Question

I recently deploy one web application in one of my development servers. I\'m using oracle, asp.net and c#. When I run the application in the server everything works fine, bu

Answer 1

Resolving TNS errors can be a real pain. A few things to keep in mind.

Most development environments (like visual studio) keep their own copy of the TNS connection information, and do not use the TNSNAMES.ora file. The file where this information is kept does not have to be called TNSNAMES.ora, that's just the default name. Which may be the reason you can't find it on Server B.

If you have the oracle client software (or an oracle database) you can use tnsping to check if your TNSNAMES.ora file is configured correctly.

The most frequent problems with a TNSNAMES.ora file configuration are using the wrong service name and/or using the wrong host name. You may need to change the "ODB_A" to "ODB_A.WORLD" or vice versa, depending upon the SQLNET settings. For Oracle 10, the latter is the default SQLNET setting. For the latter, you need to use ping to see server "A", and know if you need to use "SERVERA" or "SERVERA.DOMIN.COM" or an IP address.

Answer 2

Add the environment:

Variable Name: TNS_ADMIN

Variable Value: (YourDrive):\app\(UserName)\product\11.2.0\dbhome_1\NETWORK\ADMIN

Answer 3

Is ORACLE_HOME set on server B?

Answer 4

Have you tried this yet? (from http://ora-12154.ora-code.com/)

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.

Answer 5

It seems you need to install Oracle Client on "Server B" (the application server), and configure it's TNSNAMES.ORA file. This is required since otherwise, the running code will have no idea where to look for the database you use in the application (probably you're configured a data source in web.config or hard-coded something). Remember - you cannot access Oracle (easily) without Oracle Client.

Answer 6

Possible Resolutions -

Verify that the TNSNAMES.ORA exists and is accessible.

Make sure that there are no syntax errors in TNSNAMES.ORA.

Verify that the connection string is correct.

Verify if there are any DNS issues.

If the problem is while connect to server using PL sql developer client.try to install SQL developer within Program File instead of Program Files(x86)'s