CLSR-01003: Error number encountered during mounting database

CLSR-01003: Error number encountered during mounting database

Cause: Unexpected error occurs when mounting database.

Action: Check current status of database before retrying.

CLSR-01002: Unable to process instance startup

CLSR-01002: Unable to process instance startup

Cause: ORACLE_HOME environment variable not set.

Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported.

CLSR-01001: Unsupported open mode number is specified

CLSR-01001: Unsupported open mode number is specified

Cause: Unsupported open mode is specified for mounting database.

Action: Retry again with a valid open mode.

CLSR-00531: Can not get primary group name

CLSR-00531: Can not get primary group name

Cause: There is no primary group for this OS.

Action: Not faital. None.

CLSR-00530: Can not get user name

CLSR-00530: Can not get user name

Cause: Error caused by OSD layer.

Action: Contact Oracle support.

CLSR-00529: RACGONS: host and port number to be removed does not exist

CLSR-00529: RACGONS: host and port number to be removed does not exist

Cause: host and port number to be removed is not configured in OCR.

Action: None.

CLSR-00528: RACGONS: host and port number already configured in OCR

CLSR-00528: RACGONS: host and port number already configured in OCR

Cause: host and port number already configured in OCR.

Action: None.

CLSR-00527: OCR operation failed

CLSR-00527: OCR operation failed

Cause: See related error messages about the OCR operation.

Action: Fix the related error. Then try again.

CLSR-00526: Failed to retrieve database configuration in OCR

CLSR-00526: Failed to retrieve database configuration in OCR

Cause: See the related error message.

Action: Run crs_stat to make sure CSS and OCR working properly and database configuration in ocr is initialized.

CLSR-00525: prsr initialization failed

CLSR-00525: prsr initialization failed

Cause: See the related error message.

Action: Run crs_stat to make sure CSS and OCR working properly.

CLSR-00524: Resource string is stopping, resource string cannot start

CLSR-00524: Resource string is stopping, resource string cannot start

Cause: Resource cannot start because its composite resource is stopping.

Action: Retry to start the resource when its composite resource is not stopping.

CLSR-00523: Resource string is not enabled

CLSR-00523: Resource string is not enabled

Cause: CRS resource is not enabled.

Action: Enable the CRS resource.

CLSR-00522: Resource string is not registered

CLSR-00522: Resource string is not registered

Cause: CRS resource is not registered.

Action: Register the CRS resource.

CLSR-00521: Event string is rejected by EVM daemon

CLSR-00521: Event string is rejected by EVM daemon

Cause: No template has been registered for the event or caller is not authorized to post the event.

Action: Check if there is a template registered for this event and the authority of posting this event.

CLSR-00520: No service member found

CLSR-00520: No service member found

Cause: No service member is found running for the composite service resource.

Action: No action required as the composite service resource will fail itself.

CLSR-00519: No instance found

CLSR-00519: No instance found

Cause: No instance is found running for the database resource.

Action: No action required as the database resource will fail itself.

CLSR-00518: Failed to register a preconnect service name

CLSR-00518: Failed to register a preconnect service name

Cause: The requested preconnect service name cannot be registered.

Action: Check log file for detail.

CLSR-00517: Failed to register a service name

CLSR-00517: Failed to register a service name

Cause: The requested service name cannot be registered.

Action: Check log file for detail.

CLSR-00516: No service provider found at this node

CLSR-00516: No service provider found at this node

Cause: No suitable service provider is found on this node.

Action: No action required as the service member will try to start on another node.

CLSR-00515: A service member is already running on this node

CLSR-00515: A service member is already running on this node

Cause: There is a service member of the same service running on this node.

Action: No action required as the service member will try to start on another node.

CLSR-00514: Unable to locate PMON (pid=string(

CLSR-00514: Unable to locate PMON (pid=string(

Cause: Cannot find PMON with this pid.

Action: Check the existence of PMON.

CLSR-00513: Message file is not found

CLSR-00513: Message file is not found

Cause: The requested OCI message file is not found.

Action: Check if the message file is properly installed.

CLSR-00512: Invalid CAA trigger event type (string(

CLSR-00512: Invalid CAA trigger event type (string(

Cause: Invalid CAA trigger event type is specified.

Action: Try again with a valid type.

CLSR-00511: Error number encountered when handling incoming EVM message

CLSR-00511: Error number encountered when handling incoming EVM message

Cause: Error encountered when handling incoming EVM message.

Action: Check log file for detail.

CLSR-00510: Unable to load NLS data

CLSR-00510: Unable to load NLS data

Cause: Failed to initialize NLS data loading.

Action: Not action required as default data loading will be used.

CLSR-00509: Unable to initialize NLS

CLSR-00509: Unable to initialize NLS

Cause: Failed to initialize callback structure for NLS.

Action: Contact customer support.

PLS-00904: insufficient privilege to access object string

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-00902: A READ-ONLY bind variable used in OUT or IN-OUT context

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 or SQL local variable, then use the local variable instead.

PLS-00901: the data type of column string of table string is not supported

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 or SQL.

Action: Remove the offending column from the table or copy the desired columns to another table.

PLS-00900: can t find body of unit string

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-00801: internal error (string(

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-00753: malformed or corrupted wrapped unit

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-00752: Table function string is in an inconsistent state.

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-00751: cannot find PACKAGE SYS_STUB_FOR_PURITY_ANALYSIS

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-00739: FORALL INSERT or UPDATE or DELETE not supported on remote tables

PLS-00739: FORALL INSERT or UPDATE or DELETE not supported on remote tables

Cause: The current statement refers to remote insert or update or 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 or UPDATE or DELETE statement.

PLS-00738: REF target string changed during compilation

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-00737: LIBRARY file specification exceeds the maximum allowed length

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-00736: user-declared operators are not allowed

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-00735: Attempted to declare more than one formal ellipsis parameter

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-00734: Illegal use of an associational parameter with a formal ellipsis

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-00733: RPCs to variable argument functions are not allowed

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-00732: Illegal overload of ellipsis in formal parameter list

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-00731: ALTER TYPE is supported only on schema-level types

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-00730: collection element type does not allow modifications

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-00729: only widening of the collection element type is allowed

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-00728: the limit of a VARRAY can only be increased and to a maximum 2,147,483,647

PLS-00728: the limit of a VARRAY can only be increased and to a maximum 2,147,483,647

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-00727: MODIFY LIMIT is supported only on schema-level varray types

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-00500: invalid operator binding

PLS-00500: invalid operator binding

Cause: An operator binding fucntion cannot be found in the specified scope.

Action: Provide the correct number and types of parameters for the operator binding fucntion. Or, specify the correct names for schema, package, or type containing the operator binding fucntion.

PLS-00499: coercion into collection of records not supported

PLS-00499: coercion into collection of records not supported

Cause: A SELECT or FETCH may specify a column list to be coerced into a variable which is a collection of records. This is type checked as correct, but not yet supported because of the implicit layout change required.

Action: Express the SELECT with an object constructor around the columns and use a collection of objects as an INTO variable. Or, build the collection one row at a time coercing each row into a record which happens to be an element. Or, use a record of collections.

PLS-00498: illegal use of a type before its declaration

PLS-00498: illegal use of a type before its declaration

Cause: A variable or constant was declared to be of a type whose declaration appears later in the compilation unit; or, a type or subtype was declared in terms of another type whose declaration appears later in the compilation unit.

Action: Ensure that the type declaration preceeds its use in the variable or constant or type declaration.

PLS-00497: cannot mix between single row and multi-row (BULK) in INTO list

PLS-00497: cannot mix between single row and multi-row (BULK) in INTO list

Cause: - When BULK syntax (e.g. BULK COLLECT INTO) is used to retrieve data, every variable in the INTO list has to be of type that is a collection of the type of the corresponding column. type with the corresponding column.

Action: Change the INTO list so that all variables have correct data types

PLS-00496: too few columns in SELECT...INTO statement after bursting record targets

PLS-00496: too few columns in SELECT...INTO statement after bursting record targets

Cause: Type checking indicated the columns in a SELECT or FETCH were being collected into a record in the INTO list. The record was burst into its fields. There were not enough columns to fill all of the fields in the record.

Action: Change the number of columns or the record variable(s) in the INTO clause so that they match.

PLS-00495: too many columns in SELECT...INTO statement after bursting record targets

PLS-00495: too many columns in SELECT...INTO statement after bursting record targets

Cause: Type checking indicated the columns in a SELECT or FETCH were being collected into a record in the INTO list. The record was burst into its fields. There were not enough fields in the record for each of the columns.

Action: Change the number of columns or the record variable(s) in the INTO clause so that they match.

PLS-00494: coercion into multiple record targets not supported

PLS-00494: coercion into multiple record targets not supported

Cause: The INTO list of a SELECT or FETCH specified more than a single record- type target and the column types required coercion into a record to match the INTO list. This is type checked as correct, but not yet supported.

Action: Create a new record type to hold all of the column types or code the SELECT with an INTO target for every source column.

PLS-00493: invalid reference to a server-side object or function in a local context

PLS-00493: invalid reference to a server-side object or function in a local context

Cause: A reference to a server-side object (e.g. a table column) or function (a group function such as SUM, AVG, MIN, MAX, ... ) was found in a context where only PL or SQL objects may be present (such as within the parameter list of a local function or as the index of a (local) PL or SQL table.)

Action: Rewrite the offending statement; or (if a local function call is the problem context), make the function non-local (either packaged or top- level.)

PLS-00492: variable or constant initialization may not refer to functions declared in the same package

PLS-00492: variable or constant initialization may not refer to functions declared in the same package

Cause: If a package spec p declares a function f, that function may not be used in any variable declarations in that same package spec. This is because of a circular instantiation problem: in order to fully instantiate the package spec, the variable must be initialized. To initialize the variable, the function body code in the package body must be executed. That requires that the package body be instantiated. However, the package body cannot be instantiated until the package spec is fully instantiated.

Action: Remove the reference to the function from the variable initialization. A technique which often works is to move the variable initialization from the variable declaration (in the package spec) to the package body initialization block.

PLS-00491: numeric literal required

PLS-00491: numeric literal required

Cause: A constant or variable was used where a numeric literal is required. For example, the code might look like my_ename VARCHAR2(max_len); instead of my_ename VARCHAR2(15); When specifying the maximum length of a VARCHAR2 variable, an integer literal must be used.

Action: Replace the identifier with a numeric literal.

PLS-00490: illegal statement

PLS-00490: illegal statement

Cause: A constant, variable, function call, or incomplete statement was used where a statement was expected. For example, instead of calling a function from an expression, it might have been called as a statement (as if it were a procedure).

Action: Check the statement, making sure that its commands, identifiers, operators, delimiters, and terminator form a complete and valid PL or SQL statement.

PLS-00489: invalid table reference: string must be a column in this expression

PLS-00489: invalid table reference: string must be a column in this expression

Cause: In a query, a select-list item refers to a table in the FROM clause but not to a database column.

Action: Check the spelling of the column names, make sure each column in the select list refers to a table in the FROM clause, then re-execute the query.

PLS-00488: invalid variable declaration: object string must be a type or subtype

PLS-00488: invalid variable declaration: object string must be a type or subtype

Cause: The datatype specifier in a variable declaration does not designate a legal type. For example, the %TYPE attribute might not have been added to a declaration, as in DECLARE my_sal emp.sal%TYPE; my_ename emp.ename; -- missing %TYPE ... When declaring a constant or variable, to provide the datatype of a column automatically, use the %TYPE attribute. Likewise, when declaring a record, to provide the datatypes of a row automatically, use the %ROWTYPE attribute.

Action: Make sure the datatype specifier designates a legal type. Remember to use the %TYPE and %ROWTYPE attributes when necessary.