PLS PLSQL ERROR CODE ORACLE.

 

PLS-00660	PLS-00660: SELF parameter of constructor method must be IN OUT
Cause	The mode of the SELF parameter of the constructor was not IN OUT.
Action	Change the mode of the SELF parameter to be IN OUT.

 

PLS-00661	PLS-00661: RETURN statement in a CONSTRUCTOR cannot include an expression
Cause	An attempt was made to include an expression in the RETURN statement of a CONSTRUCTOR body.
Action	Remove the expression from the RETURN statement.

 

PLS-00662	PLS-00662: Non-external object types containing external mapped attributes are not allowed
Cause	An attempt was made to create a non-external object, whoose attributes are mapped externally.
Action	Create the object as an external object.

 

PLS-00663	PLS-00663: the NEW keyword is not allowed in this context
Cause	The NEW keyword is not followed by an call to a constructor method.
Action	Remove the NEW keyword, or make sure the expression following it is a constructor call.

 

PLS-00664	PLS-00664: Both ORDER BY and CLUSTER BY can not be specified for the same table function
Cause	An attempt was made to specify both ORDER BY and CLUSTER BY for the same table function.
Action	specify either ORDER BY or CLUSTER BY for a table function, but not both.

 

PLS-00665	PLS-00665: ORDER BY and CLUSTER BY clauses require a PARTITION BY clause
Cause	An attempt was made to specify an ORDER BY or CLUSTER BY clause without also specifying a PARTITION BY clause.
Action	Add a PARTITION BY clause, or remove the ORDER BY or CLUSTER BY clause.

 

PLS-00666	PLS-00666: Only index by binary_integer/pls_integer associative arrays allowed here
Cause	An attempt was made to specify index collection that was not indexed by binary_integer or pls_integer.
Action	Change the index collection variable type to associative array that is indexed by binary_integer or pls_integer.

 

PLS-00667	PLS-00667: Element type of associative array should be pls_integer or binary_integer
Cause	An attempt was made to specify index collection whos element type was not one of pls_integer or binary_integer.
Action	Change the index collection variable type to associative array whose element type is pls_integer or binary_integer.

 

PLS-00668	PLS-00668: Type of expression should be a collection type
Cause	An attempt was made to specify expression after INDICES OF or VALUES OF clause whose type is not a collection type.
Action	Change the index collection expression type to a valid collection type.

 

PLS-00669	PLS-00669: Type of expression should be a valid collection variable
Cause	An attempt was made to specify expression after INDICES OF or VALUES OF clause that is not a collection variable.
Action	Change the index collection expression type to a valid collection variable.

 

PLS-00670	PLS-00670: sort columns must be simple column names
Cause	An attempt was made to specify an expression as a sort column in a PARTITION BY, CLUSTER BY or ORDER BY clause. Only simple column names are permitted.
Action	Specify a simple column name.

 

PLS-00700	PLS-00700: PRAGMA EXCEPTION_INIT of string must follow declaration of its exception in the same declarative part
Cause	An EXCEPTION_INIT pragma was not declared in the same block as its exception. They must be declared in the proper order in the same block, with the pragma declaration following the exception declaration.
Action	Place the EXCEPTION_INIT pragma directly after the exception declaration referenced by the pragma.

 

PLS-00701	PLS-00701: illegal ORACLE error number string for PRAGMA EXCEPTION_INIT
Cause	The error number passed to an EXCEPTION_INIT pragma was out of range. The error number must be in the range -9999 .. -1 (excluding -100) for Oracle errors or in the range -20000 .. -20999 for user-defined errors.
Action	Use a valid error number.

 

PLS-00702	PLS-00702: second argument to PRAGMA EXCEPTION_INIT must be a numeric literal
Cause	The second argument passed to an EXCEPTION_INIT pragma was something other than a numeric literal (a variable, for example). The second argument must be a numeric literal in the range -9999 .. -1 (excluding -100) for Oracle errors or in the range -20000 .. -20999 for user-defined errors.
Action	Replace the second argument with a valid error number.

 

PLS-00703	PLS-00703: multiple instances of named argument in list
Cause	Two or more actual parameters in a subprogram call refer to the same formal parameter.
Action	Remove the duplicate actual parameter.

 

PLS-00704	PLS-00704: "string" must be declared as an exception
Cause	The exception_name parameter passed to an EXCEPTION_INIT pragma is misspelled or does not refer to a legally declared exception. Or, the pragma is misplaced; it must appear in the same declarative section, somewhere after the exception declaration.
Action	Check the spelling of the exception_name parameter. Then, check the exception declaration, making sure the exception name and the keyword EXCEPTION are spelled correctly. Also make sure the pragma appears in the same declarative section somewhere after the exception declaration.

 

PLS-00705	PLS-00705: exception "string" used in expression requiring return type
Cause	An exception was referred to in an expression. Exceptions have names but not values and therefore cannot contribute values to an expression. For example, the following RETURN statement is illegal: FUNCTION credit_limit (cust_no INTEGER) RETURN NUMBER IS limit NUMBER; over_limit EXCEPTION; ... BEGIN ... RETURN over_limit; -- illegal END;
Action	Check the spelling of the identifiers in the expression, then rewrite the expression so that it does not refer to an exception.

 

PLS-00706	PLS-00706: Exception string cannot be used as prefix of a selected component
Cause	An exception name was mistakenly used to qualify a reference to a component. For example, when dot notation was used to specify fields within a record, an exception name might have been coded instead of the record name.
Action	Rewrite the component reference using a valid prefix (for example, the name of a package, record, or schema).

 

PLS-00707	PLS-00707: unsupported construct or internal error [string]
Cause	At run time, this is an internal error. At compile time, it indicates one of the following problems: -- A call was made to a remote subprogram that has a parameter type or default expression not supported at the calling site. -- An incomplete upgrade or downgrade was done to a database that has stored procedures. Perhaps incorrect versions of system packages such as STANDARD.SQL were installed. -- A compiler bug was encountered. In such cases, legal PL/SQL syntax will fail to compile.
Action	Either report the internal error to your Customer Support representative or, depending on the problem, take one of the following actions: -- Revise the logic of the application to use parameter types and default expressions that are supported at both the local and remote sites. -- Complete the upgrade or downgrade properly, making sure to install correct versions of all system packages. -- Report the legal-syntax error to your Customer Support representative. If there are line and column numbers displayed with the error message, they might help you find a workaround. For example, try recoding the offending line to avoid the bug.

 

PLS-00708	PLS-00708: Pragma string must be declared in a package specification
Cause	The named pragma was not declared in a package specification, as required. For example, the pragma RESTRICT_REFERENCES must be declared in a package specification.
Action	Remove or relocate the misplaced pragma.

 

PLS-00709	PLS-00709: pragma string must be declared in package specification and body
Cause	The named pragma was declared in a package specification but not in the corresponding package body or vice-versa, as well as the package body.
Action	Add the pragma to that part of the package declaration that does not have the pragma.

 

PLS-00710	PLS-00710: PRAGMA string cannot be specified here
Cause	The PRAGMA was specified in an inappropriate context.
Action	Remove or relocate the misplaced pragma. Check the documentation to determine the correct context for this pragma.

 

PLS-00711	PLS-00711: PRAGMA AUTONOMOUS_TRANSACTION cannot be declared twice
Cause	The PRAGMA was declared twice in the same block.
Action	remove the duplicate declaration of the PRAGMA

 

PLS-00712	PLS-00712: illegal option for subprogram string
Cause	Only top level subprograms or subprogram declarations in PACKAGE or TYPE specifications are allowed to have the options DETERMINISTIC or PARALLEL_ENABLE. For example, this error would be raised if the options are used in PACKAGE or TYPE body.
Action	remove the option.

 

PLS-00713	PLS-00713: attempting to instantiate a type that is NOT INSTANTIABLE
Cause	An attempt was made to instantiate a type that is defined as NOT INSTANTIABLE.
Action	Avoid instantiating variables of this NOT INSTANTIABLE type, instead derive an INSTANTIABLE subtype from it and instantiate variables of the subtype.

 

PLS-00714	PLS-00714: supertypes"s AUTHID is DEFINER but supertype and subtype are not in same schema
Cause	The supertype"s AUTHID is DEFINER, but the supertype and subtype are defined in different schemas. SQL statements executed in dynamically dispatched methods can potentially pick up different values from database tables in the two schemas.
Action	Create the subtype in the same schema as the supertype.

 

PLS-00715	PLS-00715: attribute or method by name "string" does not exist
Cause	An attempt was made to drop a nonexistant method or attribute from the type being altered.
Action	Check the spelling of the attribute or method name. Make sure it is locally defined in the type and not inherited.

 

PLS-00716	PLS-00716: Attribute/method "string" can occur only once in an ALTER TYPE statement
Cause	User attempted more than one of ADD, DROP or MODIFY on an attribute in single ALTER TYPE statement. User attempted more than one of ADD or DROP on a method in single ALTER TYPE statement.
Action	Do only one ADD, DROP or MODIFY for an attribute in single ALTER TYPE statement. Do only one ADD or DROP for a method in single ALTER TYPE statement.

 

PLS-00717	PLS-00717: method "string" does not have matching signature among existing methods
Cause	The method to be dropped matches the name of some existing method but does not match it in signature.
Action	Make sure that a matching method signature is provided for dropping a method.

 

PLS-00718	PLS-00718: type of attribute "string" does not allow modifications to the attribute
Cause	The type of the attribute to modify is not one of VARCHAR2, NUMBER, or RAW.
Action	Only VARCHAR2, NUMBER and RAW type attributes are allowed to be modified.

 

PLS-00719	PLS-00719: only widening of attribute "string" constraints is allowed
Cause	Modification to the attribute did not widen its constraints or attempted to change the type of the attribute. For NUMBER type attributes, scale and precision can be changed to allow increase in number of digits after and before the decimal point. For VARCHAR2 and RAW type attributes the size can be increased. Other type attributes are not allowed to be modified. Change of type of attribute is also not allowed.
Action	Change the constraint specification so as to widen the existing constraints.To narrow the constraints or to change the type of the attribute, you must drop the attribute and add it with new constraints or new type. In that case you must also take appropriate steps to preserve your existing data based on the type (if you want to preserve it).Typically this will involve backing up the data and restoring it after the ALTER TYPE.

 

PLS-00720	PLS-00720: type "string" has evolved
Cause	The type has evolved. The version of the type used by the compiled code is not the same as the latest version of the type.
Action	Recompile the code to use the latest version of the type.

 

PLS-00721	PLS-00721: "string" formed a non-REF mutually-dependent cycle with "string"
Cause	This compilation was aborted because the library unit that was compiled would have formed a non-REF mutually-dependent cycle with some other library units. This happens when an attempt is made to compile types that have attributes of other types that may participate in a cycle with this type. Example: create type t1; create type t2 (a t1); create type t1 (a t2);
Action	Break the cycle (possibly by adding a REF or by using another type).

 

PLS-00722	PLS-00722: supertypes"s AUTHID is different than subtype"s AUTHID
Cause	The subtype"s"s AUTHID must be same as the supertype"s AUTHID.
Action	Create the subtype with AUTHID of its supertype or do not specify AUTHID for subtype.

 

PLS-00725	PLS-00725: type "string" must be a supertype or subtype of the TREAT expression
Cause	In TREAT('expr' AS 'type'), type must be a supertype or subtype of 'expr'.
Action	none

 

PLS-00726	PLS-00726: MODIFY ELEMENT is supported only on schema-level varray and nested tables
Cause	An attempt was made to modify the limit of a type that was not a schema-level varray and nested table type.
Action	This is not a legal ALTER TYPE command for this type.

 

PLS-00727	PLS-00727: MODIFY LIMIT is supported only on schema-level varray types
Cause	An attempt was made to modify the limit of a type that was not a schema-level varray type.
Action	This is not a legal ALTER TYPE command for this type.

 

PLS-00728	PLS-00728: the limit of a VARRAY can only be increased and to a maximum 2147483647
Cause	An attempt was made to decrease the limit or raise it past 2147483647.
Action	This is not a legal limit for this type, change it.

 

PLS-00729	PLS-00729: only widening of the collection element type is allowed
Cause	Modification to the collection element type did not widen its constraints or attempted to change the type of the element. For NUMBER types, scale and precision can be changed to allow increase in number of digits after and before the decimal point. For VARCHAR2 and RAW type attributes the size can be increased.
Action	Change the constraint specification so as to widen the existing constraints.

 

PLS-00730	PLS-00730: collection element type does not allow modifications
Cause	The element type to modify is not one of VARCHAR2, NUMBER, or RAW.
Action	Only VARCHAR2, NUMBER and RAW collection elements can be modified.

 

PLS-00731	PLS-00731: ALTER TYPE is supported only on schema-level types
Cause	An attempt was made to alter a type that was not schema-level.
Action	ALTER TYPE is not legal for this type.

 

PLS-00732	PLS-00732: Illegal overload of ellipsis in formal parameter list
Cause	An ellipsis and a non-ellipsis type appeared at the same position in separate overload candidates. Currently, if ellipsis types are used they must appear in ALL overload candidates with the same name (regardless of the number or types of their formal parameters) at the same position in the formal parameter list.
Action	Make sure that ellipsis types appear at the same position in all overload candidates.

 

PLS-00733	PLS-00733: RPCs to variable argument functions are not allowed
Cause	Attempted to call a vararg function (a function which contains ellipsis in the formal parameter list) as an RPC.
Action	Do not call vararg functions as an RPC.

 

PLS-00734	PLS-00734: Illegal use of an associational parameter with a formal ellipsis
Cause	Attempted to use an associational actual argument for a formal ellipsis type argument.
Action	Remove associational parameters which correspond to formal ellipsis types.

 

PLS-00735	PLS-00735: Attempted to declare more than one formal ellipsis parameter
Cause	More than one ellipsis ("...") was found in a formal parameter specification for a function or procedure
Action	Make sure only one ellipsis appears in a formal parameter specification for any given function or procedure

 

PLS-00736	PLS-00736: user-declared operators are not allowed
Cause	An attempt was made by the user to declare an operator (a function whose name is enclosed in single quotes ("")). Operators may only be declared in package STANDARD.
Action	Remove the single quotes from around the function name, replacing them with double quotes ("") only if needed.

 

PLS-00737	PLS-00737: LIBRARY file specification exceeds the maximum allowed length
Cause	A string of more than expected number of chararacters was found for the LIBRARY file specification.
Action	Limit the LIBRARY file specification to the appropriate size for the platform.

 

PLS-00738	PLS-00738: REF target string changed during compilation
Cause	The current unit contains a REF to a target object. During compilation, the REF"s target object was simultaneously changed by a different session. The current unit is therefore invalid and needs to be recompiled to pick up the latest definition of the REF target.
Action	Recompile the unit that has this error.

 

PLS-00739	PLS-00739: FORALL INSERT/UPDATE/DELETE not supported on remote tables
Cause	The current statement refers to remote insert/update/delete for remote object.
Action	Use a FOR loop instead of a FORALL loop or call a remote function or procedure that includes the FORALL INSERT/UPDATE/ DELETE statement.

 

PLS-00751	PLS-00751: cannot find PACKAGE SYS_STUB_FOR_PURITY_ANALYSIS
Cause	A top level subprogram (function or procedure) cannot be created if the system package SYS_STUB_FOR_PURITY_ANALYSIS is missing in the Oracle database.
Action	Make sure the package is in the database, and retry the creation

 

PLS-00752	PLS-00752: Table function string is in an inconsistent state.
Cause	Some of the internally generated types prefixed with SYS_ have been dropped. These should never be dropped by the user.
Action	Recompile the table function or the package or type that contains the table function.

 

PLS-00753	PLS-00753: malformed or corrupted wrapped unit
Cause	The format of the wrapped unit being compiled is not understood by the compiler. This may be because the unit was edited or modified after it was wrapped.
Action	Rewrap the unit. NLS_DO_NOT_TRANSLATE [800,800]

 

PLS-00801	PLS-00801: internal error [string]
Cause	This is a generic internal error that might occur during compilation or execution. The first parameter is the internal error number.
Action	Report this error as a bug to your Customer Support representative.

 

PLS-00900	PLS-00900: can"t find body of unit "string"
Cause	At run time, the body of a program unit could not be found. This can happen for one of two reasons. -- First, there may be a unit "a" which calls a module "b", where the spec for "b" exists but not the body. In this case, since the spec is present, there will be no compile-time errors. -- Secondly, this can occur if there is a reference to a sequence outside of the proper context such as a SQL statement. In this case, the "spec" of the sequence reference can be found, but it is invalid to actually run code which references the sequence outside a SQL statement, as in: i := seq.nextval;
Action	If caused by the first reason, create a body for the object that is being referenced. If caused by the second reason, move the sequence into a SQL statement. For example, i := seq.nextval; can be replaced by: select seq.nextval into temp from dual; i := temp;

 

PLS-00901	PLS-00901: the data type of column "string" of table "string" is not supported
Cause	A column in a database table belongs to a datatype that is not supported by the current release of PL/SQL.
Action	Remove the offending column from the table or copy the desired columns to another table.

 

PLS-00902	PLS-00902: A READ-ONLY bind variable used in OUT or IN-OUT context
Cause	A host variable that is protected from update was used in a context that allows an update.
Action	Check the context and change the use of the host variable, or assign the value of the host variable to a PL/SQL local variable, then use the local variable instead.

 

PLS-00904	PLS-00904: insufficient privilege to access object string
Cause	An attempt was made to operate on a database object without the required privilege. This error occurs, for example, if an attempt was made to UPDATE a table for which only SELECT privileges were granted.
Action	Ask the DBA to perform the operation or to grant you the required privilege.

 

PLS-00905	PLS-00905: object string is invalid
Cause	An invalid package specification or stored subprogram was referenced. A package specification or stored subprogram is invalid if its source code or any database object it references has been DROPped, REPLACEd, or ALTERed since it was last compiled.
Action	Find out what invalidated the package specification or stored subprogram, then make sure that Oracle can recompile it without errors.

 

PLS-00906	PLS-00906: Compilation is not possible
Cause	The PL/SQL compiler cannot run properly because its operating environment is corrupted. For example, its error message file might be inaccessible.
Action	Check the PL/SQL operating environment, making sure that all files required by the compiler are accessible.

 

PLS-00907	PLS-00907: cannot load library unit string (referenced by string)
Cause	PL/SQL is unable to find and load a library unit that was previously available. This typically happens when you try to load a unit which references another library unit that is non-existent or invalid.
Action	Provide the needed library unit.

 

PLS-00908	PLS-00908: The stored format of string is not supported by this release
Cause	PL/SQL cannot understand the stored format of a library unit. It has been compiled or shrink-wrapped with a version of PL/SQL either too new or too old for this version to understand it.
Action	Recompile the library unit for this version of PL/SQL.

 

PLS-00909	PLS-00909: object string is not declared or insufficient privileges to access object string
Cause	An object from the operator declaration is not declared, or it is declared but there is no sufficient privileges to access that object.
Action	Declare the object, or ask the DBA to grant the privileges required to access the object.

 

PLS-00910	PLS-00910: insufficient privilege to inherit from type string
Cause	An attempt was made to inherit from a type without the required UNDER privilege.
Action	none

 

PLS-00920	PLS-00920: parameter plsql_native_library_dir is not set
Cause	A PL/SQL program is being compiled natively, but the compiler parameter plsql_native_library_dir, which denotes the directory to store the native shared objects (DLL), is not set.
Action	The DBA should set this parameter.

 

PLS-00923	PLS-00923: native compilation failed: string:string
Cause	The native compilation of PL/SQL program has failed because the native shared object (DLL) could not be created successfully.
Action	The DBA should ensure that the commands specified in spnc_commands file are correct.

 

PLS-00924	PLS-00924: native compilation is not supported on this platform
Cause	Native compilation of PL/SQL programs is not supported on this platform.
Action	Compile the PL/SQL program to bytecode by setting the parameter plsql_compiler_flags to INTERPRETED.

 

PLS-00925	PLS-00925: native compilation failed: Unable to create C file (string string)
Cause	Native compilation of a PL/SQL program failed because the C file could not be created. It is likely that the system paramter plsql_native_library_dir does not reference a writable, existing directory
Action	Ensure that the system parameter plsql_native_library_dir references a dirextory which exists, and is writable.

 

PLS-00950	PLS-00950: In this version, PL/SQL tables can not be used in this SQL statement.
Cause	In a SQL statement, a PL/SQL table was referenced incorrectly. For example, the following reference might have been made, but PL/SQL table attributes can only be used in procedural statements: SELECT ename_tab.COUNT INTO name_count WHERE ...
Action	Remove the incorrect reference from the SQL statement.

 

PLS-00951	PLS-00951: %s Feature is not supported by this release
Cause	PL/SQL cannot understand something in an imported library unit. It uses some feature either too new or too old for this version to understand it.
Action	Recompile the imported library unit with this version of PL/SQL, to discover more precisely what feature is not supported.

 

PLS-00960	PLS-00960: RPCs cannot use parameters with schema-level object types in this release
Cause	Schema-level object types, or types which recursively use such types, were used in an RPC, which is not permitted. For example: create type foo as object (...) create package my_pack is type my_rec is record(v foo); -- on a remote server: x my_pack.my_rec@rpc; -- illegal attempt to use type my_rec
Action	Use only PL/SQL-defined types in RPC calls. It may be necessary to add extra code to element-wise copy schema-level types into local types in order to move such data through an RPC.

 

PLS-00970	PLS-00970: The class name of a method must match that of EXTERNAL NAME clause in the type header
Cause	The class name defined as part of the method signature does not match the one defined in the type header in the EXTERNAL NAME clause. create type foo as object EXTERNAL NAME "foo" LANGUAGE JAVA (... MEMBER FUNCTION my (number) return number EXTERNAL NAME "bar.func(oracle.sql.NUMBER) return oracle.sql.NUMBER", .. );
Action	Either omit the class name from the method signature or use the one defined in the type header.

 

PLS-00989	PLS-00989: Cursor Variable in record, object, or collection is not supported by this release
Cause	3.0 Implementation Restriction for Ref Cursors
Action	none

 

PLS-00990	PLS-00990: Index Tables of Cursor Variables are disallowed
Cause	2.2 Implementation Restriction for Ref Cursors
Action	none

 

PLS-00992	PLS-00992: Cursor Variables cannot be FETCH"ed from
Cause	2.2 Implementation Restriction for Ref Cursors
Action	none

 

PLS-00993	PLS-00993: Cursor variables cannot be passed as forwarded RPC arguments or results
Cause	An attempt was made to pass a cursor variable to or from a remote subprogram by way of a forwarded RPC, which is not allowed. For example, from a client-side tool, a procedure on a remote database cannot be used to open a cursor variable because remote subprograms cannot return the values of cursor variables.
Action	Change the subprogram call to reference the local database.

 

PLS-00994	PLS-00994: Cursor Variables cannot be declared as part of a package
Cause	An attempt was made to declare a cursor variable in a package specification, which is not allowed. Although REF CURSOR types can be defined in a PL/SQL block, subprogram, or package, cursor variables can be declared only in a block or subprogram.
Action	Move the cursor variable declaration into a PL/SQL block or subprogram.

 

PLS-00995	PLS-00995: unhandled exception # string
Cause	An exception was raised for which no handler was found. If it cannot find a handler for a raised exception, PL/SQL returns an unhandled exception to the host environment. The number embedded in the message is an Oracle error code listed in this manual.
Action	Fix the condition that raised the exception, write an appropriate exception handler, or use the OTHERS handler. If there is an appropriate handler in the current block, the exception was raised in a declaration or exception handler, and therefore propagated immediately to the enclosing block.

 

PLS-00996	PLS-00996: out of memory
Cause	A request from PL/SQL for more memory failed.
Action	Make sure that you are not referencing the wrong row in a PL/SQL table and that the program is not recursing too deeply.

 

PLS-00997	PLS-00997: no cursor return types allowed in this beta version
Cause	Cursor return types have bugs, and it is best to disable them for now.
Action	none