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.

ORA-12150: TNS:unable to send data

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-09859: sfngat: the input file name is not in the autobackup OMF format

ORA-09859: sfngat: the input file name is not in the autobackup OMF format

Cause: The function sfngat() received a filename which is not an autobackup OMF file name.

Action: Further diagnostic information should be in the error stack.

ORA-09858: sfngat: the input file name is not in the OMF format

ORA-09858: sfngat: the input file name is not in the OMF format

Cause: The function sfngat() received a filename which is not an OMF file name.

Action: Further diagnostic information should be in the error stack.

ORA-09857: smprset: vm_protect error while protecting pga.

ORA-09857: smprset: vm_protect error while protecting pga.

Cause: The vm_protect system call returned an error.

Action: Internal error. Contact Oracle support.

ORA-09856: smpalo: vm_allocate error while allocating pga.

ORA-09856: smpalo: vm_allocate error while allocating pga.

Cause: The vm_allocate system call returned an error.

Action: Check returned error. Possibly out of system resources.

ORA-09855: removeCallback: bad message format.

ORA-09855: removeCallback: bad message format.

Cause: The routine received an incorrectly formatted request.

Action: Internal error. Contact Oracle support.

ORA-09854: snyPortInfo: bad return code from request.

ORA-09854: snyPortInfo: bad return code from request.

Cause: The request to collect info on a port in the callback set returned a failure code.

Action: Possible operating system error. Contact Oracle support.

ORA-09853: snyRemovePort: bad return code from request.

ORA-09853: snyRemovePort: bad return code from request.

Cause: The request to remove a port from the callback set returned a failure code.

Action: Possible operating system error. Contact Oracle support.

ORA-09851: soacon: Archmon unable to lock named pipe.

ORA-09851: soacon: Archmon unable to lock named pipe.

Cause: fcntl() failed to set read lock on named pipe ? or dbs or mon2arch_.

Action: Make sure that archmon is not already active on another terminal for this ORACLE_SID. Only one archmon session is allowed at a time for a given instance.

ORA-09850: soacon: Archmon unable to lock named pipe.

ORA-09850: soacon: Archmon unable to lock named pipe.

Cause: fcntl() failed to set write lock on named pipe ? or dbs or arch2mon_.

Action: Make sure that archmon is not already active on another terminal for this ORACLE_SID. Only one archmon session is allowed at a time for a given instance.

ORA-09847: soacon: ARCH unable to open named pipe.

ORA-09847: soacon: ARCH unable to open named pipe.

Cause: open() failed to open named pipe ? or dbs or arch2mon_.

Action: Make sure that the OS userid of the currently running database has search permission for the ORACLE_HOME or dbs directory. The max number of open files may have been exceeded.

ORA-09846: soacon: ARCH unable to open named pipe.

ORA-09846: soacon: ARCH unable to open named pipe.

Cause: open() failed to open named pipe ? or dbs or mon2arch_.

Action: Make sure that the OS userid of the currently running database has search permission for the ORACLE_HOME or dbs directory. The max number of open files may have been exceeded.

ORA-09845: soacon: Archmon unable to open named pipe.

ORA-09845: soacon: Archmon unable to open named pipe.

Cause: open() failed to open named pipe ? or dbs or arch2mon_.

Action: Only the oracle dba can run archmon. Make sure that your current OS login has owner or group search permission for the ORACLE_HOME or dbs directory. The max number of open files may have been exceeded.

ORA-09844: soacon: Archmon unable to open named pipe.

ORA-09844: soacon: Archmon unable to open named pipe.

Cause: open() failed to open named pipe ? or dbs or mon2arch_.

Action: Only the oracle dba can run archmon. Make sure that your current OS login has owner or group search permission for the ORACLE_HOME or dbs directory. The max number of open files may have been exceeded.

ORA-09843: soacon: Archmon unable to create named pipe.

ORA-09843: soacon: Archmon unable to create named pipe.

Cause: mknod() failed to create named pipe ? or dbs or arch2mon_.

Action: Your current OS login may lack write permission for the ORACLE_ HOME or dbs directory. Only userids in the dba group of a given instance can run archmon for that ORACLE_SID. Make sure that the ORACLE_HOME directory is correct in oratab.

ORA-09842: soacon: Archmon unable to create named pipe.

ORA-09842: soacon: Archmon unable to create named pipe.

Cause: mknod() failed to create named pipe ? or dbs or mon2arch_.

Action: Your current OS login may lack write permission for the ORACLE_ HOME or dbs directory. Only userids in the dba group of a given instance can run archmon for that ORACLE_SID. Make sure that the ORACLE_HOME directory is correct in oratab.

ORA-09841: soacon: Name translation failure.

ORA-09841: soacon: Name translation failure.

Cause: sltln() could not translate the named pipe ? or dbs or arch2mon_.

Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID in oratab is correct.

ORA-09840: soacon: Name translation failure.

ORA-09840: soacon: Name translation failure.

Cause: sltln() could not translate the named pipe ? or dbs or mon2arch_.

Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID in oratab is correct.

ORA-09839: removeCallback: callback port is not in the callback set.

ORA-09839: removeCallback: callback port is not in the callback set.

Cause: The port to be removed to the callback list is not in the callback port set.

Action: Internal error. Contact Oracle support.

ORA-09838: removeCallback: failure removing the callback port.

ORA-09838: removeCallback: failure removing the callback port.

Cause: The port port_set_remove system call failed.

Action: Possible operating system error. Contact Oracle support.

ORA-09837: addCallback: could not add allocate a callback link.

ORA-09837: addCallback: could not add allocate a callback link.

Cause: The malloc library call failed to allocate space for a callback link.

Action: Possible operating system error. Contact Oracle support.

ORA-09836: addCallback: could not add a port to the callback set.

ORA-09836: addCallback: could not add a port to the callback set.

Cause: The port_set_add system called failed.

Action: Possible operating system error. Contact Oracle support.

ORA-09835: addCallback: callback port is already in a set.

ORA-09835: addCallback: callback port is already in a set.

Cause: The port to be added to the callback list is already in a port set.

Action: Internal error. Contact Oracle support.

ORA-09834: snyGetPortSet: failed to collect info on a port.

ORA-09834: snyGetPortSet: failed to collect info on a port.

Cause: The port_status system called failed.

Action: Possible operating system error. Contact Oracle support.

ORA-09833: addCallback: bad message format.

ORA-09833: addCallback: bad message format.

Cause: The routine received an incorrectly formatted request.

Action: Internal error. Contact Oracle support.

ORA-09832: infoCallback: bad message format.

ORA-09832: infoCallback: bad message format.

Cause: The routine received an incorrectly formatted request.

Action: Internal error. Contact Oracle support.

ORA-09831: snyStartThread: failed to build the server port set.

ORA-09831: snyStartThread: failed to build the server port set.

Cause: The routine failed to build a port set on which to listen for requests.

Action: Possible operating system failure. Contact Oracle support.

ORA-09830: snyAddPort: failed to perform a remote procedure call.

ORA-09830: snyAddPort: failed to perform a remote procedure call.

Cause: The msg_rpc system call returned an error.

Action: Internal error. Contact Oracle support.

ORA-09829: pw_createPorts: server call pws_start_instance failed.

ORA-09829: pw_createPorts: server call pws_start_instance failed.

Cause: The call pws_start_instance to (Oracle helper) failed; system resources might be exhausted.

Action: Make sure the server is still active. Check the error code returned in sercerrno, and look for error messages in the server log file.

ORA-09828: SCLFR: atomic latch return error.

ORA-09828: SCLFR: atomic latch return error.

Cause: System call atomic_op() return unexpected error.

Action: Check additional information in the trace file.

ORA-09827: sclgt: atomic latch return unknown error.

ORA-09827: sclgt: atomic latch return unknown error.

Cause: System call atomic_op() return unexpected error.

Action: Check additional information in the trace file.

ORA-09826: SCLIN: cannot initialize atomic latch.

ORA-09826: SCLIN: cannot initialize atomic latch.

Cause: System call atomic_op() return error.

Action: Check additional information in the trace file.

ORA-09825: Unable to disable allowmacaccess privilege.

ORA-09825: Unable to disable allowmacaccess privilege.

Cause: ORACLE was not able to turn off the allowmacaccess privilege after doing a label comparison.

Action: This is an internal error. Contact Oracle Support Services.

ORA-09824: Unable to enable allowmacaccess privilege.

ORA-09824: Unable to enable allowmacaccess privilege.

Cause: ORACLE was not able to turn on allowmacaccess privilege so that it could do a label comparison.

Action: Check the UNIX error number. If it indicates that ORACLE does not have the allowmacaccess privilege, add the allowmacaccess privilege to the potential privilege set of $ORACLE_HOME or bin or oracle using chpriv (1M). If the executable already has the allowmacaccess privilege, contact Oracle Support Services.

ORA-09823: device name is too long

ORA-09823: device name is too long

Cause: The name of a device was too long to fit into an internal buffer. The additional information field contains the length of the device name.

Action: This is an internal error. Contact Oracle Support Services.

ORA-09822: Translation of audit file name failed.

ORA-09822: Translation of audit file name failed.

Cause: Oracle was unable to translate the value of the AUDIT_FILE_DEST initialization parameter.

Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.

ORA-09821: Numeric label is not valid

ORA-09821: Numeric label is not valid

Cause: A label specified in ORACLE numeric format was found not to be valid.

Action: Re-enter a valid label. Consult your system s encodings for valid numeric component values.

ORA-09820: Conversion of class string to numeric representation failed.

ORA-09820: Conversion of class string to numeric representation failed.

Cause: ORACLE was unable to convert a class string to a number because all of the characters in the string were not numeric.

Action: Change the string to be either all numbers or all non-numeric characters and repeat the conversion.

ORA-09819: Number exceeds maximum legal value

ORA-09819: Number exceeds maximum legal value

Cause: the number specified for a component was greater than the maximum value allowed for that component.

Action: Change the component to a value less than the maximum and repeat the conversion. The maximum component number is contained in the Additional information field.

ORA-09818: Number is too large

ORA-09818: Number is too large

Cause: ORACLE was unable to convert a component string to a number because the number is larger than the largest possible value for an integer. The additional information field specifies the maximum.

Action: Correct the string and repeat the conversion.

ORA-09817: Write to audit file failed.

ORA-09817: Write to audit file failed.

Cause: ORACLE was unable to write an entry to the file used as the audit trail.

Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.

ORA-09815: File name buffer overflow

ORA-09815: File name buffer overflow

Cause: The buffer that ORACLE uses to hold the expanded name of a too small.

Action: This is an internal error. Contact Oracle Support Services.

ORA-09814: Unable to expand file name

ORA-09814: Unable to expand file name

Cause: ORACLE was unable to expand the name of a file that resides in multilevel directory.

Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.

ORA-09813: Unable to get directory status

ORA-09813: Unable to get directory status

Cause: ORACLE was unable to determine if a directory is multilevel.

Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.

ORA-09812: Unable to get user clearance from connection

ORA-09812: Unable to get user clearance from connection

Cause: ORACLE was unable to retrieve the user s operating system session clearance from the SQL*Net connection.

Action: Check the UNIX error number for a possible operating system error. Also check the additional information field for the SQL*Net error. If there is no error, contact Oracle Support Services.

ORA-09811: Unable to initialize package.

ORA-09811: Unable to initialize package.

Cause: ORACLE was unable to initialize the library used to obtain security information.

Action: This is an internal error. Contact Oracle Support Services.

ORA-09810: Unable to get process ID from connection

ORA-09810: Unable to get process ID from connection

Cause: ORACLE was unable to retrieve the user s process ID number from the SQL*Net connection.

Action: Check the UNIX error number for a possible operating system error. Also check the additional information field for the SQL*Net error. If there is no error, contact Oracle Support Services.

ORA-09809: Unable to get user s group ID from connection

ORA-09809: Unable to get user s group ID from connection

Cause: ORACLE was unable to retrieve the user s group ID number from the SQL*Net connection.

Action: Check the UNIX error number for a possible operating system error. Also check the additional information field for the SQL*Net error. If there is no error, contact Oracle Support Services.

ORA-09808: Could not obtain user clearance.

ORA-09808: Could not obtain user clearance.

Cause: ORACLE was unable to get a user s clearance level.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.

ORA-09807: Conversion of label from string to binary failed.

ORA-09807: Conversion of label from string to binary failed.

Cause: ORACLE was unable to convert the string representation of a label to binary format.

Action: Re-enter a valid label.

ORA-09806: Allocation of label string buffer failed.

ORA-09806: Allocation of label string buffer failed.

Cause: a temporary buffer used to hold a label could not be allocated.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. The number of bytes that ORACLE attempted to allocate is in the Additional Information field.

ORA-09805: conversion of category number to string failed.

ORA-09805: conversion of category number to string failed.

Cause: ORACLE was unable to translate a category number to its corresponding string representation failed.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. The category number is contained in the Additional information field.

ORA-09804: Class conversion from binary to ORACLE failed.

ORA-09804: Class conversion from binary to ORACLE failed.

Cause: ORACLE was unable to convert a class component from binary format to ORACLE format.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.