db instance not able to connect from sqlplus [message #344933] |
Mon, 01 September 2008 22:54 |
varunvir
Messages: 389 Registered: November 2007
|
Senior Member |
|
|
Hi,
I created third database instance on my production server.I am trying to connect it through sqlplus but it is giving me
ora-12154.I checked the tnsnames.It is fine.Listener.ora is not showing the entry of new database instance.When i am using status comand at lsnrctl,it is also not showing new instance name.What can i do to work it out.
Regards,
Varun Punj,
|
|
|
Re: db instance not able to connect from sqlplus [message #344934 is a reply to message #344933] |
Mon, 01 September 2008 22:55 |
|
BlackSwan
Messages: 26766 Registered: January 2009 Location: SoCal
|
Senior Member |
|
|
http://www.orafaq.com/forum/t/88153/0/
Please read & FOLLOW the Posting Guidelines as stated in URL above
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.
[Updated on: Mon, 01 September 2008 22:57] by Moderator Report message to a moderator
|
|
|
|
Re: db instance not able to connect from sqlplus [message #345260 is a reply to message #345184] |
Tue, 02 September 2008 14:29 |
joy_division
Messages: 4963 Registered: February 2005 Location: East Coast USA
|
Senior Member |
|
|
varunvir wrote on Tue, 02 September 2008 10:21 | Hi
I had checked the Tnsnames.ora and nothing is wrong with that.sqlnet.ora is perfect too.Is it possible that issue is due to listener because I dont see entries of new instance in listener.ora.
|
Yes, you have to put the entries into the listener.ora file too. Unless you are connection from that server, you do not need the entries in the tnsnames.ora file.
Remember to bounce the listener after you have made changes to the file.
|
|
|
|
|
|