This content has been marked as final. Show 7 replies
you can try to put the actual IP of the machine in which the database resides instead of "localhost"
"ora-12154 tns could not resolve the connect identifier specified"The problem is local to the Forms Home, probably in tnsnames.ora (seems that there are tabs in IMS entry name). Carefully check it.
$ 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. $
Its Stand Alon machine which is not on network.
On a stand-alone (non-networked) computer, you need a network emulation. If you are using Windows, you can install the Microsoft Loopback Adapter (as noted in the Oracle Database Preinstallation Requirements see section *2.4.4 Installing Oracle Database on Non-Networked Computers*). If you are not using Windows - then you will need to find the equivalent for your OS.
Also, as Paul M indicated, each Oracle product is installed into it's own Oracle Home. If you have configured the TNSNAMES on the RDBMS, but not configured it for the Developer Suite (Forms 10g) then you will need to perform this configuration. The easiest way to do this is to set an Environment Variable (TNS_ADMIN) that points to the TNSNAMES.ORA you have already configured with your RDBMS. If you are unsure of how to create an environment variable, check out this: how to create environment variables.
Hope this helps,
If someone's response is helpful or correct, please mark it accordingly.
Are you able to connect using Form or Sql plus?
Make sure the TNS is right within
Have you started the DB?
Issue has been resolved by adding TNS_ADMIN variable there was another problem i was using system/manager to connect my forms with db that was the real problem as i have created the a user and try to connect it was connected with db
any way thanks a lot for great help.
It's not good to develop the form using system login. You can create other schema for the development