469,150 Members | 1,951 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,150 developers. It's quick & easy.

URGENT help needed!! TNS issue

Hi all

I need help urgently as I am in the middle of a migration and can't resolve a TNS error.

My db has been fine for months! Today I connected as sysdba and shut down the db. Now I am trying to bring it back up but when i try connect as sysdba I get ORA-12154: TNS:could not resolve service name

This is odd because I have not changed the tnsnames file at all. Please help

Am I missing something simple here?

Oh the tns listener service is running as well

Thanks alot
Oct 1 '06 #1
2 2759
LaoDe
9
Hi,

you may have a path problem, according to the new oracle version. check ind what path oracle is looking for tnsnames.

Also the global dbname may have changed in the init<sid> some days ago. this takes effect while rebooting.

just go step by step and compare above parameter to listener.ini and tnsnames and path and I'm sure you have access to your db again.

LaoDe
Oct 2 '06 #2
Hi!

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.


By
Captain
Oct 9 '06 #3

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

1 post views Thread by David | last post: by
2 posts views Thread by Ken Baltrinic | last post: by
1 post views Thread by vp | last post: by
3 posts views Thread by N. Spiker | last post: by
reply views Thread by FAS | last post: by
2 posts views Thread by dragonball | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by zhoujie | last post: by
1 post views Thread by Mortomer39 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.