O2I-00120: Error reported by subsystem:

O2I-00120: Error reported by subsystem:

Cause: A subsystem invoked by OTT reported an error. This error immediately follows the Error reported by subsystem message.

Action: Examine the error message reported by the sybsystem to determine its cause.

O2I-00119: Warning reported by subsystem:

O2I-00119: Warning reported by subsystem:

Cause: A subsystem invoked by OTT reported a warning. This warning immediately follows the Warning reported by subsystem message.

Action: Examine the warning reported by the subsystem to determine its cause.

O2I-00118: This user-defined type was not found in the database

O2I-00118: This user-defined type was not found in the database

Cause: A user-defined type specified in the INTYPE file was not found in the database.

Action: Make sure the name of the type is spelled correctly. Make sure the type is actually declared in the database.

O2I-00117: Internal error: No message file for component O2U

O2I-00117: Internal error: No message file for component O2U

Cause: The message file for the internal OTT component O2U was not found. OTT may not be correctly installed.

Action: Contact ORACLE customer support.

O2I-00116: Unable to close the HFILE file

O2I-00116: Unable to close the HFILE file

Cause: An operating system error occurred while attempting to close the HFILE file.

Action: Try creating or modifying the HFILE file to make sure you are able to access the file.

O2I-00115: Error opening the HFILE file

O2I-00115: Error opening the HFILE file

Cause: An operating system error occurred while attempting to open the HFILE file for writing.

Action: Make sure the HFILE filename is spelled correctly. Try creating or modifying the HFILE to make sure you have write access to the file.

O2I-00114: Invalid HFILE file name

O2I-00114: Invalid HFILE file name

Cause: An HFILE file name was specified that is not syntactically correct.

Action: Make sure the HFILE filename is spelled correctly.

O2I-00113: No HFILE specified

O2I-00113: No HFILE specified

Cause: The HFILE file to which C declarations generated by OTT are written was not specified.

Action: Specify the global HFILE option on the command line or in a CONFIG file. You may choose a different HFILE for a particular type by specifying a different HFILE in the INTYPE file entry describing the type. If every INTYPE file entry specifies an HFILE, and if none of the types in the HFILE require declarations of types not mentioned there, the global HFILE option may be omitted. An INTYPE file generated by a previous invocation of OTT satisfies these conditions.

O2I-00112: Unable to write to the HFILE file

O2I-00112: Unable to write to the HFILE file

Cause: An operating system error occurred when attempting to write to the HFILE file.

Action: Make sure you have operating system permission to write to the file. Also, make sure disk space is available.

O2I-00111: Unable to allocate memory

O2I-00111: Unable to allocate memory

Cause: OTT was unable to allocate memory.

Action: Contact ORACLE customer support.

O2I-00110: Internal error in OTT component O2I

O2I-00110: Internal error in OTT component O2I

Cause: An internal OTT error occurred in the O2I component of OTT.

Action: Contact ORACLE customer support.

O2I-00103: Two file names refer to the same HFILE file in the INTYPE file

O2I-00103: Two file names refer to the same HFILE file in the INTYPE file

Cause: Two different file names have been used in the INTYPE file to refer to the same HFILE file, or different file names have been used to refer to the same HFILE file on the command line and in the INTYPE file.

Action: Consistently refer to each HFILE file using the same file name.

O2I-00102: Unable to connect to Oracle

O2I-00102: Unable to connect to Oracle

Cause: OTT could not connect to Oracle with the username, password, and, if applicable, database link that was supplied. Either the USERID option value was incorrect, or, if the USERID was not supplied, the userid OPS$lamp;lt;lamp;nbsp;usernamelamp;gt; was not accepted.

Action: Check that the username and password are current and correct. Run another program that connects to Oracle to verify that you can connect using that username and password.

NZE-28871: Peer certificate chain is incomplete.

NZE-28871: Peer certificate chain is incomplete.

Cause: The peer certificate chain presented was not complete because it did not end with a self-signed root certificate.

Action: Refer to Oracle Wallet Manager documentation to find out how to open your wallet and ensure that: 1. the certificate authority s certificate specified as the root is self-signed. 2. a certificate authority s certificate from your peer s certificate chain is added as a trusted certificate in your wallet

NZE-28870: Name comparison failure

NZE-28870: Name comparison failure

Cause: A comparison between the names contained within two certificates failed.

Action: This error is not normally visible to the user. Enable Oracle Net tracing and attempt the connection again. If the error persists, contact Oracle customer support.

NZE-28869: Peer s certificate is expired.

NZE-28869: Peer s certificate is expired.

Cause: The certificate being used to authenticate a client or server has expired.

Action: Obtain a new certificate, which has not expired, and attempt the connection again.

NZE-28868: Peer certificate chain check failed.

NZE-28868: Peer certificate chain check failed.

Cause: The check of the certificate list presented by the peer failed. This could be caused by a number of problems including: 1. the expiration of one of the certificates; 2. a certificate authority in a certificate was not recognized as a trust point; 3. the signature in a certificate could not be verified.

Action: Refer to Oracle Wallet Manager documentation to find out how to open your wallet and ensure that: 1. all of the certificates installed in your wallet are current 2. a certificate authority s certificate from your peer s certificate chain is added as a trusted certificate in your wallet

NZE-28867: Integer value is too big.

NZE-28867: Integer value is too big.

Cause: The certificate presented had an integer field whose value was too large.

Action: Refer to Oracle Wallet Manager documentation to find out how to obtain the peer s certificate. Then contact Oracle customer support with the peer s certificate chain.

NZE-28866: Invalid peer certificate encoding

NZE-28866: Invalid peer certificate encoding

Cause: A certificate in the peer s certificate chain had a field that could not be recognized.

Action: Refer to Oracle Wallet Manager documentation to find out how to obtain the peer s certificate. Then contact Oracle customer support with the peer s certificate chain.

NZE-28865: SSL connection closed

NZE-28865: SSL connection closed

Cause: The SSL connection closed because of an error in the underlying transport or because the peer process quit unexpectedly.

Action: Enable Oracle Net tracing and attempt the connection again. The trace output should indicate how the failure occurred.

NZE-28864: SSL connection closed gracefully

NZE-28864: SSL connection closed gracefully

Cause: This error is informational only. It indicates that the connection closed without error.

Action: This error is not normally visible to the user. Enable Oracle Net tracing and attempt the connection again. If the error persists, contact Oracle customer support.

NZE-28863: SSL session not found

NZE-28863: SSL session not found

Cause: This error is informational only. It indicates that a specified session does not exist.

Action: Enable Oracle Net tracing and attempt the connection again. Contact Oracle customer support with the trace output.

NZE-28862: SSL connection failed

NZE-28862: SSL connection failed

Cause: This error occurred because the peer closed the connection.

Action: Enable Oracle Net tracing on both sides and examine the trace output. Contact Oracle Customer support with the trace output.

NZE-28861: SSL connection would block

NZE-28861: SSL connection would block

Cause: This error is informational only. It should never be communicated to the user.

Action: Enable Oracle Net tracing and attempt the connection again. Then contact Oracle customer support with the trace output.

NZE-28860: Fatal SSL error

NZE-28860: Fatal SSL error

Cause: An error occurred during the SSL connection to the peer. It is likely that this side sent data which the peer rejected.

Action: Enable Oracle Net tracing on the peer and examine the trace output.

NZE-28859: SSL negotiation failure

NZE-28859: SSL negotiation failure

Cause: An error occurred during the negotiation between two processes as part of the SSL protocol. This error will occur if the two sides to the connection do not support a common cipher suite.

Action: Configure each process so they support a common cipher suite. Then attempt the connection again. If error occurs again enable Oracle Net tracing and attempt the connection again. Then contact Oracle customer support with the trace output.

NZE-28858: SSL protocol error

NZE-28858: SSL protocol error

Cause: An error occurred while negotiating the SSL handshake between two processes.

Action: This error is not normally visible to the user. Enable Oracle Net tracing and attempt the connection again. Then contact Oracle customer support with the trace output.

NZE-28857: Unknown SSL error

NZE-28857: Unknown SSL error

Cause: An unknown SSL error occurred.

Action: This error is not normally visible to the user. Enable Oracle Net tracing and attempt the connection again. Then contact Oracle customer support with the trace output.

NZE-28856: Buffer overflow error

NZE-28856: Buffer overflow error

Cause: A buffer overflowed during the SSL handshake.

Action: This error is not normally visible to the user. Enable Oracle Net tracing and attempt the connection again. Then contact Oracle customer support with the trace output.

NZE-28855: Unsupported SSL operation

NZE-28855: Unsupported SSL operation

Cause: An unsupported operation was attempted, for example, an attempt was made to select a mode of operation that is not allowed.

Action: Refer to the SSL chapter in the product s documentation.

NZE-28854: Memory allocation failure

NZE-28854: Memory allocation failure

Cause: The allocation of memory failed due to exhaustion of system memory.

Action: Terminate other processes to free up memory or add memory to the system.

NZE-28853: Initialization failure

NZE-28853: Initialization failure

Cause: Either initialization or module loading has failed.

Action: Enable Oracle Net tracing to determine the exact cause of this error.

NZE-28852: Bad password

NZE-28852: Bad password

Cause: The password created for obfuscated wallet exceeds the maximum password length limit.

Action: none

NZE-28846: No private key

NZE-28846: No private key

Cause: Either there is no private key or the system cannot find it.

Action: Check to ensure that the private key is in the specified wallet.

NZE-28845: No certificate

NZE-28845: No certificate

Cause: Either there is no certificate or the system cannot find it.

Action: Check to ensure that the certificate is in the specified wallet.

NZE-28844: No wallet present

NZE-28844: No wallet present

Cause: There was no wallet in the location specified.

Action: Check to ensure that the wallet is in the correct directory location.

NZE-28843: Operating system error while creating or opening file

NZE-28843: Operating system error while creating or opening file

Cause: An operating system dependent error occurred while trying to create or open the file or while trying to set the appropriate permissions on the file.

Action: Enable Oracle Net tracing and attempt the connection again. Contact Oracle customer support with the trace output.

NZE-28842: Incorrect file permissions

NZE-28842: Incorrect file permissions

Cause: The subject file did not have the correct permissions for the operation.

Action: Check the file permissions to ensure that they are adequate for the current operation.

NNF-00004: Operation not supported in string

NNF-00004: Operation not supported in string

Cause: The operation requested is not supported under this adapter.

Action: Verify that the operation being performed is not under restriction, such as writing to read-only name service. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNF-00003: Naming adapter string does not exist

NNF-00003: Naming adapter string does not exist

Cause: The requested name service adapter was not found in the current adapter table.

Action: Check the spelling of the adapter reqested. Verify that the adapter runs on this platform, and the adapter is compiled into the adapter table linked into the executable.

NNF-00002: Invalid value passed to function call

NNF-00002: Invalid value passed to function call

Cause: An invalid value was passed to an interface function.

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

NNF-00001: Not a TNS address

NNF-00001: Not a TNS address

Cause: While asking to read an address the name service returned a record which was not an address.

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

NPL-00420: received ASN.1 object identifier with more than 256 sub-identifiers

NPL-00420: received ASN.1 object identifier with more than 256 sub-identifiers

Cause: The ASN.1 protocol engine received an ASN.1 encoding which it could not process because its implementation does not support it.

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

NPL-00419: received ASN.1 object identifier with sub-identifier that is too large

NPL-00419: received ASN.1 object identifier with sub-identifier that is too large

Cause: The ASN.1 protocol engine received an ASN.1 encoding which it could not process because its implementation does not support it.

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

NPL-00418: received malformed ASN.1 object identifier

NPL-00418: received malformed ASN.1 object identifier

Cause: The ASN.1 protocol engine received a corrupted ASN.1 construct.

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

NPL-00417: received ASN.1 length octet count greater than maximum of string

NPL-00417: received ASN.1 length octet count greater than maximum of string

Cause: The ASN.1 protocol engine received an ASN.1 encoding which it could not process because its implementation does not support it..

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

NPL-00416: received illegal ASN.1 encoding length of string

NPL-00416: received illegal ASN.1 encoding length of string

Cause: The ASN.1 protocol engine received a corrupted ASN.1 construct.

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

NPL-00415: received unsupported ASN.1 INDEFINITE-LENGTH encoding

NPL-00415: received unsupported ASN.1 INDEFINITE-LENGTH encoding

Cause: The ASN.1 protocol engine received an ASN.1 encoding which it could not process because its implementation does not support it.

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

NPL-00414: incoming ASN.1 type tag is greater than maximum of 16383

NPL-00414: incoming ASN.1 type tag is greater than maximum of 16383

Cause: The ASN.1 protocol engine received an illegal ASN.1 construct.

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

NPL-00413: incoming ASN.1 encoding has length string, maximum allowed is string

NPL-00413: incoming ASN.1 encoding has length string, maximum allowed is string

Cause: The ASN.1 protocol engine received an ASN.1 construct too large for it to process.

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

NPL-00412: incoming ASN.1 BOOLEAN encoding has incorrect length of string

NPL-00412: incoming ASN.1 BOOLEAN encoding has incorrect length of string

Cause: The ASN.1 protocol engine received a corrupted ASN.1 construct.

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

NPL-00411: incoming ASN.1 NULL encoding has nonzero length of string

NPL-00411: incoming ASN.1 NULL encoding has nonzero length of string

Cause: The ASN.1 protocol engine received a corrupted ASN.1 construct.

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

NPL-00410: incoming ASN.1 value too large (string octets) to store locally

NPL-00410: incoming ASN.1 value too large (string octets) to store locally

Cause: The ASN.1 protocol engine was unable to translate an ASN.1 construct to its host representation because the construct was too big.

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

NPL-00313: requested form string does not match actual form string

NPL-00313: requested form string does not match actual form string

Cause: An internal function received an ASN.1 construct different from that expected.

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

NPL-00312: attempt to put ASN.1 UNIV type with illegal tag string

NPL-00312: attempt to put ASN.1 UNIV type with illegal tag string

Cause: An internal function attempted to create an illegal ASN.1 construct.

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

NPL-00311: cannot end constructed ASN.1 encoding, string encoding octets unread

NPL-00311: cannot end constructed ASN.1 encoding, string encoding octets unread

Cause: An internal function attempted to finish reading an ASN.1 construct prematurely.

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

NPL-00310: ASN.1 sequence has already been ended on read

NPL-00310: ASN.1 sequence has already been ended on read

Cause: An internal function attempted to finish reading an ASN.1 construct which has already been completely read.

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

NPL-00309: requested ASN.1 type tag string does not match received type tag string

NPL-00309: requested ASN.1 type tag string does not match received type tag string

Cause: An internal function requested an ASN.1 construct different from that received by the ASN.1 protocol engine.

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

PLS-00374: illegal EXIT statement; it must appear inside the loop labeled string

PLS-00374: illegal EXIT statement; it must appear inside the loop labeled string

Cause: An EXIT statement need not specify a label. However, if a label is specified (as in EXIT my_label), the EXIT statement must be inside the loop designated by that label.

Action: Make sure the label name is spelled correctly; if necessary, move the EXIT statement inside the loop to which the label refers.

PLS-00373: EXIT label string must label a LOOP statement

PLS-00373: EXIT label string must label a LOOP statement

Cause: The label in an EXIT statement does not refer to a loop. An EXIT statement need not specify a label. However, if a label is specified (as in EXIT my_label), it must refer to a loop statement.

Action: Make sure the label name is spelled correctly and that it refers to a loop statement.