Database Error Messages

A connection to a database or other service is being requested using a connection alias but the alias specified cannot be resolved into a connect descriptor using one of the configured naming methods.

Do the following:

• Check for mistakes in the connection string that you used.
• If you have a sqlnet.ora file containing a NAMES.DIRECTORY_PATH parameter, then ensure that the parameter contains valid values.
• If you are using an alias from a tnsnames.ora file:
• Verify that the tnsnames.ora file exists, is in the proper directory, and is accessible.
• Ensure that the alias exists in one of the tnsnames.ora files.
• Ensure that there are no syntax errors anywhere in the tnsnames.ora file or files. Look for unmatched parentheses or stray characters. Ensure that magic quotes are not used.
• If you are using LDAP directory naming:
• Verify that the net service name or database name used as the connect identifier is configured in the directory.
• Verify that the LDAP directory server is up and that it is accessible.
• 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 the error is for a dblink connection, check all of the above for Database Server process making connection to remote database.

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.

• 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.

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.

• 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.