.ORA-12154 ERROR [message #686126] |
Sun, 19 June 2022 11:44  |
 |
gladiator208
Messages: 4 Registered: June 2022
|
Junior Member |
|
|
I installed oracle database 12c with no problems.
I installed Forms 12C with no installation problems.
When I try to start FORM BUILDER, the first message that comes up is FRM-18122: Oracle Forms Debugger failed to initialize.
I click on OK and the message goes away.
When I click on Data Blocks, and create a new data block, I try to connect to the database, I get the message ORA-12154: TNS:could not resolve the connect identifier specified.
I am enclosing a file with the locations on where everything was installed.
Also, the TNSNAMES.ORA, LISTENER.ORA, SQLNET.ORA file for your review to try to help me.
|
|
|
Re: .ORA-12154 ERROR [message #686127 is a reply to message #686126] |
Sun, 19 June 2022 12:32  |
 |
Michel Cadot
Messages: 68453 Registered: March 2007 Location: Nanterre, France, http://...
|
Senior Member Account Moderator |
|
|
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.
Quote:tnsnames.ora Network Configuration File: J:\ORACEL21C_DATABASE\homes\OraDB21Home3\NETWORK\ADMIN\tnsnames.ora
Quote:sqlnet.ora Network Configuration File: J:\ORACEL21C_DATABASE\homes\OraDB21Home3\NETWORK\ADMIN\sqlnet.ora
Quote:TNS_ADMIN
C:\ORACEL21C_DATABASE\homes\OraDB21Home3\network\admin
sqlnet.ora and tnsnames.ora should be located in the directory given by TNS_ADMIN variable (or the opposite TNS_ADMIN should be set to the files directory).
|
|
|