分享一下我老师大神的人工智能教程!零基础,通俗易懂!http://blog.csdn.net/jiangjunshow
也欢迎大家转载本篇文章。分享知识,造福人民,实现我们中华民族伟大复兴!
ORA-12150 to ORA-12236 9
ORA-12150: TNS:unable to send data
Cause: Unable to send data. 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
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.
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-12153: TNS:not connected
Cause: Not currently connected to a remote host.
Action: Reestablish connection.
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.
9-2 Oracle Database Error Messages
- 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.
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-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-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-12158: TNS:could not initialize parameter subsystem
Cause: Unable to locate parameter file.
Action: Verify that a valid parameter file exists, and is readable.
ORA-12159: TNS:trace file not writeable
Cause: The trace file to be generated is not writeable by this user.
Action: If the user does not have write permissions in the directory to which the
trace file will be written, contact an administrator to get the proper permissions or
set the TRACE_DIRECTORY_CLIENT parameter in the net profile (SQLNET.ORA
file) to a directory the user can write to.
ORA-12160: TNS:internal error: Bad error number
Cause: C
ORA-12150: TNS:unable to send data
Cause: Unable to send data. 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
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.
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-12153: TNS:not connected
Cause: Not currently connected to a remote host.
Action: Reestablish connection.
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.
9-2 Oracle Database Error Messages
- 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.
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-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-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-12158: TNS:could not initialize parameter subsystem
Cause: Unable to locate parameter file.
Action: Verify that a valid parameter file exists, and is readable.
ORA-12159: TNS:trace file not writeable
Cause: The trace file to be generated is not writeable by this user.
Action: If the user does not have write permissions in the directory to which the
trace file will be written, contact an administrator to get the proper permissions or
set the TRACE_DIRECTORY_CLIENT parameter in the net profile (SQLNET.ORA
file) to a directory the user can write to.
ORA-12160: TNS:internal error: Bad error number
Cause: C