Problem regarding Running Multiple Database in Oracle 9i (9.2.0.1)

Question

I am using Oracle 9i (9.2.0.1) version on Windows 2003 server. My database is ORCL. it is successfully running. Now I have create a new database as TEST, it is successfully created Now I can't connect on that database in sys and system user but i connect my previous database(ORCL) successfully.
message comes as : ORA : 12154, TNS could not resolve service name.
Plz give a solution.

Answer 1

Anil Malkai wrote:
Have you created password file?
can you post
dir %ORACLE_HOME/database
try this as well
set oracle_sid=test
sqlplus sys as sysdba
Anil MAlkaiNot only does it not have anything to do with the listener, it has nothing to do with the password file.
If you haven't looked recently, here is the full description AND ACTION LIST of the OP's error:
stevense> 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.Notice that there are two items which are NOT listed in the above. The first is any reference to the listener. The second is any reference to the password file. If you can't resolve the connect identifier (you can't find the number you are looking for in the telephone directory), then your inability to connect to the database (to place a telephone call) has nothing to do with the listener (the telephone company switchboard) or the password file (the other guy's secretary being willing to accept your call).