| Cause | This function has yet to be implemented. |
| Action | This function will be supported in the next version. |
| Cause | Parsing failed. |
| Action | Check the syntax. |
| Cause | Failed during pragma check; two parameters that should match, did not. |
| Action | Modify the parameters to match. |
| Cause | Failed during the parse tree check; the parse trees of two parameters do not match. |
| Action | Check the parameters used in the statement and modify them. |
| Cause | Unable to open the psm_commands file for PSM compilation. |
| Action | Verify that the psm_commands file exists under the config directory, or contact the technical support team. |
| Cause | The comment is duplicated. |
| Action | Check the comment. |
| Cause | The comment is not terminated. |
| Action | Check the comment and terminate it properly. |
| Cause | The string is not terminated. |
| Action | Check the string and terminate it properly. |
| Cause | The ID length is 0. |
| Action | Check the ID and ensure the length is greater than 0. |
| Cause | The ID string is declared over several lines. |
| Action | Declare the ID on one line. |
| Cause | Unknown character. |
| Action | Verify that a character is not out of place. |
| Cause | No default expression has been defined. |
| Action | Define a default expression. |
| Cause | No type constraint has been defined. |
| Action | Define a type constraint. |
| Cause | No expression has been defined. |
| Action | Define an expression. |
| Cause | No subprogram body has been defined. |
| Action | Define the subprogram body. |
| Cause | No package body has been defined. |
| Action | Define the package body. |
| Cause | An SQL statement that is not a SELECT statement was used. |
| Action | Modify the SQL statement to use a SELECT statement. |
| Cause | INTO clause is missing. |
| Action | Specify an INTO clause. |
| Cause | RETURN clause is missing. |
| Action | Specify a RETURN clause. |
| Cause | Character unit (CHAR or BYTE) is not allowed. |
| Action | Change the data type. |
| Cause | Schema name is not allowed. |
| Action | Do not specify a schema name. |
| Cause | AUTHID clause is not allowed. |
| Action | Do not specify an AUTHID. |
| Cause | Default expression is not allowed. |
| Action | Delete the default expression. |
| Cause | A HANDLER clause cannot be used after OTHERS. |
| Action | Move the clause to a different location or delete it. |
| Cause | Expression is not allowed. |
| Action | Do not specify an expression. |
| Cause | Specification is not allowed. |
| Action | Move the specification to a different location or delete it. |
| Cause | RETURN clause is not allowed. |
| Action | Delete the RETURN clause. |
| Cause | INTO clause is not allowed. |
| Action | Delete the INTO clause. |
| Cause | OUT parameter is not allowed. |
| Action | Delete the parameter or use an IN parameter. |
| Cause | REVERSE character is not allowed. |
| Action | Delete the REVERSE character. |
| Cause | Dynamic SQL statements are not allowed. |
| Action | Modify or delete the SQL statement. |
| Cause | Cannot open the cursor of IN parameter. |
| Action | Delete OPEN, or specify an OUT or IN/OUT parameter cursor. |
| Cause | The bind parameter was used in the DDL outside the trigger. |
| Action | Delete the bind parameter. |
| Cause | The specified PRAGMA clause is not allowed in this area. |
| Action | Modify or delete the PRAGMA clause. |
| Cause | The number is out of range. |
| Action | Check the value. |
| Cause | A type constraint is out of range. |
| Action | Verify that the type constraints are valid. |
| Cause | The labels do not match. |
| Action | Ensure that the labels match. |
| Cause | The data types do not match. |
| Action | Verify the data types are compatible. |
| Cause | The declaration and the called parameter do not match. |
| Action | Verify that the parameter is correct. |
| Cause | The declaration and the definition do not match. |
| Action | Verify that the declaration is correct. |
| Cause | There are many subprograms that match the specified argument(s). |
| Action | Modify the argument(s). |
| Cause | No subprogram matches the specified argument(s). |
| Action | Modify the argument(s). |
| Cause | The number of parameters in the INTO clause does not match the query. |
| Action | Ensure the number of parameters in the INTO clause matches the query. |
| Cause | Undefined identifier. |
| Action | Define the identifier. |
| Cause | Unknown attribute name. |
| Action | Verify the attribute name is correct. |
| Cause | The identifier is out of scope. |
| Action | Modify the identifier scope or delete it. |
| Cause | The dot operator (.) cannot be used for this ID; the ID type is not a record, block label, procedure, or username. |
| Action | Ensure the dot operator is used with the correct ID types. |
| Cause | Cannot use a parenthesis operator for this ID; the ID is not a by table. |
| Action | Ensure the parenthesis operator is used with the correct ID types. |
| Cause | The value specified is not a constant. |
| Action | Use a constant value. |
| Cause | A value was expected but not found. |
| Action | Specify a value. |
| Cause | A cursor was expected but not found. |
| Action | Specify a cursor. |
| Cause | A label was expected but not found. |
| Action | Specify a label. |
| Cause | A type was expected but not found. |
| Action | Specify a type. |
| Cause | An exception was expected but not found. |
| Action | Specify an exception. |
| Cause | Cannot use an assignment expression for the corresponding expression. |
| Action | Use another expression or modify the current expression. |
| Cause | A static cursor was expected, but a reference cursor was found. |
| Action | Specify a static cursor. |
| Cause | A reference cursor was expected, but a static cursor was found. |
| Action | Specify a reference cursor. |
| Cause | A procedure was expected but not found. |
| Action | Specify a procedure. |
| Cause | An identifier was expected but not found. |
| Action | Specify an identifier. |
| Cause | A declaration was expected but not found. |
| Action | Specify a declaration. |
| Cause | A loop label was expected but not found. |
| Action | Specify a loop label. |
| Cause | A record was expected but not found. |
| Action | Specify a record. |
| Cause | An identifier with this name already exists. |
| Action | Modify the identifier name. |
| Cause | A parameter with this name already exists. |
| Action | Modify the parameter name. |
| Cause | A handler clause with this name already exists. |
| Action | Modify the clause name. |
| Cause | Positional arguments cannot come after a named argument. |
| Action | Delete or move the positional argument. |
| Cause | An invalid type constraint was detected. |
| Action | Modify the type constraint. |
| Cause | Invalid attribute. |
| Action | Modify the attribute. |
| Cause | An invalid error code was used for pragma exception_init. |
| Action | Modify the error code. |
| Cause | Invalid pragma. |
| Action | Modify the pragma. |
| Cause | Only BINARY_INTEGER, PLS_INTEGER, and character types are allowed for the table index type. |
| Action | Modify the table index type. |
| Cause | The location of the declaration is wrong, The location must precede the body. |
| Action | Declaration must be specified before the definition. |
| Cause | Overloading is invalid here. |
| Action | Modify the procedure. |
| Cause | Invalid RETURN clause. |
| Action | Correct the RETURN clause. |
| Cause | Invalid GOTO clause. |
| Action | Correct the GOTO clause. |
| Cause | Invalid EXIT clause in loop. |
| Action | Correct the EXIT clause. |
| Cause | The return value of a CASE expression cannot be NULL. |
| Action | Modify the CASE statement. |
| Cause | An invalid attempt was made to call an invalid function or access a collection variable. |
| Action | Modify the statement to use a valid function call or access an array. |
| Cause | Invalid parameter. |
| Action | Modify the parameter. |
| Cause | Invalid SQL statement. |
| Action | Correct the SQL statement. |
| Cause | Invalid use of collection type method. |
| Action | Check the return type and parameters of the method. |
| Cause | Invalid return type. |
| Action | Specify a different return type |
| Cause | Invalid use of index of the collection variable. |
| Action | Modify the index. |
| Cause | Cannot use LONG or LONG RAW for a parameter type. |
| Action | Modify the parameter type or use another subprogram. |
| Cause | The program terminated abnormally. |
| Action | Contact the system administrator. |
| Cause | A user-defined error. |
| Action | Check the user-defined error statement. |
| Cause | This function has yet to be implemented. |
| Action | This function will be supported in the next version. |
| Cause | A critical error occurred. |
| Action | Contact the system administrator. |
| Cause | Failed in type conversion. |
| Action | Check the type. |
| Cause | An uninitialized variable was accessed. |
| Action | Initialize the variable. |
| Cause | A binary for executing the function does not exist. |
| Action | Recreate the function. |
| Cause | The size of the parameter exceeded the maximum of 32K. |
| Action | Decrease the parameter size or use a different parameter. |
| Cause | The NULL value cannot be used for this parameter. |
| Action | Specify a value other than NULL. |
| Cause | The program length exceeded the maximum length allowed. |
| Action | Shorten the program or create it as a package. |
| Cause | The called trigger or subprogram refers to the table. |
| Action | Modify the trigger or subprogram to eliminate table references. |
| Cause | Procedures called within the query cannot contain DML statements. |
| Action | Remove the DML from the procedure or use a different procedure. |
| Cause | Procedures called from a DML statement or query cannot contain DDL or TCS statements. |
| Action | Remove DDL or TCS statements from the DML statement (or query) or use another subprogram. |
| Cause | An attempt was made to assign a value to an uninitialized variable. |
| Action | Initialize the variable first. |
| Cause | The ELSE statement does not exist, or the matching condition is missing. |
| Action | Specify an ELSE statement or check the condition clause. |
| Cause | Unable to call functions (other than EXISTS) or assign values to uninitialized tables or arrays. |
| Action | Initialize the table or array first. |
| Cause | Unable to open currently opened cursors. |
| Action | The cursor is already open. |
| Cause | Invalid cursor operation. |
| Action | Check the status of the cursor. |
| Cause | Invalid user ID or password. |
| Action | Verify that the user ID and password are correct, and then try relogging. |
| Cause | No result rows were found. |
| Action | Check the SQL statement or the access statement related to the collection. |
| Cause | There is no active connection to the server. |
| Action | Log on to the server and try again. |
| Cause | PSM internal error. |
| Action | Contact the system administrator. |
| Cause | The host cursor variable type and the PSM internal cursor variable type do not match. |
| Action | Verify that the cursor type in use is correct. |
| Cause | Unable to call the MEMBER function of an uninitialized object. |
| Action | Initialize the object first. |
| Cause | Not enough memory or invalid memory data. |
| Action | Contact the system administrator. |
| Cause | An index is greater than the maximum length of the array or beyond the bounds of the table. |
| Action | Specify a smaller index. |
| Cause | An index is less than zero or greater than the maximum length of the array. |
| Action | Modify the index to smaller than the declared size in the collection. |
| Cause | The string is not a valid ROWID. |
| Action | Modify the string to be a valid ROWID. |
| Cause | Assigning server resources timed out. |
| Action | Contact the system administrator. |
| Cause | There is more than one result row for a SELECT INTO query. |
| Action | Correct the SELECT statement. |
| Cause | The value is invalid. |
| Action | Verify that the value is a valid type and length. |
| Cause | The user-defined error was not processed in an EXCEPTION clause but sent to the user. |
| Action | Verify that the actual cause of the error matches the cause listed above. If necessary, add an EXCEPTION clause. |
| Cause | Too many shared libraries were opened at one time. |
| Action | Rewrite the program to use fewer shared libraries. |
| Cause | The bind variable could not be found. |
| Action | Verify the specified bind variable exists. |
| Cause | The PSM and server build versions do not match. |
| Action | Rebuild the whole PSM with the statement EXEC UTL_RECOMP.RECOMP_SERIAL; |
| Cause | The large parse tree size caused a compilation failure. |
| Action | Modify the PSM. |
| Cause | The integer value was too large or too small. |
| Action | Check the operation. |
| Cause | There is no exception to reraise. |
| Action | Process all exceptions, and verify 'reraise' was performed. |
| Cause | The specified index is out of range. |
| Action | Check the limit of the length of the collection variable. |
| Cause | Primitive data type variable is not allowed. |
| Action | Use a collection variable. |
| Cause | In a FORALL clause, DML without bind parameters is not allowed. |
| Action | Use a bind parameter. |
| Cause | In a FORALL clause, queries are not allowed. |
| Action | In order to use queries, use FOR/LOOP/CSR_FOR_LOOP statements. |
| Cause | Invalid use of data type. |
| Action | Use a collection variable. |
| Cause | Invalid element data type. |
| Action | Use a PLS_INTEGER or BINARY_INTEGER data type. |
| Cause | An error occurred while executing a FORALL clause. |
| Action | Contact the technical support team. |
| Cause | Invalid index type was used in the FORALL clause. |
| Action | Use a PLS_INTEGER or BINARY_INTEGER data type. |
| Cause | In an INTO clause, a composite data type and a scalar data type cannot be used together. |
| Action | Use either a scalar data type or a composite data type. |
| Cause | Invalid ROWID. |
| Action | Verify that a valid ROWID value was transmitted. |
| Cause | A field variable of a record is not allowed in a FORALL clause. |
| Action | Specify a record variable or a different variable. |
| Cause | No element was found at the specified index number. |
| Action | Verify that the index is valid. |
| Cause | The library name is not defined. |
| Action | Verify that the library name is correct. |
| Cause | The protocol is not defined. |
| Action | Contact the technical support team. |
| Cause | An error occurred during communication with External Procedure Agent. |
| Action | Contact the technical support team. |
| Cause | An error occurred during communication with External Procedure Agent. |
| Action | Contact the technical support team. |
| Cause | An error occurred during communication with External Procedure Agent. |
| Action | Contact the technical support team. |
| Cause | Cannot to start the EPA (External Procedure Agent) process. |
| Action | Contact the technical support team. |
| Cause | Failed to execute the external procedure. |
| Action | Refer to the error code of EPA (External Procedure Agent). |
| Cause | No RETURN clause was specified. |
| Action | Specify a RETURN clause. |
| Cause | The statement uses too many temporary variables in interpret mode. |
| Action | Divide or modify the statement to decrease the number of temporary variables. |
| Cause | The statement uses too many expressions in interpret mode. |
| Action | Divide or modify the expressions. |
| Cause | Failed to compile the given PSM. |
| Action | Check the error, and modify the PSM. |
| Cause | The length of identifier exceeds the maximum (4,000 bytes). |
| Action | Shorten the identifier. |
| Cause | The object condition is invalid. |
| Action | Check the object condition, and recreate it if necessary. |
| Cause | The number of elements exceeds the maximum allowed (16,777,216). |
| Action | Lessen the number of elements. |
| Cause | 'Not enough memory' error occurred during PSM execution. |
| Action | Modify the program to decrease memory use. |
| Cause | The number of specified bind parameters is invalid. |
| Action | Verify that the PSM and bind parameters match. |
| Cause | Failed to compile the Java sources in the given PSM. |
| Action | Check the error, and modify the Java source. |
| Cause | No input mode bulk parameter exists among the parameters passed to a FORALL clause. |
| Action | Verify that the collection is bound correctly for the FORALL clause. |
| Cause | A backtrace occurred because the exception was not handled. |
| Action | Investigate the cause from the PSM module where the exception occurred, and add appropriate exception handling code. |
| Cause | Invalid byte code. This error may occur if the byte code was damaged, or the version is too old. |
| Action | Recreate the PSM object. The PSM cannot be executed due to the invalid byte code. |
| Cause | The PSM version is not compatible with the current server version. |
| Action | Create a new PSM object. |
| Cause | MAXLEN cannot be used for IN parameters. |
| Action | MAXLEN is valid for OUT, IN/OUT, and RETURN parameters. |
| Cause | The pipelined function contains an invalid return type. |
| Action | Ensure the collection type returned by the pipe function is valid. |
| Cause | An attempt was made to return an expression from a pipelined function. |
| Action | A pipelined function cannot return an expression. Modify the function. |
| Cause | An attempt was made to use a pipe row function outside a pipelined function. |
| Action | Pipe row function can be used only in a pipelined function. |
| Cause | Invalid error code. |
| Action | Check the error message. |
| Cause | No object body has been defined. |
| Action | Define the object body. |
| Cause | Unable to call function/procedures or assign values to uninitialized objects. |
| Action | Initialize the object by using the constructor function first. |
| Cause | Constructor of object does not exist. |
| Action | Add a constructor of the object. |
| Cause | Constructor name does not match with the type name. |
| Action | Modify the constructor name. |
| Cause | Constructor must return SELF AS RESULT. |
| Action | Set SELF AS RETURN as a return type of constructor. |
| Cause | Object type member subprograms need to be declared in the object specification. |
| Action | Define the subprogram spec in the object type specification. |
| Cause | Object type cannot be self-referenced. |
| Action | Do not declare the object type recursively. |
| Cause | Exceeds the maximum record field count limit. |
| Action | Declare less than 32568 fields per record. |
| Cause | The PSM recursive level is too deep. |
| Action | Modify the '_PSM_RECURSIVE_LVL' parameter. |
| Cause | An invalid attempt was made to access a non-collection variable using (). |
| Action | Modify the statement to access a collection-type array. |
| Cause | An invalid attempt was made to call a non-void collection method using (). |
| Action | Remove () when calling a non-void collection method. |
| Cause | An unexpected error occurred while wrapping PSM source code. |
| Action | Contact the system administrator. |
| Cause | An unexpected error occurred while unwrapping PSM source code. |
| Action | Contact the system administrator. |
| Cause | The number of parameters in the external procedure is too large. |
| Action | Reduce the number of parameters in the external procedure and try again. |
| Cause | An EXTERNAL PROCEDURE recursively issuing a CALLBACK function is not supported. |
| Action | Contact the technical support team. |
| Cause | Java source compilation has failed. |
| Action | Java source compilation has failed. |
| Cause | Failure occurred in the batch update operation where PSM's FORALL statement or DBMS_SQL package was instantiated. |
| Action | Verify the SQL statement is suitable for the batch update. If suitable, contact the technical support team. |
| Cause | PP has been invalidated during the batch update operation where PSM's FORALL statement or DBMS_SQL package was used. |
| Action | Contact the technical support team. |
| Cause | User does not have an appropriate permission to create EXTERNAL PROCEDURE in DIRECT_EXECUTE mode. |
| Action | SYSDBA permission is required. |
| Cause | Only an automatic value is allowed to access the collection using a duplicate index in the FORALL statement. |
| Action | Remove the arithmetical operation used for accessing the collection. |
| Cause | There is an expression that cannot be handled while optimizing PSM Constant Folding. |
| Action | Disable the option when optimizing PSM Constant Folding. |
| Cause | To execute the external procedure, the %1$s package is required. |
| Action | Contact the system administrator. |
| Cause | Only the cursor of the query declared as FOR UPDATE can perform a positioned update. |
| Action | Insert a FOR UPDATE section to the query specified in the cursor. |
| Cause | An operation that is not permitted within EXTERNAL PROCEDURE was executed. |
| Action | Modify the EXTERNAL PROCEUDRE. |
| Cause | Refer to the manual. |
| Action | RESULT_CACHE OPTION cannot be used. |
| Cause | A Java source name was used as a PSM ID. |
| Action | Modify the PSM source. |
| Cause | PSM compiler internal error. |
| Action | Contact the technical support team. |
| Cause | MAP methods must have a scalar return type. |
| Action | Modify the signature of the MAP method. |
| Cause | MAP methods can only use the SELF parameter. |
| Action | Modify the signature of the MAP method. |
| Cause | ORDER methods must have an integer return type. |
| Action | Modify the signature of the ORDER method. |
| Cause | ORDER methods can only use the SELF parameter or objects that have the same type. |
| Action | Modify the signature of the ORDER method. |
| Cause | A function can only contain a single MAP or ORDER function. |
| Action | Modify the declaration of the object type. |
| Cause | The current specification is invalid in Object. |
| Action | Modify the signature of the object type. |
| Cause | The object specification does not contain a declaration for the method '%1$s', which is defined in the object body. |
| Action | Cannot compile. The object specification or object body must be modified. |
| Cause | The method '%1$s', declared in the object specification, must be defined. |
| Action | Cannot compile. The object specification or object body must be modified |
| Cause | Duplicate method names are defined in the object specification. |
| Action | Cannot compile. The object specification must be modified. |
| Cause | MAP and ORDER methods are not defined. |
| Action | The value of this object type can be compared using MAP and ORDER methods. |
| Cause | The CONTINUE statement was not used in a loop. |
| Action | Execute the CONTINUE statement in loop. |
| Cause | The _USE_SUCCESS_WITH_INFO_IN_BATCH iparam must be enabled in batch psm. |
| Action | Set the _USE_SUCCESS_WITH_INFO_IN_BATCH iparam to YES. |
| Cause | The number of columns returned by the bulk cursor does not match the return type. |
| Action | The operation cannot be performed on the cursor. |
| Cause | internal |
| Action | internal |
| Cause | internal |
| Action | internal |
| Cause | The return type is a composite type, the parameter is 'OUT' or 'IN OUT', or the parameter type is a composite type or a lob type. |
| Action | Redefine the function. |
| Cause | A composite type that cannot be used was bound. |
| Action | Check the bind parameter. |
| Cause | There is no available session to execute the pipelined function. |
| Action | Re-execute the function after securing an available session. |
| Cause | Aggregate and table functions cannot be used as a general function. |
| Action | Modify the PSM program. |
| Cause | The number of table columns and values do not match the number of data fields. |
| Action | Cannot be supported. The UPDATE/INSERT statement must be modified. |
| Cause | Accessed an object instance that has not been created. |
| Action | Check whether the instance has been created. |
| Cause | Used an invalid continue clause in the loop. |
| Action | Modify the continue clause. |
| Cause | This function is no longer provided. |
| Action | Contact the technical support team for more detailed information |