OSN Error Messages (ORA-12150 to 12195)

Cause:	Unable to send data. Connection probably disconnected.

Action:	Re-establish 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:	Re-establish 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:	Re-establish connection.

ORA-12154 TNS:Could not resolve service name

Cause:	The service name specified is not defined in the TNSNAMES.ORA file.

Action:	Make the following checks and correct the error:

• Verify that a TNSNAMES.ORA file exists and is in the proper place and accessible. See the operating system specific manual for details on the required name and location.

• Check to see that the service name exists in one of the TNSNAMES.ORA files and add it if necessary.

• Make sure there are no syntax errors anywhere in the file. Particularly look for unmatched parentheses or stray characters. Any error in a TNSNAMES.ORA file makes it unusable. See Chapter 4 in the SQL*Net Administrator's Guide. If possible regenerate the configuration files using the Oracle Network Manager.

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 the DBA to get the proper permissions or use TRACE_DIRECTORY_CLIENT in SQLNET.ORA to specify a directory the user can write to.

ORA-12160 TNS:Internal error: Bad error number

Cause:	Corrupt error reporting subsystem.

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-12161 TNS:Internal error: partial data received

Cause:	The connection may be terminated.

Action:	Reconnect and try again. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

ORA-12162 TNS:service name is incorrectly specified

Cause:	The connect descriptor corresponding to the service name in TNSNAMES.ORA is incorrectly specified.

Action:	Make sure there are no syntax errors in the connect descriptor. Particularly look for unmatched parentheses or stray characters. Any error in the TNSNAMES.ORA file makes it unusable. See the SQLNet V2 Administrator's Guide.

ORA-12163 TNS:Connect descriptor is too long.

Cause:	The connect descriptor corresponding to the service name in TNSNAMES.ORA is too long.

Action:	The maximum length for a connect descriptor is 512 bytes and this limit has been exceeded. Use a smaller connect descriptor. If this is not possible, contact Worldwide Customer Support.

ORA-12164 TNS:sqlnet.fdf file not present

Cause:	The sqlnet.fdf file doesn't exist in $ORACLE_HOME/network/admin.

Action:	The sqlnet.fdf file is required for Oracle Tracing to occur. Either install the sqlnet.fdf file in $ORACLE_HOME/network/admin or turn off tracing in your ORA file.

ORA-12165 TNS:Trying to write trace file into swap space

Cause:	Oracle Trace doesn't allow writing trace information into your swap space.

Action:	Oracle Trace cannot write trace information into swap space so either disable tracing or redirect trace files to be written to another area of your disk.

ORA-12166 TNS:client cannot connect to HO agent

Cause:	NVstring contained DESCRIPTION/HO.

Action:	Call HO agent from integrating server.