Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
For more security server messages, see 28000-28499: Security-Related Messages on page -399.
Cause: An Oracle Security Service error of unspecified type occurred.
Action: Contact your Oracle Worldwide Support representative. This error should not be visible to applications.
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 Net8 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: Enabled Net8 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: There was a 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: Memory has been exhausted.
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 Net8 tracing to determine the reason why the operation failed.
Cause: The opening of the specified file failed.
Action: Enable Net8 tracing to determine the name of the file that could not be opened and the reason.
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: 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.
Action: Enter the correct version number and retry the operation.
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.
Action: This is a programming error. The application must always initialize the data source.
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, e.g. 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 not 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 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: The allocation of memory to grow a buffer failed due to exhaustion of system memory.
Action: Terminate other processes to free up memory or add memory to the system.
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: The opening of a string for use by the NLS subsystem failed.
Action: Enable Net8 tracing to determine the exact error.
Cause: Verification of the certificate supplied by the user failed.
Action: Enable Net8 tracing to determine the exact error.
Cause: A PL/SQL operation attempted by the Oracle Security Service failed.
Action: This is an internal error. Enable Net8 and try the operation again. Contact Oracle Worldwide Support for assistance.
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 Net8 tracing to determine the exact error.
Cause: The method specified to access data is not supported.
Action: Use a supported access method.
Cause: The data type specified for a key is not supported.
Action: Correct the key type and retry the operation.
Cause: The number of keys passed by the application to bind does not match the number used to create the key.
Action: This is an internal programming exception. Contact your Oracle Worldwide Support representative.
Cause: The allocation of shared memory for use in operations involving the shared server failed.
Action: Enable Net8 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 Net8 tracing to determine the exact error.
Cause: Mode or data source specified in configuration file is incorrect.
Action: Check the SQLNET.ORA file for method parameter. Else enable Net8 tracing to determine the exact error.
Cause: Failed to access a data source(file or database).
Action: Enable Net8 tracing to determine the exact error.
Cause: Failed to close the data source(file or database).
Action: Enable Net8 tracing to determine the exact error.
Cause: Failed to retrieve information from the data source (file or database).
Action: Enable Net8 tracing to determine the exact error.
Cause: Failed to write to the data source(file or database).
Action: Enable Net8 tracing to determine the exact error.
Cause: Failed to update a data source(file or database).
Action: Enable Net8 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 Net8 tracing to determine the exact error.
Cause: Failed to delete information from data source.
Action: Enable Net8 tracing to determine the exact error.
Cause: Failed to create a key descriptor.
Action: Enable Net8 tracing to determine the exact error.
Cause: The conversion of a number which was specified in Oracle format to native format failed.
Action: This is an internal programming exception. Enable Net8 tracing and attempt to reproduce the problem. Contact your customer support representative and supply the trace file.
Cause: The conversion of a number which was specified in native format to Oracle portable format failed.
Action: This is an internal programming exception. Enable Net8 tracing and attempt to reproduce the problem. Contact your customer support representative and supply the trace file.
Cause: A required password was not passed to a PL/SQL function.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: A PL/SQL function returned an error unexpectedly.
Action: This is an internal error. Contact Oracle Worldwide Support.
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. Contact Oracle Worldwide Support.
Cause: The user's distinguished name was not provided to a PL/SQL function or procedure.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: The state of either a signature or decryption/encryption was not passed to a PL/SQL function or procedure.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: A PL/SQL function or procedure was not passed an expected buffer.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: No seed was specified to the PL/SQL seed initialization function.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: The number of random bytes to generate was not specified to the PL/SQL random number generator.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: An invalid state was passed to a PL/SQL encryption, decryption or signature procedure or function.
Action: Specify a correct state value and retry the operation.
Cause: No function was specified for the cryptographic engine.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: An incorrect cryptographic engine function was passed to a PL/SQL function or procedure.
Action: Specify a correct engine function and retry the operation.
Cause: An incorrect cipher type was passed to a PL/SQL function or procedure.
Action: Specify a correct cipher type and retry the operation.
Cause: An incorrect identity type was passed to a PL/SQL function or procedure.
Action: Specify a correct identity type and retry the operation.
Cause: No cipher type was passed to a PL/SQL function or procedure.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: No identity type was passed to a PL/SQL function or procedure.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: No data unit format was passed to a PL/SQL function or procedure.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: An incorrect data unit format was passed to a PL/SQL function or procedure.
Action: Specify a data unit format and retry the operation.
Cause: Not enough info (usually parameters) provided to a PL/SQL function
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: Buffer provided by PL/SQL to a Oracle Security Server toolkit function is too small for the data to be returned
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: An identity descriptor passed to a PL/SQL function or descriptor was not provided or does not have the correct size.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: The wallet to be used has not been opened yet.
Action: Call the function that opens the wallet and retry the operation.
Cause: No wallet descriptor was specified to a PL/SQL function or procedure.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: No identity descriptor was specified to a PL/SQL function or procedure.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: No persona descriptor was specified to a PL/SQL function or procedure.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: An attempt was made to open a wallet that had already been opened.
Action: This is a programming error. A wallet should only be opened once.
Cause: An attempt was made to perform an operation that is not supported.
Action: This is a programming error.
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 probably passed the wrong parameters.
Action: Check the parameters being used with the cryptographic functions.
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.
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 probably passed the wrong parameters.
Action: Check the parameters being used with the toolkit functions.
Cause: The application probably passed 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: WRL's have a specific set of types and must be formatted correctly.
Action: Check the parameters being used with the toolkit functions.
Cause: The application probably passed the wrong parameters.
Action: Check the parameters being used with the toolkit functions.
