Saturday, 25 February 2012

ORA-12157: TNS:internal network communication error

ORA-12157: TNS:internal network communication error

Cause: Internal error during network communication.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

ORA-12156: TNS:tried to reset line from incorrect state

ORA-12156: TNS:tried to reset line from incorrect state

Cause: Internal error during break handling.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

ORA-12155: TNS:received bad datatype in NSWMARKER packet

ORA-12155: TNS:received bad datatype in NSWMARKER packet

Cause: Internal error during break handling.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

ORA-12154: TNS:could not resolve the connect identifier specified

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) accessible. 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). is configured in the directory. 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). Administrators Guide or the Oracle operating system specific guide for more information on naming.

ORA-12153: TNS:not connected

ORA-12153: TNS:not connected

Cause: Not currently connected to a remote host.

Action: Reestablish connection.

ORA-12152: TNS:unable to send break message

ORA-12152: TNS:unable to send break message

Cause: Unable to send break message. Connection probably disconnected.

Action: Reestablish connection. If the error is persistent, turn on tracing and reexecute the operation.

ORA-12151: TNS:received bad packet type from network layer

ORA-12151: TNS:received bad packet type from network layer

Cause: Internal error.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.