Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
Cause: Some Oracle Security Server error occurred of an unspecified type. This error should not be visible to applications.
Action: Contact Oracle Support Services.
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.
Cause: The initialization of a data source failed.
Action: Enable Oracle Net tracing to determine the exact cause of the error. Frequently, this error is caused by the exhaustion of system resources.
Cause: The termination of the use of a data source failed.
Action: Enable Oracle Net tracing to determine the exact cause of the error. The error may be caused by the corruption of memory or disk, among other things.
Cause: This is an internal error.
Action: No action required.
Cause: Failure to retrieve subject information from a file or database.
Action: Check if the data source exists or check for the correct subject information.
Cause: A function supplied by the caller failed to allocate memory.
Action: This error could be due to system memory exhaustion.
Cause: No more memory.
Action: This error could be due to system memory exhaustion.
Cause: The release of memory fragment failed. This may be caused by corruption of memory either within the application or the Oracle Security Server library.
Action: Enable Oracle Net tracing to determine the reason why the operation failed.
Cause: The opening of the specified file failed.
Action: Enable Oracle Net tracing to determine the name of the file that could not be opened and the reason.
Cause: This is an internal error.
Action: No action required.
Cause: This is an internal error.
Action: No action required.
Cause: This is an internal error.
Action: No action required.
Cause: Possible error in parameter in SQLNET.ORA.
Action: Check the SQLNET.ORA file for this parameter value.
Cause: The retrieval of a configuration parameter failed.
Action: Supply the needed configuration parameter.
Cause: This is an internal error.
Action: No action required.
Cause: An error occurred when attempting to end use of a data source. This could be due to a system error.
Action: Enable tracing to see what the exact error is.
Cause: Version number of the file is incorrect.
Cause: An invalid magic number was specified in a data file.
Action: This could be due to disk corruption or some other process overwriting the file. Enable tracing to determine what the exact error is.
Cause: The data access method specified in the configuration file is not supported.
Action: Specify a supported method. Consult the Oracle Security Server documentation to determine the supported types.
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.
Cause: The caller attempted to use a data source which had not been initialized yet. This is a programming error. The application must always initialize the data source.
Action: Correct the error.
Cause: This is an internal error.
Action: No action required.
Cause: The write of both the magic and version numbers failed.
Action: This error usually occurs because disk space has been exhausted.
Cause: The output of a file failed.
Action: This error usually occurs because disk space has been exhausted.
Cause: The close of a file used by a data access method failed.
Action: This error usually indicates an error such as memory corruption or a system error. Enable tracing and examine the trace file to see what the exact error.
Cause: The data to be returned by a function is too large for the supplied buffer.
Action: Call the routine again with a larger buffer.
Cause: The creation of a binding for use in the parsing of a parameter value failed. This error can be caused by the parameter value being in an incorrect format, for example, a right parenthesis was not supplied where expected, or the exhaustion of 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 add more memory.
Cause: The configuration parameter was specified in the proper format.
Action: Consult the Oracle Security Server documentation for a description of the proper format for this parameter.
Cause: No method for data access was specified in the parameter value.
Action: Specify a parameter method. Consult the Oracle Security Server documentation for the supported data access methods for this data type.
Cause: The data access method specified by the parameter value is not supported.
Action: Specify a data access method. Consult the Oracle Security Server documentation for the supported data access methods for this data type.
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.
Cause: No memory was allocated for a data source.
Action: The application should call in the data source initialization function.
Cause: No match for parameter name in the configuration file.
Action: Check your SQLNET.ORA file for the parameter.
Cause: The translation of a file name from Oracle format to native format failed.
Action: Specify a correct name. Consult your Oracle documentation for the correct file name format.
Cause: A configuration parameter does not exist in a parameter file.
Action: Supply the required parameter.
Cause: Use of incorrect password for decryption.
Action: Type in the correct password.
Cause: Possible error in parameter for MKWALLET in SQLNET.ORA.
Action: Check your SQLNET.ORA file. Also turn on tracing and check the MKTOKEN.TRC file for other errors.
Cause: Incorrect input by the user in response to a prompt or an unknown error.
Action: Provide the correct input or enable tracing and check the trace file for errors.
Cause: This is an internal error.
Action: No action required.
Cause: The opening of a string for use by the NLS subsystem failed.
Action: Enable Oracle Net tracing to determine the exact error.
Cause: Verification of the certificate supplied by the user failed.
Action: Enable Oracle Net tracing to determine the exact error.
Cause: A PL/SQL operation attempted by the Oracle Security Server failed. This is an internal error.
Action: Enable Oracle Net and try the operation again. Contact Oracle Support Services for assistance.
Cause: This is an internal error.
Action: No action required.
Cause: The initialization of the attribute data type failed.
Action: Enable tracing to determine the exact error. This error may be caused by the exhaustion of system resources.
Cause: The termination of the use of the attribute data type subsystem failed.
Action: Enable Oracle Net tracing to determine the exact error.
Cause: The method specified to access data is not supported.
Action: Use a supported access method.
Cause: The type specified for a key is not supported.
Action: Correct the key type.
Cause: The number of keys passed by the application to bind does not match the number used to create the key. This is an internal programming exception.
Action: Contact Oracle Support Services.
Cause: The allocation of shared memory for use in operations involving the shared server failed.
Action: Enable Oracle Net tracing to determine the exact error. This error is probably caused by the exhaustion of the memory heap supplied by the Oracle server.
Cause: Failed to open the data source (file or database).
Action: Enable Oracle Net tracing to determine the exact error.
Cause: This is an internal error.
Action: No action required.
Cause: Mode or data source specified in configuration file is incorrect.
Action: Check the SQLNET.ORA file for method parameter. Else enable Oracle Net tracing to determine the exact error.
Cause: Failed to access a data source (file or database).
Action: Enable Oracle Net tracing to determine the exact error.
Cause: Failed to close the data source (file or database).
Action: Enable Oracle Net tracing to determine the exact error.
Cause: Failed to retrieve information from the data source (file or database).
Action: Enable Oracle Net tracing to determine the exact error.
Cause: Failed to write to the data source (file or database).
Action: Enable Oracle Net tracing to determine the exact error.
Cause: Failed to update a data source (file or database).
Action: Enable Oracle Net tracing to determine the exact error.
Cause: Failed to retrieve method (file/database) information.
Action: Check the SQLNET.ORA file for method configuration parameters. Else enable Oracle Net tracing to determine the exact error.
Cause: Failed to delete information from data source.
Action: Enable Oracle Net tracing to determine the exact error.
Cause: Failed to create a key descriptor.
Action: Enable Oracle Net tracing to determine the exact error.
Cause: This is an internal error.
Action: No action required.
Cause: This is an internal error.
Action: No action required.
Cause: This is an internal error.
Action: No action required.
Cause: The conversion of a number which was specified in Oracle format to native format failed. This is an internal programming exception.
Action: Enable Oracle Net tracing and attempt to reproduce the problem. Contact Oracle Support Services and supply the trace file.
Cause: The conversion of a number which was specified in native format to Oracle portable format failed. This is an internal programming exception.
Action: Enable Oracle Net tracing and attempt to reproduce the problem. Contact Oracle Support Services and supply the trace file.
Cause: A required password was not passed to a PL/SQL function. This is an internal error.
Action: Contact Oracle Support Services.
Cause: A PL/SQL function returned an error unexpectedly. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The context that holds the state of the security package was not passed to a function or procedure that was expecting it. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The user's distinguished name was not provided to a PL/SQL function or procedure. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The state of either a signature or decryption/encryption was not passed to a PL/SQL function or procedure. This is an internal error.
Action: Contact Oracle Support Services.
Cause: A PL/SQL function or procedure was not passed an expected buffer. This is an internal error.
Action: Contact Oracle Support Services.
Cause: No seed was specified to the PL/SQL seed initialization function. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The number of random bytes to generate was not specified to the PL/SQL random number generator. This is an internal error.
Action: Contact Oracle Support Services.
Cause: An invalid state was passed to a PL/SQL encryption, decryption or signature procedure or function.
Action: Specify a correct state value.
Cause: No function was specified for the cryptographic engine. This is an internal error.
Action: Contact Oracle Support Services.
Cause: An incorrect cryptographic engine function was passed to a PL/SQL function or procedure.
Action: Specify a correct engine function.
Cause: An incorrect cipher type was passed to a PL/SQL function or procedure.
Action: Specify a correct cipher type.
Cause: An incorrect identity type was passed to a PL/SQL function or procedure.
Action: Specify a correct identity type.
Cause: No cipher type was passed to a PL/SQL function or procedure. This is an internal error.
Action: Contact Oracle Support Services.
Cause: No identity type was passed to a PL/SQL function or procedure. This is an internal error.
Action: Contact Oracle Support Services.
Cause: No data unit format was passed to a PL/SQL function or procedure. This is an internal error.
Action: Contact Oracle Support Services.
Cause: An incorrect data unit format was passed to a PL/SQL function or procedure.
Action: Specify a data unit format.
Cause: Not enough info (usually parameters) provided to a PL/SQL function. This is an internal error.
Action: Contact Oracle Support Services.
Cause: Buffer provided by PL/SQL to a Oracle Security Server toolkit function is too small for the data to be returned. This is an internal error.
Action: Contact Oracle Support Services.
Cause: An identity descriptor passed to a PL/SQL function or descriptor was not provided or does not have the correct size. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The wallet to be used has not been opened yet.
Action: Call the function that opens the wallet.
Cause: No wallet descriptor was specified to a PL/SQL function or procedure. This is an internal error.
Action: Contact Oracle Support Services.
Cause: No identity descriptor was specified to a PL/SQL function or procedure. This is an internal error.
Action: Contact Oracle Support Services.
Cause: No persona descriptor was specified to a PL/SQL function or procedure. This is an internal error.
Action: Contact Oracle Support Services.
Cause: An attempt was made to open a wallet that had already been opened. This is a programming error. A wallet should only be opened once.
Action: Correct the error.
Cause: An attempt was made to perform an operation that is not supported. This is a programming error.
Action: Correct the error.
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.
Cause: An unsupported operation was attempted, for example, an unknown cipher specification or an incorrect version.
Action: Specify a correct value.
Cause: A buffer overflowed during the SSL handshake.
Action: This error is not normally visible to the user. Enable tracing and attempt the connection again. If the error persists, contact Oracle Support Services.
Cause: An unknown SSL error occurred.
Action: This error is not normally visible to the user. Enable tracing and attempt the connection again. If the error persists, contact Oracle Support Services.
Cause: An error occurred during the SSL handshake between two processes.
Action: This error is not normally visible to the user. Enable tracing and attempt the connection again. If the error persists, contact Oracle Support Services.
Cause: An error occurred during the negotiation done 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 or if the SSL versions on both sides are incompatible.
Action: Configure each process so they support a common cipher suite and compatible versions and then attempt the connection again.
Cause: An error occurred during the SSL connection.
Action: This error is not normally visible to the user. Enable tracing and attempt the connection again. If the error persists, contact Oracle Support Services.
Cause: This error is informational only. It should never be communicated to the user.
Action: This error is not normally visible to the user. Enable tracing and attempt the connection again. If the error persists, contact Oracle Support Services.
Cause: This error can occur when one side of the connection fails for one reason or another. For example, the process might have been terminated.
Action: Attempt the connection again.
Cause: This error is informational only. It indicates that a specified session does not exist.
Action: This error is not normally visible to the user. Enable tracing and attempt the connection again. If the error persists, contact Oracle Support Services.
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 tracing and attempt the connection again. If the error persists, contact Oracle Support Services.
Cause: The SSL connection closed because of an error in the underlying transport or because the destination process unexpectedly quit.
Action: Enable tracing and attempt the connection again. The trace output should indicate how the failure occurred.
Cause: The presented certificate had a field that could not be recognized.
Action: Verify that the certificate is correct. If it is, enable tracing and attempt the connection again. If the error persists, contact Oracle Support Services.
Cause: The certificate presented had an integer field whose value was too large.
Action: Verify that the certificate is correct. If it is, enable tracing and attempt the connection again. If the error persists, contact Oracle Support Services.
Cause: The check of the certificate list presented by the remote process failed. This could be caused by a number of problems including:
Action: Make sure that:
Cause: The certificate being used to authenticate a client or server has expired.
Action: Obtain a certificate which has not expired and attempt the connection again.
Cause: A comparison between the names contained within two certificates failed.
Action: This error is not normally visible to the user. Enable tracing and attempt the connection again. If the error persists, contact Oracle Support Services.
Cause: The certificate chain presented was not incomplete. In other words, the chain did not end with a self-signed root certificate.
Action: Make sure that the certificate specified as the root is self-signed.
Cause: The certificate presented by the other process does not conform to the X.509v3 standard.
Action: Obtain a certificate that conforms to the standard and attempt the connection again.
Cause: A function was presented with a null parameter.
Action: This error is not normally visible to the user. Enable tracing and attempt the connection again. If the error persists, contact Oracle Support Services.
Cause: This error is informational only. It indicates that a specified session does not exist.
Action: This error is not normally visible to the user. Enable tracing and attempt the connection again. If the error persists, contact Oracle Support Services.
Cause: This error is used as a internal status indicator and not really an error.
Action: This error is not normally visible to the user. Enable tracing and attempt the connection again. If the error persists, contact Oracle Support Services.
Cause: An error occurred when processing a certificate sent from Microsoft Internet Explorer.
Action: This error is not normally visible to the user. Enable tracing and attempt the connection again. If the error persists, contact Oracle Support Services.
Cause: An application attempted to provide credentials to an SSL connection but had not previously stated whether the process was a client or server.
Action: This error is not normally visible to the user. Enable tracing and attempt the connection again. If the error persists, contact Oracle Support Services.
Cause: An application attempted to convert a cipher suite to a string representation but the value did not correspond to a known cipher suite.
Action: Specify a correct value for the cipher suite. If, however, this error is returned by the Oracle Net SSL protocol adapter, it should be reported to Oracle Support Services as this error should not be returned by the adapter.
Cause: An application's attempt to login to Entrust Profile failed. This could be caused by a number of problems including:
Action: Make sure that:
For more information, enable tracing and the trace output should indicate the exact Entrust failure codes.
Cause: Client detects mismatched Distinguished Name from server's certificate. Server's Distinguished Name does not reflect its SID or ServiceName.
Action: It may not be safe to connect to the server. Contact your administrator to update the server's certificate to reflect server's database name or service name.
Cause: Client detects mismatch from server's DN and the security configuration.
Action: It may not be safe to connect to the server. Contact your administrator to configure client TNS connect data to reflect the server Distinguished Name.
Cause: The cryptographic engine is confused about the algorithm.
Action: Check the parameters being used with the cryptographic functions.
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 trying to be used.
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 trying to be used.
Cause: During initialization of the cryptographic engine, some failure occurred. This includes 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.
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.
Cause: The key object may be corrupted or may be an unsupported type.
Action: Check the key object being passed to the encoding routine.
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.
Cause: The key may be corrupted or may be an unsupported type.
Action: Check the parameters being used with the cryptographic functions.
Cause: The cryptographic engine may have run out of memory.
Action: Make sure the executable has been linked with compatible library versions.
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.
Cause: The cryptographic engine does not have enough information to correctly apply the algorithm.
Action: Check the parameters being used with the cryptographic functions.
Cause: The cryptographic engine does not have enough information to correctly initialize the algorithm.
Action: Check the parameters being used with the cryptographic functions.
Cause: The application is probably passing the wrong parameters.
Action: Check the parameters being used with the cryptographic functions.
Cause: The application has pre-allocated an output buffer that is too short for the operation and has specified that the buffer should not grow as needed.
Action: Either pre-allocate a larger buffer or allow the toolkit to grow the output buffer as needed.
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.
Cause: The application is probably passing the wrong parameters.
Action: Check the parameters being used with the toolkit functions.
Cause: The application is probably passing the wrong parameters.
Action: Check the parameters being used with the toolkit functions.
Cause: The TDU could be corrupted.
Action: Check the parameters being used with the toolkit functions.
Cause: Some toolkit objects must be opened before they can be used.
Action: Check the parameters being used with the toolkit functions.
Cause: WRLs have a specific set of types and must be formatted correctly.
Action: Check the parameters being used with the toolkit functions.
Cause: The application is probably passing the wrong parameters.
Action: Check the parameters being used with the toolkit functions.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
