Oracle Error Messages: 11/09/11

NNL-00503: repeat lamp;lt;lamp;nbsp;numberlamp;gt; lamp;lt;lamp;nbsp;commandlamp;gt; (lamp;lt;lamp;nbsp;argslamp;gt;( : repeat a command lamp;lt;lamp;nbsp;numberlamp;gt; times

NNL-00503: repeat lamp;lt;lamp;nbsp;numberlamp;gt; lamp;lt;lamp;nbsp;commandlamp;gt; (lamp;lt;lamp;nbsp;argslamp;gt;( : repeat a command lamp;lt;lamp;nbsp;numberlamp;gt; times

Cause: Control program help text.

Action: None.

NNL-00502: Shows, sets, or cancels when the server next dumps its statistic counters

NNL-00502: Shows, sets, or cancels when the server next dumps its statistic counters

Cause: Control program help text.

Action: None.

NNL-00501: set|show log_stats_interval (lamp;lt;lamp;nbsp;secondslamp;gt;( (lamp;lt;lamp;nbsp;server_listlamp;gt;( : set|show the server s statistic counter logging interval

NNL-00501: set|show log_stats_interval (lamp;lt;lamp;nbsp;secondslamp;gt;( (lamp;lt;lamp;nbsp;server_listlamp;gt;( : set|show the server s statistic counter logging interval

Cause: Control program help text.

Action: None.

NNL-00500: Shows information on domains served by this server

NNL-00500: Shows information on domains served by this server

Cause: Control program help text.

Action: None.

NNL-00418: Attributes Mapped: number

NNL-00418: Attributes Mapped: number

Cause: Control program general message.

Action: None.

NNL-00417: Distinguished Name: string

NNL-00417: Distinguished Name: string

Cause: Control program general message.

Action: None.

NNL-00416: Last timestamp: number

NNL-00416: Last timestamp: number

Cause: Control program general message.

Action: None.

NNL-00415: Name: string

NNL-00415: Name: string

Cause: Control program general message.

Action: None.

NNL-00414: Maximum response time: string

NNL-00414: Maximum response time: string

Cause: Control program general message.

Action: None.

NNL-00413: Total response time: string

NNL-00413: Total response time: string

Cause: Control program general message.

Action: None.

NNL-00412: Number of requests: number

NNL-00412: Number of requests: number

Cause: Control program general message.

Action: None.

NNL-00411: Minimum response time: string

NNL-00411: Minimum response time: string

Cause: Control program general message.

Action: None.

NNL-00410: Average response time: string

NNL-00410: Average response time: string

Cause: Control program general message.

Action: None.

NNL-00409: data type is string

NNL-00409: data type is string

Cause: Control program general message.

Action: None.

NNL-00408: Answers:

NNL-00408: Answers:

Cause: Control program general message.

Action: None.

NNL-00407: Alias translations:

NNL-00407: Alias translations:

Cause: Control program general message.

Action: None.

NNL-00406: Canonical name: string

NNL-00406: Canonical name: string

Cause: Control program general message.

Action: None.

PCB-00109: Unable to open generated source file string

PCB-00109: Unable to open generated source file string

Cause: The precompiler was unable to open the output file specified by the ONAME precompiler option. Some possible causes follow: o The filename is misspelled. o The file does not exist. o The search path to the file is incorrect. o File acces privileges are insufficient. o Another user has locked the file. o There is not enough disk space. o There are too many open files.

Action: Check that the file exists, that the search path to the file is correct, that sufficient privileges have been granted to access the file, and that it is not locked by another user. Also check that there is enough disk space and that the limit for open files is set high enough (check with the system manager).

PCB-00108: Unable to open list file string

PCB-00108: Unable to open list file string

Cause: The precompiler was unable to open the list file specified by the LNAME precompiler option. Some possible causes follow: o The filename is misspelled. o The file does not exist. o The search path to the file is incorrect. o File acces privileges are insufficient. o Another user has locked the file. o There is not enough disk space. o There are too many open files.

Action: Check that the file exists, that the search path to the file is correct, that sufficient privileges have been granted to access the file, and that it is not locked by another user. Also check that there is enough disk space and that the limit for open files is set high enough (check with the system manager). If a listing file is not needed, specify LTYPE=NONE on the command line.

PCB-00106: Unable to open INCLUDE file string

PCB-00106: Unable to open INCLUDE file string

Cause: The precompiler was unable to open the input file specified in the INCLUDE statement. Some possible causes follow: o The filename is misspelled. o The file does not exist. o The search path to the file is incorrect. o File access privileges are insufficient. o There is not enough disk space. o There are too many open files.

Action: Check that the file exists, that the search path to the file is correct, that sufficient privileges to access the file have been granted, and that it is not locked by another user. Also, check that there is enough disk space and that the limit for open files is set high enough (check with the system manager).

PCB-00105: Included file name string exceeds name limit of number characters

PCB-00105: Included file name string exceeds name limit of number characters

Cause: The file name length specified exceeded the maximum length. Some operating systems have a maximum file name length.

Action: Use a file name of length less than or equal to the maximum platform specific file name length.

PCB-00104: Unable to open input file string

PCB-00104: Unable to open input file string

Cause: The precompiler was unable to open the input file specified by the INAME precompiler option. Some possible causes follow: o The filename is misspelled. o The file does not exist. o The search path to the file is incorrect. o File access privileges are insufficient. o Another user has locked the file. o There is not enough disk space. o There are too many open files.

Action: Check that the file exists, that the search path to the file is correct, that sufficient privileges have been granted to access the file, and that it is not locked by another user. Also check that there is enough disk space and that the limit for open files is set high enough (check with the system manager).

PCB-00102: Input file name length exceeds the maximum length

PCB-00102: Input file name length exceeds the maximum length

Cause: The file name length specified exceeded the maximum length. Some operating systems have a maximum file name length.

Action: Use a file name of length less than or equal to the maximum platform specific file name length.

PCB-00101: Could not find or open system configuration file

PCB-00101: Could not find or open system configuration file

Cause: The precompiler was unable to open the system configuration file. The system configuration file does not exist or is not in the proper directory.

Action: Check that the system configuration file is in the proper directory. See Oracle installation documentation for where this should be. Put a new copy of pcccob.cfg with desired default options in the proper directory.

PCB-00100: Unable to reopen temporary file string

PCB-00100: Unable to reopen temporary file string

Cause: The precompiler was unable to reopen a temporary file. Some possible causes follow: o File access privileges are insufficient. o Another user has locked the file. o There is not enough disk space. o There are too many open files.

Action: Check that sufficient privileges have been granted to access the file, and that it is not locked by another user. Also check that there is enough disk space and that the limit for open files is set high enough (check with the system manager).

PCB-00012: Command line option DYNAMIC=ANSI required with option TYPE_ CODE=ANSI

PCB-00012: Command line option DYNAMIC=ANSI required with option TYPE_ CODE=ANSI

Cause: The precompiler option TYPE_CODE=ANSI was used without also specifying DYNAMIC=ANSI. The precompiler option DYNAMIC=ANSI must be specifiied if TYPE_CODE=ANSI.

Action: Set the precompiler option DYNAMIC=ANSI in addition to TYPE_ CODE=ANSI or do not set TYPE_CODE=ANSI.

PCB-00011: DBMS=V6 no longer supported; using DBMS=NATIVE

PCB-00011: DBMS=V6 no longer supported; using DBMS=NATIVE

Cause: V6 compatibility is no longer supported. The precompiler will precompile as though DBMS=NATIVE was specified.

Action: Revise the specified DBMS option value from v6 to another value as desired.

PCB-00010: SQLCHECK value in EXEC ORACLE statement exceeds command line value

PCB-00010: SQLCHECK value in EXEC ORACLE statement exceeds command line value

Cause: The SQLCHECK option was entered inline and specified a level of checking higher than the level specified (or accepted by default) on the command line. This is not allowed. For example, if SQLCHECK={SYNTAX | LIMITED} is specified on the command line, SQLCHECK={SEMANTICS | FULL} cannot be specified inline. This informational message is; the precompiler ignores the inline value and continues processing.

Action: Revise the EXEC ORACLE statement or specify a lower level of checking on the command line.

PCB-00009: Cannot change MAXLITERAL after an EXEC SQL statement

PCB-00009: Cannot change MAXLITERAL after an EXEC SQL statement

Cause: The MAXLITERAL option has been used in an inline EXEC ORACLE OPTION statement after and EXEC SQL, EXEC TOOLS, or EXEC IAF statement. This is not allowed.

Action: Use the MAXLITERAL option only on the command line or in an EXEC ORACLE OPTION statement placed at the beginning of the input source file.

PCB-00008: Must use option SQLCHECK=SEMANTICS(FULL) when there is embedded PL or SQL

PCB-00008: Must use option SQLCHECK=SEMANTICS(FULL) when there is embedded PL or SQL

Cause: The precompiler tried to parse an embedded PL or SQL block when SQLCHECK={SYNTAX | NONE}. PL or SQL blocks can be parsed only when SQLCHECK=SEMANTICS is specified.

Action: Remove the PL or SQL block or specify SQLCHECK=SEMANTICS.

PCB-00007: %s

PCB-00007: %s

Cause: This is a generic error message from the command-line processor.

Action: Correct the indicated error.

PCB-00006: Userid only used when SQLCHECK=FULL, userid ignored.

PCB-00006: Userid only used when SQLCHECK=FULL, userid ignored.

Cause: The USERID option was specified when SQLCHECK={SYNTAX | NONE}. This is unnecessary.

Action: Specify the USERID option only when SQLCHECK=SEMANTICS.

NZE-29042: Read buffer is not empty.

NZE-29042: Read buffer is not empty.

Cause: There is an attempt to free a read buffer that is not empty.

Action: none

NZE-29041: The callback is NULL.

NZE-29041: The callback is NULL.

Cause: A NULL callback was passed.

Action: none

NZE-29040: There are no supported cipher suites.

NZE-29040: There are no supported cipher suites.

Cause: This end of the handshake cannot support any cipher suites. This connection and the peer have some matching cipher suites, howvever, these cipher suites cannot be negotiated because they cannot be supported by the connection.

Action: Check to ensure that both sides of the handshake select cipher suites that are supported by the connection. Refer to Oracle documentation for supported cipher suites.

NZE-29039: There are no matching cipher suites.

NZE-29039: There are no matching cipher suites.

Cause: Neither end of the handshake can agree on a cipher suite.

Action: Check to ensure that both sides of the handshake select cipher suites that are supported.

NZE-29038: There are no matching certificates.

NZE-29038: There are no matching certificates.

Cause: The other client or server sent a certificate message that contained a certificate which was not signed by a trusted certificate authority (CA).

Action: Check to ensure that the other client or server sends a certificate which is signed by a CA that is in your trusted list. Or you can include the CA certificate for the other client or server s certificate as a trustpoint in your wallet.

NZE-29037: No certificate is present

NZE-29037: No certificate is present

Cause: The other client or server sent a certificate message that contained no certificates.

Action: No action recommended other than checking the other client or server to ensure they have appropriate credentials.

NZE-29036: This feature is not supported

NZE-29036: This feature is not supported

Cause: Operation is not supported by the current connection parameters.

Action: Check the Oracle documentation to determine the appropriate connection parameters required for this operation.

NZE-29035: Pseudo Random Number Generator is needed

NZE-29035: Pseudo Random Number Generator is needed

Cause: PRNG not set yet. A PRNG must be installed first.

Action: none

NZE-29034: Correct cipher suite or client authentication is needed.

NZE-29034: Correct cipher suite or client authentication is needed.

Cause: Before installing a private key, a cipher suite or client authentication suite using the same key exchange algorithm must be installed first. This has not been done.

Action: Install a cipher suite or client authentication suite that uses the same key exchange algorithm as the private key before re-installing the private key.

NZE-29033: Invalid PFX

NZE-29033: Invalid PFX

Cause: The PFX is invalid for this operation containing either no certificates and private key or multiple private keys. However, the API which returns this error is not used in our code.

Action: none

NZE-29032: The given identity is not complete.

NZE-29032: The given identity is not complete.

Cause: The certificate list does not contain both private key and certificate.

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

NZE-29031: SSL handshake is required.

NZE-29031: SSL handshake is required.

Cause: Renegotiation cannot proceed before the SSL handshake is completed.

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

NZE-29030: SSL handshake is requested.

NZE-29030: SSL handshake is requested.

Cause: The peer sends this message if it wishes to renegotiate. The application can either proceed with the rengotiation or reject the request.

Action: This is not an error. To find out more details enable Oracle Net tracing and attempt the connection again. Contact Oracle customer support with the trace output.

NZE-29029: SSL handshake already completed

NZE-29029: SSL handshake already completed

Cause: The system is trying to initiate a handshake when it has already been completed.

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

NZE-29028: Server verification failure when using SSL 2.0

NZE-29028: Server verification failure when using SSL 2.0

Cause: Processing of an SSL 2.0 SERVER-VERIFY message failed.

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

NZE-29027: Error in entropy collection

NZE-29027: Error in entropy collection

Cause: The internal entropy collection failed to generate enough seed data.

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

NZE-29026: Decryption failure

NZE-29026: Decryption failure

Cause: SSL record decryption failed.

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

NZE-29025: Error found in certificate check callback.

NZE-29025: Error found in certificate check callback.

Cause: The application callback failed while trying to do additional certificate validation. Additional checks include CRL validation, extension checking.

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

NZE-29024: Certificate validation failure

NZE-29024: Certificate validation failure

Cause: The certificate sent by the other side could not be validated. This may occur if the certificate has expired, has been revoked, or is invalid for another reason.

Action: Check the certificate to determine whether it is valid. Obtain a new certificate, alert the sender that there certificate has failed, or resend.

NZE-29023: The buffers are not empty.

NZE-29023: The buffers are not empty.

Cause: Trying to free buffers that are not empty.

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

NZE-29022: Operation is being attempted on the wrong side of the client or server connection.

NZE-29022: Operation is being attempted on the wrong side of the client or server connection.

Cause: The SSL network layer has detected that the operation has been attempted on the wrong side of the client or server connection.

Action: Select the protocol side (of this protocol) to be the same as the one selected with a previous protocol.

NZE-29021: Secret key length is incorrect when using SSL 2.0.

NZE-29021: Secret key length is incorrect when using SSL 2.0.

Cause: The length of the decrypted ENCRYPTED-KEY is incorrect.

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

NZE-29020: The handshake record length is too long.

NZE-29020: The handshake record length is too long.

Cause: The handshake record length exceeds the maximum that is specified by the SSL specification.

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

NZE-29019: The protocol version is incorrect.

NZE-29019: The protocol version is incorrect.

Cause: There is a protocol version mismatch between the two peers.

Action: Specify the correct protocol version in the product s configuration file.

NZE-29018: The premaster secret contains an incorrect version number.

NZE-29018: The premaster secret contains an incorrect version number.

Cause: The premaster secret must contain the same version number as the ClientHello. The version sent by the client was incorrect.

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