PLS-00164: cursor subqueries are not supported in this release
Cause: This feature is not yet implemented.
Action: No action required.
Category Archives: PLS Database Error Messages
PLS-00162: Pragma string expects 4th argument to be a positive integer literal
PLS-00162: Pragma string expects 4th argument to be a positive integer literal
Cause: The fourth argument (actual parameter) passed to the named pragma (compiler directive) was not a numeric literal, as required. The parameter might be misspelled, or the pragma syntax might be faulty (for example, a comma might be missing between two parameters).
Action: Check the spelling of the fourth parameter, and make sure the proper syntax was used.
PLS-00161: Pragma string expects 3rd argument to be an identifier or a string literal
PLS-00161: Pragma string expects 3rd argument to be an identifier or a string literal
Cause: The third argument (actual parameter) passed to the named pragma (compiler directive) was not an identifier or a string literal when there is a fourth argument to the pragma. The parameter might be misspelled, or the pragma syntax might be faulty (for example, a comma might be missing between two parameters).
Action: Check the spelling of the third parameter, and make sure the proper syntax was used.
PLS-00160: AUTHID must specify CURRENT_USER or DEFINER
PLS-00160: AUTHID must specify CURRENT_USER or DEFINER
Cause: The only two allowed options for AUTHID are CURRENT_USER and DEFINER.
Action: Fix the AUTHID clause to specify CURRENT_USER or DEFINER.
PLS-00157: AUTHID only allowed on schema-level programs
PLS-00157: AUTHID only allowed on schema-level programs
Cause: An AUTHID clause was specified for a subprogram inside a package or type. These clauses are only supported for top-level stored procedures, packages, and types.
Action: Remove the clause.
PLS-00156: Null constraints not supported for object attributes
PLS-00156: Null constraints not supported for object attributes
Cause: A null constraint was specified for an attribute in an object. This is not supported.
Action: Remove the constraint.
PLS-00155: Only a function may be a MAP, ORDER or CONSTRUCTOR method
PLS-00155: Only a function may be a MAP, ORDER or CONSTRUCTOR method
Cause: A procedure was declared as a MAP, ORDER, or CONSTRUCTOR method. Only functions can be MAP, ORDER, or CONSTRUCTOR methods.
Action: Change the procedure to a function.
PLS-00154: An object type may have only 1 MAP or 1 ORDER method
PLS-00154: An object type may have only 1 MAP or 1 ORDER method
Cause: More than one map or order function was declared. An object type can have only one map function or one order function, but not both.
Action: Delete all but one of the MAP or ORDER functions on the type.
PLS-00153: A string type may only be used as an object type attribute
PLS-00153: A string type may only be used as an object type attribute
Cause: A POINTER or [SIGNED/UNSIGNED] BINARY INTEGER can only be used as attributes of object types. These types can only be referenced in CREATE TYPE statements, and are non-queryable data types. One of these external PL/SQL types outside of an object type.
Action: Use a different type and retry the operation.
PLS-00152: POINTER type may only reference an object type
PLS-00152: POINTER type may only reference an object type
Cause: A POINTER type which does not belong to PL/SQL can only refer to an object type. This type can only be referenced in CREATE TYPE statements, and is a non-queryable data type.
Action: Use a different type and retry the operation.