Oracle Error Messages: 11/15/11

NZE-29224: Cannot locate matching certificate request.

NZE-29224: Cannot locate matching certificate request.

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

Action: Install the correct certificate if there is one.

NZE-29223: Cannot create certificate chain.

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-29222: Distinguished name does not match.

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-29195: CRL is expired

NZE-29195: CRL is expired

Cause: CRL nextUpdate time is in the past

Action: Get a new CRL from the CA

NZE-29194: no CRL found in cache

NZE-29194: no CRL found in cache

Cause: CRL not in cache

Action: none

NZE-29193: no CRL found using CRLDP mechanism

NZE-29193: no CRL found using CRLDP mechanism

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

Action: Discuss with CA

NZE-29192: Validation mechanism not set in OID

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-29191: OID connection information not set

NZE-29191: OID connection information not set

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

Action: Set the OID connection info

NZE-29190: Multiple entries in 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-29189: No entry found in OID

NZE-29189: No entry found in OID

Cause: CRL not found in OID

Action: Upload the CRL to OID

NZE-29187: unsupported validation mechanism

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-29180: Unsupported validation protocol

NZE-29180: Unsupported validation protocol

Cause: The certificate validation protocol is not supported

Action: Make sure a supported certificate validation protocol is specified

NZE-29178: certificate serial number is in CRL

NZE-29178: certificate serial number is in CRL

Cause: Cert has been revoked

Action: Reject the certificate

NZE-29177: certificate serial number is not in CRL

NZE-29177: certificate serial number is not in CRL

Cause: Cert is not revoked

Action: none

NZE-29176: CRL signature verification failed

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-29164: External PKCS #12 wallet is not supported 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-28776: Output buffer supplied is too small.

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-28775: file cannot close

NZE-28775: file cannot close

Cause: The closing of a file, which is used by a data access method, has failed. This error usually indicates memory corruption or a system error.

Action: Enable Oracle Net tracing and examine the trace file to see exactly what error occurred.

NZE-28774: file cannot write to disk

NZE-28774: file cannot write to disk

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

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

NZE-28773: failure to write magic and version numbers

NZE-28773: failure to write magic and version numbers

Cause: Both the magic and version numbers failed to write. This usually occurs because disk space has been exhausted.

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

NZE-28772: invalid file ID

NZE-28772: invalid file ID

Cause: Error not user-visible.

Action: none

NZE-28771: Data source is not yet initialized.

NZE-28771: Data source is not yet initialized.

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

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

NZE-28770: Data source is already initialized.

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-28769: Specified method does not exist.

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-28768: bad magic number

NZE-28768: bad magic number

Cause: d by a corrupted disk or by some other process overwriting the file.

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

NZE-28767: invalid version number

NZE-28767: invalid version number

Cause: Version number of a file was incorrect.

Action: Replace the file with the correct version.

NZE-28766: failure to terminate use of data source

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 Oracle Net tracing to determine the exact cause of the error.

NZE-28765: Data method list does not exist.

NZE-28765: Data method list does not exist.

Cause: Error not user-visible.

Action: none

NZE-28764: failure to retrieve a configuration parameter

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-28763: Invalid parameter type found in configuration file.

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-28762: failure to add element

NZE-28762: failure to add element

Cause: Error not user-visible.

Action: none

NZE-28761: element creation failure

NZE-28761: element creation failure

Cause: Error not user-visible.

Action: none

NZE-28760: list creation failure

NZE-28760: list creation failure

Cause: Error not user-visible.

Action: none

NZE-28759: failure to open file

NZE-28759: failure to open file

Cause: The system could not open the specified file.

Action: Enable Oracle Net tracing to determine the name of the file that could not be opened and the reason.

NZE-28758: memory release failure

NZE-28758: memory release failure

Cause: The release of a memory fragment failed. This may have been caused by memory corruption either within the application or in the Oracle Security Server library.

Action: Enable Oracle Net tracing to determine the reason why the operation failed.

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

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

Cause: The system attempted to allocate 0 bypes of memory because there was no available memory left to allocate. 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-28756: callback failure to allocate memory

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-28755: object retrieval failure

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-28754: object storage failure

NZE-28754: object storage failure

Cause: Error not user-visible.

Action: none

NZE-28753: failure to terminate use of data source

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 Oracle Net tracing to determine the exact cause of the error.

NZE-28752: data source initialization failure

NZE-28752: data source initialization failure

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

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

NZE-28751: memory allocation failure

NZE-28751: 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-28750: unknown error

NZE-28750: unknown error

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

Action: Contact your customer support representative. This error should not be visible to applications.

NCR-04028: NCRR: Operation failed

NCR-04028: NCRR: Operation failed

Cause: An operation for the Oracle Internet Directory server failed because the data involved exceeds the maximum allowed size.

Action: Check the entries in the Oracle Internet Directory instance with tools available from Oracle Internet Directory and or or turn on Oracle Internet Directory tracing.

NCR-04027: NCRR: Operation failed

NCR-04027: NCRR: Operation failed

Cause: An operation for the Oracle Internet Directory server failed because the Service Registration interfaces met with invalid parameters.

Action: Contact customer support.

NCR-04026: NCRR: Operation not supported

NCR-04026: NCRR: Operation not supported

Cause: An operation for the Oracle Internet Directory server failed because it met with a server referral to another instance.

Action: Unify the Remote Ops registration entries into the Oracle Internet Directory instance and or or turn on Oracle Internet Directory tracing.