51 NZE-28750 to NZE-29249

NZE-28750: unknown error

Cause: An Oracle Security Server error of an unspecified type occurred.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28751: memory allocation failure

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

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

NZE-28752: data source initialization failure

Cause: A data source failed to initialize. Frequently, this error is caused by insufficient system resources.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28753: failure to terminate use of data source

Cause: The system failed to terminate its use of a data source. This error may have been caused by memory or disk corruption, among other things.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28755: object retrieval failure

Cause: The system failed to retrieve information from a file or a database.

Action: Check if the data source exists, or check to ensure that the correct information exists.

NZE-28756: callback failure to allocate memory

Cause: A function supplied by the caller failed to allocate memory. This error could have been caused by system memory exhaustion.

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

NZE-28757: system attempt to allocate 0 bytes of memory

Cause: The system attempted to allocate 0 bytes of memory because there was no available memory left to allocate. This error could have been caused by insufficient system memory.

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

NZE-28758: memory release failure

Cause: The release of a memory fragment failed. This may be due to memory corruption either within the application or in the Oracle Security Server library.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28759: failure to open file

Cause: The system could not open the specified file.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28763: Invalid parameter type found in configuration file.

Cause: A parameter in the sqlnet.ora file may have been specified incorrectly.

Action: Check the sqlnet.ora file for this parameter value.

NZE-28764: failure to retrieve a configuration parameter

Cause: The system failed to retrieve a configuration parameter from the sqlnet.ora file. This error may have occurred because a necessary configuration parameter was not specified in the sqlnet.ora file.

Action: Supply the needed configuration parameter in the sqlnet.ora file.

NZE-28766: failure to terminate use of data source

Cause: The system failed to terminate its use of a data source. This error may have been caused by memory or disk corruption, or a system error.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28767: invalid version number

Cause: Version number of the wallet was incorrect. A corrupt wallet or an incompatible wallet was provided.

Action: Ensure that proper wallet is being used.

NZE-28768: bad magic number

Cause: An invalid magic number was specified in a data file. This could have been caused by a corrupted disk or by some other process overwriting the file.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28769: Specified method does not exist.

Cause: The data access method that was specified in the configuration file is not supported.

Action: Specify a supported method. Consult the Oracle Security Server documentation to determine the supported types.

NZE-28770: Data source is already initialized.

Cause: The caller attempted to initialize a data source which was already initialized.

Action: This is a programming error. An application should not attempt to initialize a data source more than once.

NZE-28771: Data source is not yet initialized.

Cause: The caller attempted to use a data source which had not yet been initialized.

Action: This is a programming error. The application must always initialize the data source before it can be used.

NZE-28773: failure to write magic and version numbers

Cause: Both the magic and version numbers failed to write. This usually occurs because of insufficient disk space.

Action: Delete unnecessary files to free up disk space or add disk space to the system.

NZE-28774: file cannot write to disk

Cause: The output of a file failed. This error usually occurs because of insufficient disk space.

Action: Delete unnecessary files to free up disk space or add disk space to the system.

NZE-28775: file cannot close

Cause: Failed to close a file which is used by a data access method. This error usually indicates memory corruption or a system error.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28776: Output buffer supplied is too small.

Cause: The data returned by a function was too large for the supplied buffer.

Action: Call the routine again with a larger buffer.

NZE-28777: binding creation failure

Cause: Failed to create a binding for use in the parsing of a parameter value. This error can be caused by the parameter value being in an incorrect format, such as a right parenthesis was not supplied where expected, or due to insufficient system memory.

Action: Make sure that the parameter is specified in the correct format. If the format is correct, free up system memory by terminating processes or adding more memory.

NZE-28778: Configuration parameter is not specified in the proper format.

Cause: The configuration parameter was not specified in the proper format.

Action: Consult the Oracle Security Server documentation for a description of the proper format for this parameter.

NZE-28779: no data access method specified in parameter

Cause: No method for data access was specified in the parameter value.

Action: Specify a method for data access in the parameter. Consult the Oracle Security Server documentation for the supported data access methods for this data type.

NZE-28780: invalid data access method specified by the parameter

Cause: The data access method specified by the parameter value is not supported.

Action: Specify a supported data access method. Consult the Oracle Security Server documentation for the supported data access methods for this data data type.

NZE-28781: No data for the access method is specified in the parameter.

Cause: No data was specified in the parameter for use with the specified access method.

Action: Consult the Oracle Security Server documentation for the data that must be specified for the access method.

NZE-28782: data source is not allocated

Cause: No memory was allocated for a data source.

Action: Ensure that the application calls in the data source initialization function.

NZE-28783: invalid parameter

Cause: There was no match for the parameter name that was used in the configuration file.

Action: Check your sqlnet.ora file for the correct parameter name.

NZE-28784: file name translation failure

Cause: The translation of a file name from Oracle format to native format has failed.

Action: Specify a correct file name. Consult your Oracle documentation for the correct file name format.

NZE-28785: parameter does not exist

Cause: A necessary configuration parameter was not found in the parameter file.

Action: Supply the required parameter.

NZE-28786: decryption of encrypted private key failure

Cause: An incorrect password was used to decrypt an encrypted private key.

Action: Enter the correct password.

NZE-28787: private key encryption failure

Cause: This may have been caused by an error in the mkwallet parameter of the sqlnet.ora file.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28788: user provided invalid information, or an unknown error

Cause: User may have responded to a prompt with unexpected input, or an unknown error occurred.

Action: Enter correct input, or enable tracing to check the trace file for errors.

NZE-28790: NLS string open failure

Cause: The opening of a string for use by the NLS subsystem failed.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28791: certificate verification failure

Cause: Verification of the certificate, which the user supplied, failed.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28794: data type attribute did not initialize

Cause: The initialization of the attribute data type failed. This error may be due to insufficient system resources.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28795: data type attribute did not terminate

Cause: The termination of the use of the attribute data type subsystem failed.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28796: access method is not supported

Cause: The method specified to access data is not supported.

Action: Use a supported access method. Consult your Oracle documentation to determine which access methods are supported.

NZE-28797: invalid key data type

Cause: The type specified for a key is not supported.

Action: Correct the key type. Consult your Oracle documentation to determine which key types are supported.

NZE-28800: data source failed to open

Cause: A data source (a file or a database) failed to open.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28802: invalid mode or data source in configuration file

Cause: An invalid mode or data source has been specified in the configuration file (sqlnet.ora).

Action: Check the method parameter in the sqlnet.ora file. If the parameter value is correct, then enable tracing to determine the exact error.

NZE-28803: I/O operation failure

Cause: The system or application failed to access a data source (file or database).

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28804: Data source cannot close.

Cause: The data source, which could be either a file or a database), failed to close.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28805: Cannot retrieve information from the data source.

Cause: The system or application failed to retrieve information from the data source (file or database).

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28806: Cannot write to the data source.

Cause: The system or application failed to write to the data source (file or database).

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28807: Cannot update the data source.

Cause: The system or application failed to update the data source (file or database).

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28808: Cannot retrieve method information from the configuration file.

Cause: The system or application failed to retrieve method information from the sqlnet.ora configuration file.

Action: Check the method configuration parameters in the sqlnet.ora file. If the method configuration parameters are correct, then enable tracing to determine the exact error.

NZE-28809: Cannot delete information from the data source.

Cause: The system or application failed to delete information from the data source (file or database).

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28810: Cannot create key descriptor.

Cause: The system failed to create a key descriptor.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28814: Cannot convert a number in Oracle format to native format.

Cause: Failed to convert a number from Oracle format to native format.

Action: This is an internal programming exception. Enable tracing to try and reproduce the problem. Contact Oracle customer support and supply the trace file.

NZE-28815: Cannot convert a number in native format to Oracle format.

Cause: Failed to convert a number from native format to Oracle portable format failed.

Action: This is an internal programming exception. Enable tracing to try and reproduce the problem. Contact Oracle customer support and supply the trace file.

NZE-28818: No package context provided.

Cause: The context that holds the state of the security package was not passed to a function or procedure that was expecting it.

Action: This is an internal error. Enable tracing to find more information. Contact Oracle customer support if needed.

NZE-28836: Wallet is not open.

Cause: The wallet to be used has not yet been opened.

Action: Call the function that opens the wallet.

NZE-28840: Wallet is already open.

Cause: An attempt was made to open a wallet that was already open.

Action: This is a programming error. A wallet should only be opened once.

NZE-28841: Operation is not supported.

Cause: An attempt was made to perform an operation that is not supported.

Action: This is a programming error. Please refer to Oracle documentation to determine which operations are supported.

NZE-28842: Incorrect file permissions

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

Action: Ensure that the file permissions allow the current operation.

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

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

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

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-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-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-28847: No clear private key file

Cause: Failed to retrieve private key from SSO wallet

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28848: No encrypted private key file

Cause: Failed to retrieve private key from the wallet

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28849: No Trustpoints

Cause: The wallet does not have any trusted certificates

Action: Ensure that the wallet/keystore has trusted certificates.

NZE-28853: Initialization failure

Cause: Either initialization or module loading has failed.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28854: Memory allocation failure

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

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

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-28857: Unknown SSL error

Cause: An unknown SSL error occurred.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28858: SSL protocol error

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

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28859: SSL negotiation failure

Cause: An error occurred during 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 tracing and retry the connection. Then contact Oracle customer support with the trace output.

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 tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-28861: SSL connection would block

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

Action: Enable tracing and retry the connection to determine the exact cause of the error. Contact Oracle customer support if needed.

NZE-28862: SSL connection failed

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

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

NZE-28863: SSL session not found

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

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

NZE-28864: SSL connection closed gracefully

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

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

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 tracing and retry the connection. The trace output should indicate how the failure occurred.

NZE-28866: Invalid peer certificate encoding

Cause: A field from a certificate in the peer's certificate chain 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-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-28868: Peer certificate chain check failed.

Cause: The check of the certificate list presented by the peer failed. Possible causes include: 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-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 is unexpired, and attempt the connection again.

NZE-28870: Name comparison failure

Cause: A comparison of the names contained in two certificates failed.

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

NZE-28871: Peer certificate chain is incomplete.

Cause: The peer certificate chain presented was incomplete 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 root certificate 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-28872: Invalid peer certificate format

Cause: The peer certificate does not conform to the X.509v3 standard.

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

NZE-28874: SSL: I/O closed - override goodbye kiss

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

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

NZE-28875: SSL: use server-gated cryptographic suites

Cause: This is used as a internal status indicator and not really an error.

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

NZE-28884: invalid cipher suite

Cause: An invalid cipher suite string has been specified in the product's configuration file.

Action: Refer to the product documentation for information about supported cipher suites.

NZE-28885: No certificate with the required key usage found.

Cause: Certificate not created with the appropriate X509v3 key usage extension.

Action: Refer to Oracle Wallet Manager documentation to find out the supported key usages.

NZE-28890: Entrust Login Failed

Cause: An application failed to log in to an Entrust Profile. Possible causes include: 1. Entrust Admin/Authority was not online. 2. Invalid password for Entrust profile was specified. 3. Invalid path to Entrust profile was specified 4. Invalid Entrust initialization file was specified. 5. Entrust Server Login program was not executed (server-side only).

Action: Make sure that: 1. Entrust Authority is online; 2. Password for Entrust profile is specified correctly; 3. Path to Entrust profile is specified correctly; 4. A valid Entrust initialization file is provided; 5. Entrust Server Login program is run before the database startup. For more information, enable tracing and examine the trace output to get exact the Entrust failure codes.

NZE-29000: Certificate not installed

Cause: Trying to delete a certificate which has not been installed.

Action: Refer to the Oracle Wallet Manager documentation for information about delete option.

NZE-29002: SSL transport detected invalid or obsolete server certificate.

Cause: The client detected a mismatch between the server's distinguished name specified on the server's certificate and the server's SID or service name.

Action: Refer to the SSL chapter in Oracle Advanced Security Administrator's Guide for information about enabling server distinguished name matching. Contact your administrator to perform the appropriate action.

NZE-29003: SSL transport detected mismatched server certificate.

Cause: The client detected a mismatch between the server's distinguished name specified on the server's certificate and the server's SID or service name.

Action: Refer to the SSL chapter in Oracle Advanced Security Administrator's Guide for information about enabling server distinguished name matching. Contact your administrator to perform the appropriate action.

NZE-29005: The certificate is invalid.

Cause: The peer certificate encoding is invalid when using SSL 2.0.

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-29006: The certificate request message is invalid when using SSL 2.0.

Cause: There is an error processing the SSL 2.0 REQUEST-CERTIFICATE message.

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

NZE-29007: Bad Clear Key Length when using SSL 2.0

Cause: The clear key length of an SSL 2.0 Client Master key handshake message is invalid.

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

NZE-29008: Bad DH Param key length

Cause: The length of the Diffie-Hellman params exceeds export restrictions.

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

NZE-29009: Bad encrypted key length when using SSL 2.0

Cause: The encrypted key length of an SSL 2.0 Client Master key handshake message is invalid.

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

NZE-29010: Export key length does not meet export restrictions.

Cause: The server sent a ServerKeyExchange message with an export key which does not meet export restrictions. For RSA, the export key must be exactly 512 bits.

Action: Obtain a certificate with the appropriate key length.

NZE-29011: Finished message is incorrect.

Cause: The FINISHED message data verification failed.

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

NZE-29012: Bad key argument length when using SSL 2.0

Cause: The key argument length of an SSL 2.0 Client Master Key handshake message is invalid.

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

NZE-29013: SSL MAC verification failure

Cause: Verification of SSL Record MAC failed.

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

NZE-29014: Maximum fragment length extension is incorrect.

Cause: The maximum fragment length extension specified is incorrect.

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

NZE-29015: incorrect message length

Cause: The message length is not correct.

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

NZE-29016: inadequate PKCS1 message padding

Cause: The message was not properly padded before encryption.

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

NZE-29017: The premaster secret length is incorrect.

Cause: The premaster secret sent by the peer has an incorrect length.

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

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 tracing and attempt the connection again. Contact Oracle customer support with the trace output.

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-29020: The handshake record length is too long.

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

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

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

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

Action: Enable 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/server connection.

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

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

NZE-29023: The buffers are not empty.

Cause: Trying to free buffers that are not empty.

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

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 the certificate has failed, or resend.

NZE-29025: Error found in certificate check callback.

Cause: The application callback failed during additional certificate validation. Additional checks include CRL validation and extension checking.

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

NZE-29026: Decryption failure

Cause: SSL record decryption failed.

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

NZE-29027: Error in entropy collection

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

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

NZE-29028: Server verification failure when using SSL 2.0

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

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

NZE-29029: SSL handshake already completed

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

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

NZE-29030: SSL handshake is requested.

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

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

NZE-29031: SSL handshake is required.

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

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

NZE-29032: The given identity is not complete.

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

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

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-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-29037: No certificate is present

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

Action: Check the other side (client or server) to ensure they have appropriate credentials.

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, include the CA certificate for the other client or server's certificate as a trustpoint in your wallet.

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-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, however, 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-29043: Read is required.

Cause: Renegotiation with the peer has not yet started. There is application data which must be processed before the handshake can proceed.

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

NZE-29044: Renegotiation has already been requested.

Cause: Renegotiation has already been requested.

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

NZE-29045: Renegotiation request has been refused.

Cause: A renegotiated handshake has been refused by the peer.

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

NZE-29046: Session is resumable.

Cause: Server is trying to resume a session with different session parameters.

Action: Server should resume the session with the correct session parameters.

NZE-29047: Mismatch in Transport Layer Security extension

Cause: Neither side can agree on a TLS extension.

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

NZE-29048: Unexpected message received.

Cause: An unexpected message has been received.

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

NZE-29049: Unknown record

Cause: The record type is unknown.

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

NZE-29050: Installed client authentication mode is not supported.

Cause: The enabled client authentication mode(s) cannot be used within the selected cipher suite.

Action: Enable a client authentication mode that can be used within the selected cipher suite.

NZE-29051: The given public key type is not supported.

Cause: The public key in the first certificate is not supported.

Action: Check to ensure that the certificate complies with the X.509v3 standard.

NZE-29052: Write buffer is not empty.

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

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

NZE-29084: The parameter specified is illegal.

Cause: The parameter is not correct. For example, it could be bad input, or an invalid message.

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

NZE-29095: Index is not correct.

Cause: The instance identified by the index parameter doesn't exist.

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

NZE-29096: The given length is incorrect.

Cause: The specified length is too small or is invalid.

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

NZE-29100: Cannot create local key ID.

Cause: Creation of local key identifier for the certificate or the private key failed.

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

NZE-29101: Cannot add private key bag.

Cause: The private key could not be added to the PKCS#12 object. Possible reasons are: (i) A required parameter is NULL (ii) The PKCS#12 construct is not supported (iii) An ASN.1 encoding error occurred in the certificate.

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

NZE-29102: Cannot add certificate bag.

Cause: Creation of certificate bag failed. The application could have run out of memory.

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

NZE-29103: Cannot create PKCS #12 wallet.

Cause: Creation of PKCS#12 wallet failed possibly due to memory allocation failure.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-29104: Cannot add certificate request.

Cause: Adding certificate request to the PKCS#12 wallet failed.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-29105: Cannot export PKCS #12 wallet.

Cause: A required parameter is NULL or the PKCS#12 construct is not supported.

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

NZE-29106: Cannot import PKCS #12 wallet.

Cause: A required parameter is NULL or the BER-encoding is malformed.

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

NZE-29107: Cannot create PKCS #12 wallet.

Cause: PKCS#12 wallet creation failed. The application may have run out of memory.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-29108: Cannot initialize random object.

Cause: The random object could not be initialized or seeded. Either memory allocation has failed or the pseudo random number generator module has not been installed.

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

NZE-29109: Cannot create private key object.

Cause: The private key object could not be created. Memory allocation may have failed.

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

NZE-29110: Invalid PKCS #12 bag type

Cause: The PKCS #12 bag type is invalid. Either one of the required parameters is NULL or the requested OID is not in the list.

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

NZE-29111: Invalid index

Cause: The index passed for getting the bag type is less than 1.

Action: Check to ensure that the index is greater than 1.

NZE-29112: Cannot access attributes from a PKCS #12 certificate bag.

Cause: The certificate cannot be accessed. One of the required parameters is probably NULL, or the index specified by the application does not contain a certbag, or the certificate could be malformed.

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

NZE-29113: Cannot access attributes from a PKCS #12 key bag.

Cause: Retrieval of the private key failed. One of the required parameters is probably NULL or the index specified by the application does not contain a key bag.

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

NZE-29114: Cannot import private key.

Cause: The private key could not be imported. One of the required parameters could be NULL or the encoded private key could be malformed.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-29115: Cannot export private key.

Cause: The private key could not be exported. Either the application ran out of memory or the key type is not valid.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-29116: Cannot get PKCS #12 attributes.

Cause: Retrieval of an attribute failed. One of the required parameters could be NULL.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-29117: Cannot add PKCS #12 attributes.

Cause: Could not add an attribute. The attribute parameter could be NULL.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-29118: Cannot create PKCS #12 attributes.

Cause: Creation of the attributes failed, possibly due to a memory allocation error.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-29119: Cannot import certificate.

Cause: The certificate cannot be imported. One of the required parameters could be NULL or the certificate has an invalid X.509 BER or DER encoding.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-29120: Cannot export certificate.

Cause: The certificate cannot be exported. One of the required parameters could be NULL.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-29122: could not add pkcs11 info to the pkcs12 wallet

Cause: Failed while adding pkcs11 information into a pkcs12 wallet.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-29123: could not get pkcs11 info from the pkcs12 wallet

Cause: An error was encountered while retrieving pkcs11 information from the wallet.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.

NZE-29124: pkcs11 library name already set

Cause: pkcs11 library information was already set in the wallet.

Action: Use a different wallet that does not have this information. If issue persists, enable tracing to determine the exact cause of the error. Contact Oracle customer support if needed.

NZE-29125: pkcs11 token label already set

Cause: pkcs11 token label information was already set in the wallet.

Action: Use a different wallet that does not have this information. If issue persists, enable tracing to determine the exact cause of the error. Contact Oracle customer support if needed.

NZE-29126: pkcs11 token passphrase already set

Cause: The pkcs11 token passphrase can be set only once in the wallet.

Action: Use a different wallet that does not have this information. If issue persists, enable tracing to determine the exact cause of the error. Contact Oracle customer support if needed.

NZE-29127: unknown pkcs11 information

Cause: An unknown pkcs11 information type was encountered. The wallet may have been corrupted due to a system error or memory corruption.

Action: Enable tracing and retry the failed operation. Contact Oracle customer support with the trace output.

NZE-29128: pkcs11 library name not set

Cause: The wallet does not have pkcs11 library information.

Action: Ensure that the wallet was created with valid library location or update the wallet with this information.

NZE-29129: pkcs11 token label not set

Cause: The wallet does not have pkcs11 token label information.

Action: Ensure that the wallet was created with valid token label information or update the wallet with this information.

NZE-29130: pkcs11 token passphrase not set

Cause: The wallet does not have pkcs11 token passphrase.

Action: Ensure that the wallet was created with valid token passphrase information or update the wallet with this information.

NZE-29131: pkcs11 certificate label already set in wallet

Cause: The pkcs11 certificate label was already set in the wallet.

Action: Use an empty wallet (created with orapki).

NZE-29135: Seed generation for Random Number Generator failed.

Cause: Generation of seed for random number generator failed.

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

NZE-29136: The allocated buffer is too small.

Cause: The output buffer is too small.

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

NZE-29137: The global context is incorrect.

Cause: The global context is incorrectly configured or invalid.

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

NZE-29140: Cannot create certificate object.

Cause: Creation of the certificate object failed. The application could have run out of memory.

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

NZE-29141: Cannot import in the der format.

Cause: Cannot import the certificate into the certificate object. The reason could be a malformed certificate.

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

NZE-29150: DES self-test failure

Cause: DES power up self-test has failed.

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

NZE-29151: 3DES self-test failure

Cause: 3DES power up self-test has failed.

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

NZE-29152: SHA-1 self-test failure

Cause: The SHA-1 power up self-test has failed.

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

NZE-29153: RSA self-test failure

Cause: The RSA power up self-test has failed.

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

NZE-29154: deterministic RNG self-test failure

Cause: The deterministic Random Number Generator power up self-test has failed.

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

NZE-29155: continuous key pair consistency check self-test failure

Cause: The public-private key pair check test failed.

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

NZE-29156: conditional RNG self-test failure

Cause: Continuous Random Number Generator test, which is needed in FIPS mode, has failed.

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

NZE-29157: Unable to build an absolute path to the library.

Cause: Not able to construct an absolute path to the location of the library.

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

NZE-29158: Unable to open library.

Cause: Opening of the library failed.

Action: Check to ensure that the library is present in the location specified, and that it has the appropriate file permissions.

NZE-29159: Unable to read library.

Cause: Not able to read the library on which the DAC check has to be performed. Read call failed.

Action: Check if the library has the appropriate file permissions.

NZE-29160: NZ library being used is different.

Cause: The NZ library being used at runtime is not the same one on which the digest was computed for the software integrity check.

Action: Check to ensure that the library being used is the same as the one on which the digest was pre-computed.

NZE-29161: software integrity self-test failure

Cause: The software integrity check test on the NZ shared library has failed.

Action: Check to ensure that the library being used is the same as the one on which the digest was pre-computed.

NZE-29162: Non-FIPS cipher suites being used in FIPS mode.

Cause: The cipher suite being used does not contain FIPS-approved algorithms.

Action: Use cipher suites that contain FIPS-approved algorithms.

NZE-29163: Third party PKI vendor is not supported in FIPS mode.

Cause: Third party PKI vendors like Entrust and MCS are not supported in FIPS mode.

Action: Use only Oracle PKI when running in FIPS mode.

NZE-29164: External PKCS #12 wallet is not supported in FIPS mode.

Cause: PKCS #12 wallets created using third party software cannot be used in FIPS mode.

Action: Use only PKCS #12 wallets created by Oracle Wallet Manager when running in FIPS mode.

NZE-29166: Bad key size in FIPS mode.

Cause: User attempted to use a key size that is not allowed in FIPS mode

Action: Ensure that the key size meets FIPS usage requirement. For example, RSA key modulus cannot be less than 1024 bits in FIPS mode.

NZE-29176: CRL signature verification failed

Cause: A CRL is verified before being used. CRL signature cannot be verified.

Action: Get a new CRL from CA

NZE-29177: certificate serial number is not in CRL

Cause: Cert is not revoked

Action: n/a

NZE-29178: certificate serial number is in CRL

Cause: Cert has been revoked

Action: Reject the certificate

NZE-29179: certificate validation check failed

Cause: Could not complete checking certificate status with a CRL.

Action: Enable tracing to find more information on this error. Contact Oracle customer support if needed.

NZE-29180: Unsupported validation protocol

Cause: The certificate validation protocol is not supported

Action: Make sure a supported certificate validation protocol is specified

NZE-29181: ldap_open failed

Cause: Could not connect to the LDAP server

Action: Ensure that correct LDAP information was provided. Enable tracing to find more information. Contact Oracle customer support if needed.

NZE-29182: ldap_bind failed

Cause: Could not log in to the LDAP server

Action: Ensure that correct LDAP credentials were provided. Enable tracing to find more information. Contact Oracle customer support if needed.

NZE-29183: ldap_search failed

Cause: Failed to complete search operation in LDAP server

Action: Enable tracing to find more information on this error. Contact Oracle customer support if needed.

NZE-29184: ldap_result failed

Cause: Failed to retrieve results from LDAP operation

Action: Enable tracing to find more information on this error. Contact Oracle customer support if needed.

NZE-29185: ldap_first_attribute failed

Cause: Could not get the first attribute from LDAP entry.

Action: Enable tracing to find more information on this error. Contact Oracle customer support if needed.

NZE-29186: ldap_get_values_len failed

Cause: Failed to retrieve attribute values from LDAP entry

Action: Enable tracing to find more information on this error. Contact Oracle customer support if needed.

NZE-29187: unsupported validation mechanism

Cause: The validation mechanism specified in OID is not supported

Action: Make sure a supported validation mechanism is set in OID

NZE-29188: ldap_count_entries failed

Cause: Failed to get count of entries from a search result chain.

Action: Enable tracing to find more information on this error. Contact Oracle customer support if needed.

NZE-29189: No entry found in OID

Cause: CRL not found in OID

Action: Upload the CRL to OID

NZE-29190: Multiple entries in OID

Cause: For a given issuer name there should be only one CRL in OID

Action: Make sure there is only one CRL for a given issuer name in OID

NZE-29191: OID connection information not set

Cause: To connect to OID the connection information must be available

Action: Set the OID connection information.

NZE-29192: Validation mechanism not set in OID

Cause: The validation mechanism to be used is not set in OID

Action: Set validation mechanism to be used in OID at cn=ValidationMechanism, cn=Validation, cn=PKI, cn=Products, cn=OracleContext

NZE-29193: no CRL found using CRLDP mechanism

Cause: A CRL could not fetched using CRL Distribution point (CRLDP)

Action: Contact the CA

NZE-29194: no CRL found in cache

Cause: CRL not in cache

Action: n/a

NZE-29195: CRL is expired

Cause: CRL nextUpdate time is in the past

Action: Get a new CRL from the CA

NZE-29222: Distinguished name does not match.

Cause: Distinguished name (DN) on certificate doesn't match user.

Action: Create the global user in the database with the DN that matches with the one in the user certificate on the client side.

NZE-29223: Cannot create certificate chain.

Cause: Unable to create a certificate chain with the existing trust points for the certificate that is to be installed.

Action: Install the trust point that signed the certificate.

NZE-29224: Cannot locate matching certificate request.

Cause: No matching certificate request for the certificate was found.

Action: Install the correct certificate.

NZE-29225: Certificate already installed.

Cause: Attempting to install a certificate into a persona which already has it.

Action: Do not install the certificate.

NZE-29226: No matching private key found.

Cause: Could not locate a matching private key in the persona for the given certificate (public key).

Action: n/a

NZE-29227: Certificate is expired.

Cause: Certificate is no longer valid..

Action: Obtain another certificate or renew this certificate.

NZE-29228: Cannot calculate the number of bytes for output.

Cause: The cryptographic engine is confused about the algorithm.

Action: Check the parameters being used with the cryptographic functions.

NZE-29229: the magic number found in the header does not match expected

Cause: The input TDU has either been corrupted or is not being used correctly.

Action: Check that the TDU is being used from the beginning. If possible, compare the size of the TDU upon generation to the size being used.

NZE-29230: the header length is not sufficient for message header

Cause: The input TDU has either been corrupted or it is not being used correctly.

Action: Check that the TDU is being used from the beginning. If possible, compare the size of the TDU upon generation to the size being used.

NZE-29231: the cryptographic engine failed to initialize

Cause: During initialization of the cryptographic engine, some failure occurred. Possible causes include running out of memory and trying to seed the random number generator.

Action: Make sure the executable has been linked with compatible library versions, and that you are not running out of swap space.

NZE-29232: the cryptographic engine key initialization failed

Cause: During initialization of a key for cryptography, some failure occurred. This includes running out of memory and passing illegal arguments.

Action: Make sure the executable has been linked with compatible library versions, and that the correct parameters are being used for the cryptographic functions.

NZE-29233: the key object could not be encoded

Cause: The key object may be corrupted or may be an unsupported type.

Action: Check the key object being passed to the encoding routine.

NZE-29234: a key object was not extracted from encoding

Cause: The encoding may be corrupted or may not be a key object at all.

Action: Check the encoding and parameters passed to decoding routine.

NZE-29235: the key information could not be retrieved

Cause: The key may be corrupted or may be an unsupported type.

Action: Check the parameters being used with the cryptographic functions.

NZE-29236: the random number generator will not accept seed

Cause: The cryptographic engine may have run out of memory.

Action: Make sure the executable has been linked with compatible library versions.

NZE-29237: the cryptographic engine could not finish the algorithm

Cause: The cryptographic engine does not have enough information to correctly finish applying the algorithm.

Action: Check the parameters being used with the cryptographic functions.

NZE-29238: the cryptographic engine could not apply the algorithm

Cause: The cryptographic engine does not have enough information to correctly apply the algorithm.

Action: Check the parameters being used with the cryptographic functions.

NZE-29239: the cryptographic engine could not initialize the algorithm

Cause: The cryptographic engine does not have enough information to correctly initialize the algorithm.

Action: Check the parameters being used with the cryptographic functions.

NZE-29240: the cryptographic engine does not recognize the algorithm

Cause: The application may be passing wrong parameters.

Action: Check the parameters being used with the cryptographic functions.

NZE-29241: a buffer block needs more space but its length is fixed

Cause: The application has preallocated an output buffer that is too short for the operation and has specified that the buffer should not grow as needed.

Action: Either preallocate a larger buffer or allow the toolkit to grow the output buffer as needed.

NZE-29242: the asymmetric key is too short to be used with the data.

Cause: An asymmetric key must be at least 11 bytes longer than the data it is being used to encrypt.

Action: Use an asymmetric key with more bits or break the data into smaller pieces.

NZE-29243: the toolkit does not recognize the type of key being used

Cause: The application may be passing wrong parameters.

Action: Check the parameters being used with the toolkit functions.

NZE-29245: the toolkit does not recognize the function being used

Cause: The application is probably passing the wrong parameters.

Action: Check the parameters being used with the toolkit functions.

NZE-29246: the toolkit could not parse the tdu

Cause: The TDU could be corrupted.

Action: Check the parameters being used with the toolkit functions.

NZE-29247: an unopen toolkit object was used before it was opened

Cause: Some toolkit objects must be opened before they can be used.

Action: Check the parameters being used with the toolkit functions.

NZE-29248: an unrecognized WRL was used to open a wallet

Cause: WRL's have a specific set of types and must be formatted correctly.

Action: Check the parameters being used with the toolkit functions.

NZE-29249: an unrecognized state was passed to a cryptographic function

Cause: The application is probably passing the wrong parameters.

Action: Check the parameters being used with the toolkit functions.