| Cause | This function has yet to be implemented. |
| Action | This function will be supported in the next version. |
| Cause | The argument type or value is invalid. |
| Action | Modify the argument type or value. |
| Cause | The package instance is invalid and has been removed from the session. |
| Action | Use the package member to recreate the instance. |
| Cause | The error message number is out of range - error number must be an integer between -20000 and -20999. |
| Action | Specify a valid error number. |
| Cause | Radian values must be between -1 and 1 (-1 < x < 1). |
| Action | Specify a valid radian value. |
| Cause | The argument of the extract() function is invalid. |
| Action | Choose a proper value within the ranges of DATETIME or INTERVAL. |
| Cause | The length of LOB is too long. It cannot be longer than 4GB - 1 byte. |
| Action | Check the parameter. |
| Cause | The seed value is invalid. |
| Action | Check if the seed value is NULL. |
| Cause | The length of the seed value is too short. |
| Action | The seed value must contain more than 80 characters. |
| Cause | The key value is invalid. |
| Action | The key must contain more than eight characters. |
| Cause | The size of the input parameter is invalid. |
| Action | Set the length of input parameter to a multiple of eight bytes. |
| Cause | The DES mode is invalid. |
| Action | Choose either TWO KEY MODE or TRIPLE KEY MODE only. |
| Cause | The buffer size exceeded the maximum limit. |
| Action | Increase the buffer size, or delete some contents of the buffer. |
| Cause | An invalid value was specified. |
| Action | Verify an identical value was not already set. |
| Cause | The savepoint value is invalid. |
| Action | Verify the parameter is NULL. |
| Cause | The actual length does not match the length value. |
| Action | Verify that the number format is correct. |
| Cause | The endian value is invalid. |
| Action | Specify big endian (1) or little endian (2) only. |
| Cause | The length value is invalid. |
| Action | Verify that the length value is correct. |
| Cause | The number of open files has reached the maximum. |
| Action | Close some open files. |
| Cause | The line size exceeded the maximum limit (32768). |
| Action | Reduce the value of the MAX_LINESIZE parameter. |
| Cause | The directory name or path is invalid. |
| Action | Verify that the path name is correct. |
| Cause | Invalid file name. |
| Action | Verify that the file name is correct. |
| Cause | The ID of a closed or invalid file was used. |
| Action | Check the current condition of the file. |
| Cause | Invalid OPENMODE specified. |
| Action | Specify a valid FILE_OPENMODE_x [x = A, R, W, AB, RB, WB]. |
| Cause | Invalid offset value specified. |
| Action | Specify a valid offset value. |
| Cause | The length value is invalid. |
| Action | Specify an integer that is greater than or equal to 0. |
| Cause | An attempt was made to perform an invalid operation on the file. |
| Action | Verify the authority for the path is correct. |
| Cause | The amount of data to be written to a single line exceeds the maximum allowed. |
| Action | The length of a line cannot exceed the maximum. The maximum size is specified in the max_linesize parameter. |
| Cause | An attempt was made to perform an invalid read on the file. |
| Action | Check the file's OPENMODE. |
| Cause | The specified file name already exists. |
| Action | Either overwrite or delete the existing file. |
| Cause | The file to be deleted does not exist. |
| Action | Verify that the file exists. |
| Cause | Internal system error. |
| Action | Contact the system administrator. |
| Cause | The character sets do not match. |
| Action | Verify that the character sets are correct. |
| Cause | Access to the file or directory was denied. |
| Action | Modify permissions or use the user directory. |
| Cause | The task cannot be executed on an open file. |
| Action | Close the file and try again. |
| Cause | A job matching the job number has not been added to the job queue. |
| Action | Check the job number and try again. |
| Cause | An error occurred while executing job [%1$d]. |
| Action | Verify that a DD object related to the job exists. |
| Cause | The argument value is invalid, NULL, or out of range. |
| Action | Correct the argument value. |
| Cause | The specified directory could not be found. |
| Action | Verify that the directory exists. |
| Cause | Access to the directory or file was denied. |
| Action | Verify that the user has permission to access the directory or file. |
| Cause | The directory is invalid. |
| Action | Check the directory or contact the DBA. |
| Cause | Invalid file access method. |
| Action | Verify that the file access method is correct. |
| Cause | The file is not open. |
| Action | Open the file first. |
| Cause | The number of open files has reached the maximum. |
| Action | Close some open files. |
| Cause | A lock has already been obtained by another user. |
| Action | Try later. |
| Cause | Statements were executed in the wrong order. |
| Action | Execute PSM statements following the fetch sequence. |
| Cause | The bind parameters are not all bound yet. |
| Action | Perform the bind_variable function for all parameters. |
| Cause | The column_value function was executed in a column type other than the defined one. |
| Action | Execute column_value in a column type that matches the defined type. |
| Cause | Too many cursors were opened in a single session with the DBMS_SQL package. |
| Action | Decrease the number of cursors to open. |
| Cause | An attempt was made to call a function in a statement that had not yet been parsed. |
| Action | Parse the statement first and then call the bind_variable, execute and fetch_rows functions. |
| Cause | An attempt was made to define a column that does not exist in the SELECT list, or bring an undefined column. |
| Action | Verify the definition matches the SELECT list, and the column_value was called by the defined column. |
| Cause | The URL contains a malformed code sequence. |
| Action | Check the URL. |
| Cause | The HTTP server request failed. |
| Action | Verify the HTTP server is properly running. A request may fail due to timeout. |
| Cause | The URL is invalid. |
| Action | Check the URL. |
| Cause | Unknown scheme (scheme://) was included in the URL. |
| Action | Verify it is a supported scheme. |
| Cause | Either there is no header in the response from the server, or a header cannot be parsed since the response is not correct. |
| Action | Verify the response from the server is correct. |
| Cause | There is no response from the server. |
| Action | Verify the server is properly running and that the network delay time is under 20 seconds. |
| Cause | The dump option is invalid. |
| Action | Verify the dump option is correct. |
| Cause | The tablespace name is invalid. |
| Action | Verify the tablespace name is correct. |
| Cause | The datafile number is invalid. |
| Action | Verify the datafile number is correct. |
| Cause | The block number is invalid. |
| Action | Verify the block number is correct. |
| Cause | The segment owner is invalid. |
| Action | Verify the segment owner is correct. |
| Cause | The segment name is invalid. |
| Action | Verify the segment name is correct. |
| Cause | The segment type is invalid. |
| Action | Verify the segment type is correct. |
| Cause | The partition name is invalid. |
| Action | Verify the partition name is correct. |
| Cause | CLUSTER type is not supported. |
| Action | Check if the schema object is CLUSTER type. |
| Cause | There is no user with the specified name in the argument. |
| Action | Verify the specified owner name is correct |
| Cause | There is no object with the specified names in the argument. |
| Action | Verify the object and partition names are correct. |
| Cause | Input or input_string is NULL. |
| Action | Input or input_string must have a value. |
| Cause | The argument value is invalid, NULL, or out of range. |
| Action | Correct the argument value. |
| Cause | This procedure cannot be called when the SQL statement is not a %1$s. |
| Action | Use this procedure when the SQL statement is a %1$s. |
| Cause | col_name_len=%1$s (> 32). |
| Action | Use DESCRIBE_COLUMNS2 procedure. |
| Cause | The key value is invalid. |
| Action | The key must contain %1$d or more characters. |
| Cause | The initialization vector value is invalid. |
| Action | The initialization vector must contain %1$d or more characters. |
| Cause | The size of the input parameter is invalid. |
| Action | Set the length of input parameter to multiples of %1$d bytes. |
| Cause | An error occurred during encryption or decryption using the DBMS_CRYPTO package. |
| Action | Contact the system administrator. |
| Cause | An error occurred during encryption or decryption using the DBMS_CRYPTO package. |
| Action | Verify the data is valid and contact the system administrator. |
| Cause | An error occurred during encryption or decryption using the DBMS_OBFUSCATION_TOOLKIT package. |
| Action | Verify the data is valid and contact the system administrator. |
| Cause | The standard function '%1$s' is called only from the SQL statement. |
| Action | Call the function in the SQL statement. |
| Cause | A general network error occurred at the UTL_TCP package. |
| Action | Verify the connection is valid. |
| Cause | The length of a line read by the server is too long. |
| Action | Use another API for reading. |
| Cause | No more input data is available from the connection. |
| Action | Stop reading. |
| Cause | No reply arrived within timeout (seconds). |
| Action | Check the status of the TCP connection. |
| Cause | An HTTP header larger than the internal buffer was received from the HTTP server. |
| Action | Verify the HTTP server is valid. |
| Cause | A pipe of the same name already exists. |
| Action | Create a new pipe name or reuse the existing pipe. |
| Cause | Pipe creation failed due to system limit and redundant pipe creation. |
| Action | Contact the system administrator. |
| Cause | DBMS_PIPE package buffer size exceeded; no more data can be entered. |
| Action | Empty the data in the buffer by calling the DBMS_PIPE.SEND_MESSAGE function. |
| Cause | All data in the buffer read from the DBMS_PIPE.RECEIVE_MESSAG function has been read. |
| Action | None |
| Cause | The requested data type is different from the actual data type. |
| Action | Call the DBMS_PIPE.UNPACK_MESSAGE procedure by using a valid message type. |
| Cause | DBMS_PIPE internal error. |
| Action | Contact the system administrator. |
| Cause | There was an attempt to create a policy for the object of the SYS user. |
| Action | This command cannot be executed. |
| Cause | The policy name already exists. |
| Action | Check the policy name. |
| Cause | The policy does not exist. |
| Action | Check the name of the policy. |
| Cause | Cannot execute policy function. |
| Action | Check fine-grained audit policy. |
| Cause | The pipe was privately created by a different user. |
| Action | Contact the user who created the pipe. |
| Cause | If the collection bound with DBMS_SQL.BIND_ARRAY is empty, batch update cannot be performed. |
| Action | Fill the bound collection with data. |
| Cause | DBMS_SQL.COLUMN_VALUE_LONG can be used only for LONG type columns. |
| Action | Check the column type. |
| Cause | The argument is an invalid SQL name. |
| Action | Refer to a description of DBMS_ASSERT in the manual and specify a valid argument. |
| Cause | The argument is invalid for a qualified SQL name. |
| Action | Refer to a description of DBMS_ASSERT in the manual and specify a valid argument. |
| Cause | Internal system error. |
| Action | Contact the system administrator. |
| Cause | An invalid column name was specified in SORT_LIST. |
| Action | SORT_LIST may only contain ENQ_TIME and PRIORITY. |
| Cause | All queues in a queue table must be dropped before the queue table can be dropped. |
| Action | Drop all of the queues using the drop_queue() command or with the force option. |
| Cause | The queue table does not exist. |
| Action | Check if the queue table exists using the USER_QUEUE_TABLES view. |
| Cause | The schema defined in queue_name does not match the schema in queue_table. |
| Action | Specify two arguments that have the same schema name. |
| Cause | The queue already exists. |
| Action | Change the queue name. Search the USER_QUEUES view to see the current queues. |
| Cause | The enqueue/dequeue pair is invalid. |
| Action | One of the arguments must be TRUE. |
| Cause | The agent is already specified as a subscriber of the queue. |
| Action | Use a different agent name. |
| Cause | The enqueue function of the queue is disabled. |
| Action | Enable the queue using the start_queue() command. |
| Cause | Attempted to enqueue to queues that can serve multiple consumers, but a subscriber or a recipient was not defined for the queue. |
| Action | Specify a recipient or register a subscriber in the queue before attempting to enqueue. |
| Cause | The dequeue option can be specified with either a message ID or a dequeue condition/correlation ID, but not both. |
| Action | Specify at most one option. |
| Cause | A timeout occurred while dequeuing a message. |
| Action | Try dequeuing again. Correct the wait time specified in the dequeue option if insufficient. |
| Cause | The dequeue function of the queue is disabled. |
| Action | Enable the queue using the start_queue() command. |
| Cause | A consumer was specified while registering a notification for a single-consumer queue or an exception queue. |
| Action | Do not specify a consumer when registering a subscription name. |
| Cause | Failed to find the specified registration. |
| Action | Verify the specified subscription name and callback string are valid. |
| Cause | Attempted to dequeue to queues that can serve multiple consumers, but consumer_name was not defined in the dequeue option. |
| Action | Specify consumer_name in the dequeue option. |
| Cause | The directory name or path is invalid. |
| Action | Verify that the path name is correct. |
| Cause | Visibility must be set to ON_COMMIT or IMMEDIATE. |
| Action | Specify ON_COMMIT or IMMEDIATE for visibility. |
| Cause | The specified privilege to be granted or revoked is invalid. |
| Action | Specify a valid privilege. |
| Cause | The queue is not stopped. (enqueue or dequeue has been enabled.) |
| Action | Disable both enqueue and dequeue using the stop_queue() command. |
| Cause | msgid cannot be specified in dequeue_options when calling dequeue_array. |
| Action | Remove the specified msgid from dequeue_options. |
| Cause | The server env name is invalid. |
| Action | Verify that the svr env name is correct. |
| Cause | The package has not been initialized. |
| Action | Verify that the database server has started normally. |
| Cause | The size of the message is greater than the maximum size of the pipe. |
| Action | Reduce the size of the message, or increase the maximum size of the pipe. |
| Cause | A consumer name can only be defined for multi-consumer queues. |
| Action | Remove the consumer_name from the dequeue options. |
| Cause | The queue does not exist. |
| Action | Check whether the queue exists through the USER_QUEUES view. |
| Cause | STOP_QUEUE will fail if there is a transaction in progress when WAIT is set to false. |
| Action | Set WAIT to true, and then retry to execute the STOP_QUEUE command. The command will wait until all transactions are committed before stopping the queue. |
| Cause | The policy does not exist. |
| Action | Re-check the name of the schema, schema object, and policy name. |
| Cause | The policy already exists. |
| Action | Re-check the name of the schema, schema object, and policy. |
| Cause | A lock has already been obtained by another user. |
| Action | Try later. |
| Cause | A patch for previous versions may exist or a patch was applied incorrectly. |
| Action | 'EXEC UTL_RECOMP.RECOMP_SERIAL;' is required. Contact the technical support team. |
| Cause | A queue with this name exists, but it is not a multiple consumer queue. |
| Action | None |
| Cause | An incorrect HTTP package subprogram has been used. |
| Action | The program must be recreated. |
| Cause | The end of the HTTP response has been reached. |
| Action | None |
| Cause | The HTTP request cannot be executed. |
| Action | None |
| Cause | The character set is not supported. |
| Action | None |
| Cause | The amount of data to be written to a single line exceeds the maximum allowed. |
| Action | The length of a line cannot exceed the maximum. The maximum size is specified in the max_linesize parameter. |
| Cause | Policy is disabled. |
| Action | Check the status of the policy. |
| Cause | Timeout occurred while using a pipe. |
| Action | Try again. |
| Cause | ABORT_EXECUTION was called in the debugger session. |
| Action | None |
| Cause | Specified profile already exists. |
| Action | Check the profile name. |
| Cause | Specified profile does not exist. |
| Action | Check the profile name. |
| Cause | Custom translation of this SQL statement or error code is not registered. |
| Action | Check custom translation. |
| Cause | Synonyms cannot be used in column-level VPD. |
| Action | Check the argument of the procedure. |
| Cause | Specified column does not exist. |
| Action | Check the argument of the procedure. |
| Cause | Invalid parameter was used. |
| Action | Use a valid parameter. |
| Cause | Invalid method was used for the type operation. |
| Action | Refer to a valid example to apply a valid method to the operation. |
| Cause | An invalid type was used to access AnyData. |
| Action | Attempt operation using a valid type. |
| Cause | An invalid context was passed as an argument of XMLGEN.GETXML. |
| Action | Check if the context is configured correctly. |
| Cause | A negative value was assigned to a variable that does not allow a negative value. |
| Action | Assign a non-negative value to the variable. |
| Cause | An insert that violates the DOM Tree structure was executed. |
| Action | Check the node relationships. |
| Cause | A node that does not belong to the document was used. |
| Action | Include the node in the current document or create a new node. |
| Cause | A character string that is not allowed in XML was used. |
| Action | Use a character string allowed in XML. |
| Cause | An invalid DOM handle was used. |
| Action | Use a valid DOM handle. |
| Cause | A DOM processing error has occurred. |
| Action | Check the DOM processing rules. |
| Cause | Package function is currently unavailable. |
| Action | Check the package related parameters. |
| Cause | The order of the API calls or the application implementation is incorrect. |
| Action | Check whether it needs to be preceded by another operation, or how touse the operation. |
| Cause | An error response code in the 400-499 range occurred. |
| Action | Check the response code and text for error details. |
| Cause | An error response code in the 500-599 range occurred. |
| Action | Check the response code and text for error details. |
| Cause | The size of the user-entered string is more than 130 bytes. |
| Action | Enter a string that is less than 130 bytes. |
| Cause | The user-entered an invalid column name. |
| Action | Enter a valid column name. |
| Cause | Rowsettag and Rowtag are both set to NULL. |
| Action | Enter a non-NULL value for Rowsettag or Rowtag. |
| Cause | If Rowsettag or Rowtag is NULL, then the query result must be a single column or a single row. |
| Action | Either enter a non-NULL value for both Rowsettag and Rowtag, or use a query whose result is a single row or a single column. |
| Cause | A column that does not exist in the query result has been set to the rowid attribute value. |
| Action | Rowid attribute value must be selected among the columns that exist in the query result. |
| Cause | Rowid attribute value can only be set in a scalar column. |
| Action | Set one of the scalar columns to the rowid attribute value. |
| Cause | The query result is empty, and the “Raise No Rows Exception flag” is set to “true”. |
| Action | Change the “Raise No Rows Exception" flag to “false” by using DBMS_XMLQUERY.SETRAISENOROWSEXCEPTION. |
| Cause | If the “SQL to XML Name Escaping” flag is set to “false”, then the “escape” character cannot be used in the tag. |
| Action | Either enter a string without an escape character, or change the "SQL to XML Name Escaping" flag to “true” by using DBMS_XMLQUERY.SETSQLTOXMLNAMEESCAPING. |
| Cause | The bind value does not exist in the query used to create the context. |
| Action | Enter the name of the bind variable that exists in the query used to create the context. |
| Cause | The input DDL must be the create or replace statement. |
| Action | Use one of the following types: PROCEDURE, FUNCTION, PACKAGE or PACKAGE BODY |
| Cause | Wrapping the create or replace statement is failed. |
| Action | Check the system log. |
| Cause | Creating procedure or package is failed. rc=%1$d |
| Action | Check the system log. |
| Cause | Trigger which you specified is not found. |
| Action | Please check the trigger name and its owner name. |
| Cause | Hierarchical workspace is not supported yet. |
| Action | Please use workspace in single level |
| Cause | The node type is invalid. |
| Action | Use a valid node type. |
| Cause | An error occurred while calling an external API. |
| Action | Check the program that calls the DOM API. |
| Cause | Following feature not supported. |
| Action | Check requirements for DBMS_CMGT |
| Cause | An error occurred during streaming. |
| Action | None |
| Cause | Invalid data. |
| Action | None |
| Cause | The compression results exceed the maximum RAW size. |
| Action | None |
| Cause | An error occurred during compression. |
| Action | None |
| Cause | An error occurred during decompression. |
| Action | None |
| Cause | Insufficient memory. |
| Action | None |
| Cause | Network with same name already exists. |
| Action | Try different network name. |
| Cause | Node table with same name already exist. |
| Action | Try different node table name. |
| Cause | Link table with same name already exist. |
| Action | Try different link table name. |
| Cause | Path table with same name already exist. |
| Action | Try different path table name. |
| Cause | Pathlink table with same name already exist. |
| Action | Try different pathlink table name. |
| Cause | Network does not exist error. |
| Action | Check network name. |
| Cause | An error occurred while attempting to read the data whose size is greater than that of bfile. |
| Action | Enter a valid size of data. |
| Cause | The user session ID no longer exists, probably because the session was logged out. |
| Action | Use a valid session ID. |