Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 28750-29249: Security Server Messages

For more security server messages, see 28000-28499: Security-Related Messages on page -399.

##### ORA-28750: unknown error occurred

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.

##### ORA-28751: memory allocation failed

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.

##### ORA-28752: failed to initialize data source

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.

##### ORA-28753: failed to terminate use of data source

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.

##### ORA-28755: object retrieval failed

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.

##### ORA-28756: callback failed to allocate memory

Cause: A function supplied by the caller failed to allocate memory.

Action: This error could be due to system memory exhaustion.

##### ORA-28757: attempted to allocate 0 bytes of memory

Cause: Memory has been exhausted.

Action: This error could be due to system memory exhaustion.

##### ORA-28758: memory release failed

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.

##### ORA-28759: failed to open file

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.

##### ORA-28763: invalid parameter type

Cause: Possible error in parameter in SQLNET.ORA.

Action: Check the SQLNET.ORA file for this parameter value.

##### ORA-28764: configuration parameter retrieval failed

Cause: The retrieval of a configuration parameter failed.

Action: Supply the needed configuration parameter.

##### ORA-28766: failed to terminate use of data source

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.

##### ORA-28767: invalid version number

Cause: Version number of the file is incorrect.

Action: Enter the correct version number and retry the operation.

##### ORA-28768: bad magic number

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.

##### ORA-28769: specified method does not exist

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.

##### ORA-28770: data source 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.

##### ORA-28771: data source 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.

##### ORA-28773: write of magic and version numbers failed

Cause: The write of both the magic and version numbers failed.

Action: This error usually occurs because disk space has been exhausted.

##### ORA-28774: write of file to disk failed

Cause: The output of a file failed.

Action: This error usually occurs because disk space has been exhausted.

##### ORA-28775: close of file failed

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.

##### ORA-28776: output buffer supplied is too small

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.

##### ORA-28777: binding creation failed

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.

##### ORA-28778: parameter not specified in 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.

##### ORA-28779: no data access method specified in 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.

##### ORA-28780: invalid method specified by parameter

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.

##### ORA-28781: no method data specified in 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.

##### ORA-28782: data source not allocated

Cause: No memory was allocated for a data source.

Action: The application should call in the data source initialization function.

##### ORA-28783: invalid parameter

Cause: No match for parameter name in the configuration file.

Action: Check your SQLNET.ORA file for the parameter.

##### ORA-28784: file name translation failed

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.

##### ORA-28785: parameter does not exist

Cause: A configuration parameter does not exist in a parameter file.

Action: Supply the required parameter.

##### ORA-28786: unknown cryptographic algorithm

Cause: Use of incorrect password for decryption.

Action: Type in the correct password.

##### ORA-28787: failed to allocate more memory

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.

##### ORA-28788: invalid key size

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.

##### ORA-28790: NLS string open failed

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

Action: Enable Net8 tracing to determine the exact error.

##### ORA-28791: certificate verification failed

Cause: Verification of the certificate supplied by the user failed.

Action: Enable Net8 tracing to determine the exact error.

##### ORA-28792: PL/SQL operation failed

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.

##### ORA-28794: attribute initialization data type failed

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.

##### ORA-28795: attribute data type termination failed

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

Action: Enable Net8 tracing to determine the exact error.

##### ORA-28796: unsupported access method

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

Action: Use a supported access method.

##### ORA-28797: invalid data type

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

Action: Correct the key type and retry the operation.

##### ORA-28798: number of sub-keys to bind does not match that in key

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.

##### ORA-28799: failed to allocate shared memory

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.

##### ORA-28800: open failed

Cause: Failed to open the data source (file or database).

Action: Enable Net8 tracing to determine the exact error.

##### ORA-28802: invalid mode specified

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.

##### ORA-28803: input/output operation failed

Cause: Failed to access a data source(file or database).

Action: Enable Net8 tracing to determine the exact error.

##### ORA-28804: close failed

Cause: Failed to close the data source(file or database).

Action: Enable Net8 tracing to determine the exact error.

##### ORA-28805: retrieve failed

Cause: Failed to retrieve information from the data source (file or database).

Action: Enable Net8 tracing to determine the exact error.

##### ORA-28806: store failed

Cause: Failed to write to the data source(file or database).

Action: Enable Net8 tracing to determine the exact error.

##### ORA-28807: update failed

Cause: Failed to update a data source(file or database).

Action: Enable Net8 tracing to determine the exact error.

##### ORA-28808: retrieval of method information failed

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.

##### ORA-28809: deletion failed

Cause: Failed to delete information from data source.

Action: Enable Net8 tracing to determine the exact error.

##### ORA-28810: creation failed

Cause: Failed to create a key descriptor.

Action: Enable Net8 tracing to determine the exact error.

##### ORA-28814: conversion of number in Oracle format to native failed

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.

##### ORA-28815: Conversion of native number to Oracle format failed

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.

##### ORA-28816: no password provided

Cause: A required password was not passed to a PL/SQL function.

Action: This is an internal error. Contact Oracle Worldwide Support.

##### ORA-28817: PL/SQL function returned an error

Cause: A PL/SQL function returned an error unexpectedly.

Action: This is an internal error. Contact Oracle Worldwide Support.

##### ORA-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. Contact Oracle Worldwide Support.

##### ORA-28819: no distinguished name provided

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.

##### ORA-28820: state not provided

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.

##### ORA-28821: no input buffer provided

Cause: A PL/SQL function or procedure was not passed an expected buffer.

Action: This is an internal error. Contact Oracle Worldwide Support.

##### ORA-28822: no seed

Cause: No seed was specified to the PL/SQL seed initialization function.

Action: This is an internal error. Contact Oracle Worldwide Support.

##### ORA-28823: number of bytes not specified

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.

##### ORA-28824: invalid encryption/decryption/signature state

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.

##### ORA-28825: no cryptographic engine function

Cause: No function was specified for the cryptographic engine.

Action: This is an internal error. Contact Oracle Worldwide Support.

##### ORA-28826: invalid cryptographic engine function

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.

##### ORA-28827: invalid cipher type

Cause: An incorrect cipher type was passed to a PL/SQL function or procedure.

Action: Specify a correct cipher type and retry the operation.

##### ORA-28828: invalid identity type

Cause: An incorrect identity type was passed to a PL/SQL function or procedure.

Action: Specify a correct identity type and retry the operation.

##### ORA-28829: no cipher type specified

Cause: No cipher type was passed to a PL/SQL function or procedure.

Action: This is an internal error. Contact Oracle Worldwide Support.

##### ORA-28830: no identity type specified

Cause: No identity type was passed to a PL/SQL function or procedure.

Action: This is an internal error. Contact Oracle Worldwide Support.

##### ORA-28831: no data unit format

Cause: No data unit format was passed to a PL/SQL function or procedure.

Action: This is an internal error. Contact Oracle Worldwide Support.

##### ORA-28832: invalid data unit format

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.

##### ORA-28833: not enough info provided

Cause: Not enough info (usually parameters) provided to a PL/SQL function

Action: This is an internal error. Contact Oracle Worldwide Support.

##### ORA-28834: buffer too small

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.

##### ORA-28835: identity descriptor not present or too small

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.

##### ORA-28836: wallet not open

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

Action: Call the function that opens the wallet and retry the operation.

##### ORA-28837: no wallet descriptor

Cause: No wallet descriptor was specified to a PL/SQL function or procedure.

Action: This is an internal error. Contact Oracle Worldwide Support.

##### ORA-28838: no identity descriptor

Cause: No identity descriptor was specified to a PL/SQL function or procedure.

Action: This is an internal error. Contact Oracle Worldwide Support.

##### ORA-28839: no persona descriptor

Cause: No persona descriptor was specified to a PL/SQL function or procedure.

Action: This is an internal error. Contact Oracle Worldwide Support.

##### ORA-28840: wallet already open

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.

##### ORA-28841: operation not supported

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

Action: This is a programming error.

##### ORA-29228: the number of bytes for output could not be calculated

Cause: The cryptographic engine is confused about the algorithm.

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

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

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.

##### ORA-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 trying to be used.

##### ORA-29231: the cryptographic engine failed to initialize

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.

##### ORA-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.

##### ORA-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.

##### ORA-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.

##### ORA-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.

##### ORA-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.

##### ORA-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.

##### ORA-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.

##### ORA-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.

##### ORA-29240: the cryptographic engine does not recognize the algorithm

Cause: The application probably passed the wrong parameters.

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

##### ORA-29241: a buffer block needs to 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.

##### ORA-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.

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

Cause: The application probably passed the wrong parameters.

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

##### ORA-29245: the toolkit does not recognize the function being used

Cause: The application probably passed the wrong parameters.

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

##### ORA-29246: the toolkit could not parse the TDU

Cause: The TDU could be corrupted.

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

##### ORA-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.

##### ORA-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.

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

Cause: The application probably passed the wrong parameters.

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

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index