Oracle 11g Error Codes and Solution Suggestions from ORA-02400 to ORA-02500

Oracle 11g Error Codes and Solution Suggestions from ORA-02400 to ORA-02500

ORA-02400: explain plan output buffer size limit exceeded

Cause: Internally this error is raised and caught to handle cases where the plan output exceeds te buffer size. The output is truncated in cases.

Action: This error should never be seen externally.

ORA-02401: cannot EXPLAIN view owned by another user

Cause: The view specified in the SQL statement belongs to another user and cannot be explained.

Action: Create a view with the same definition that belongs to current user.

ORA-02402: PLAN_TABLE not found

Cause: The table used by EXPLAIN to store row source information does not exist in the current schema.

Action: Create a plan table in the current schema or use the INTO clause of the statement to put the results of the explain command in an existing plan table.

ORA-02403: plan table does not have correct format

Cause: The explicit plan table does not have the appropriate field definitions.

Action: Redefine the plan table to have the appropriate field definitions.

ORA-02404: specified plan table not found

Cause: The specified plan table does cannot be found.

Action: Create the specified plan table or use an existing plan table.

ORA-02405: invalid sql plan object provided

Cause: The user provided a NULL, empty, or malformed object of type SQL_PLAN_TABLE_TYPE

Action: Provide a new, properly formed object to the function

ORA-02420: missing schema authorization clause

Cause: the AUTHORIZATION clause is missing from a create schema statement.

Action: Preceed the schema authorization identifier with the AUTHORIZATION keyword.

ORA-02421: missing or invalid schema authorization identifier

Cause: the schema name is missing or is incorrect in an authorization clause of a create schema statement.

Action: If the name is present, it must be the same as the current schema.

ORA-02422: missing or invalid schema element

Cause: A statement other than a create table, create view, or grant privilege appears in a create schema statement.

Action: Self-evident.

ORA-02423: schema name does not match schema authorization identifier

Cause: a table definition with a schema name prepended to the table name does not match the schema name provided in the authorization clause of a create schema statement.

Action: make sure the schema names match.

ORA-02424: potential circular view references or unknown referenced tables

Cause: the create schema statement contains views that depend on other views in the containing create schema statement or they contain references to unknown tables.

Action: create the dependent views in a separate create schema statement and make sure all referenced tables are either defined in the create schema statement or exist outside the statement.

ORA-02425: create table failed

Cause: a create table statement failed in the create schema statement.

Action: the cause for failure will be presented below this error message. Follow appropriate action(s) as suggested by the subsequent error message.

ORA-02426: privilege grant failed

Cause: a grant privilege statement failed inthe create schema statement.

Action: the cause for failure will be presented below this error message. Follow appropriate action(s) as suggested by the subsequent error message.

ORA-02427: create view failed

Cause: a create view statement failed in the create schema statement.

Action: the cause for failure will be presented below this error message. Follow appropriate action(s) as suggested by the subsequent error message.

ORA-02428: could not add foreign key reference

Cause: could not add a foreign key reference because of error in declaration. Either referenced table does not exist or table does not have an unique key.

Action: make sure referenced table exists and/or has unique key

ORA-02429: cannot drop index used for enforcement of unique/primary key

Cause: user attempted to drop an index that is being used as the enforcement mechanism for unique or primary key.

Action: drop the constraint instead of the index.

ORA-02430: cannot enable constraint (string) – no such constraint

Cause: the named constraint does not exist for this table.

Action: Obvious

ORA-02431: cannot disable constraint (string) – no such constraint

Cause: the named constraint does not exist for this table.

Action: Obvious

ORA-02432: cannot enable primary key – primary key not defined for table

Cause: Attempted to enable a primary key that is not defined for the table.

Action: Need to add a primary key definition for the table.

ORA-02433: cannot disable primary key – primary key not defined for table

Cause: Attempted to disable a primary key tht is not defined for the table.

Action: None

ORA-02434: cannot enable unique(string) – unique key not defined for table

Cause: attempted to enable a unique key that is not defined for the table.

Action: None

ORA-02435: cannot disable unique(string) – unique key not defined for table

Cause: attempted to disable a unique key that is not deined for the table.

Action: None

ORA-02436: date or system variable wrongly specified in CHECK constraint

Cause: An attempt was made to use a date constant or system variable, such as USER, in a check constraint that was not completely specified in a CREATE TABLE or ALTER TABLE statement. For example, a date was specified without the century.

Action: Completely specify the date constant or system variable. Setting the event 10149 allows constraints like “a1 > ’10-MAY-96′”, which a bug permitted to be created before version 8.

ORA-02437: cannot validate (string.string) – primary key violated

Cause: attempted to validate a primary key with duplicate values or null values.

Action: remove the duplicates and null values before enabling a primary key.

ORA-02438: Column check constraint cannot reference other columns

Cause: attempted to define a column check constraint that references another column.

Action: define it as a table check constriant.

ORA-02439: Unique index on a deferrable constraint is not allowed

Cause: attempted to enable a deferrable primary key/unique constraint that has an existing unique index on the constraint columns.

Action: Drop the index on the constraint columns or make the constraint not deferrable.

ORA-02440: Create as select with referential constraints not allowed

Cause: create table foo (… ref. con. …) as select …;

Action: Create the table as select, then alter the table to add the constraints afterwards.

ORA-02441: Cannot drop nonexistent primary key

Cause: alter table drop primary key – primary key does not exist.

Action: None

ORA-02442: Cannot drop nonexistent unique key

Cause: alter table drop unique (<col list>) – unique specification does not exist.

Action: make sure column list for unique constraint is correct.

ORA-02443: Cannot drop constraint – nonexistent constraint

Cause: alter table drop constraint <constraint_name>

Action: make sure you supply correct constraint name.

ORA-02444: Cannot resolve referenced object in referential constraints

Cause: attempted to define foreign key referencing an object which cannot be resolved to a base table reference

Action: referential constraints can only be defined on objects which can be resolve to base table reference

ORA-02445: Exceptions table not found

Cause: the explicity or implicity declared exceptions table does not exist.

Action: Create the table then issue the enable command again.

ORA-02446: CREATE TABLE … AS SELECT failed – check constraint violated

Cause: An attempt was made to use a CREATE TABLE … AS SELECT statement when some rows violated one or more CHECK constraints.

Action: Do not select rows that violate constraints.

ORA-02447: cannot defer a constraint that is not deferrable

Cause: An attempt was made to defer a nondeferrable constraint

Action: Drop the constraint and create a new one that is deferrable

ORA-02448: constraint does not exist

Cause: The named constraint does not exist

Action: Stop trying to do something with a nonexistant constraint

ORA-02449: unique/primary keys in table referenced by foreign keys

Cause: An attempt was made to drop a table with unique or primary keys referenced by foreign keys in another table.

Action: Before performing the above operations the table, drop the foreign key constraints in other tables. You can see what constraints are referencing a table by issuing the following command: SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = “tabnam”;

ORA-02450: Invalid hash option – missing keyword IS

Cause: Missing IS keyword.

Action: Specify HASH IS option.

ORA-02451: duplicate HASHKEYS specification

Cause: The HASHKEYS option is specified more than once.

Action: Only specify the HASHKEYS option once.

ORA-02452: invalid HASHKEYS option value

Cause: The specified HASHKEYS option must be an integer value.

Action: Specify an appropriate value.

ORA-02453: duplicate HASH IS specification

Cause: The HASH IS option is specified more than once.

Action: only specify the HASH IS option once.

ORA-02454: Number of hash keys per block (string) exceeds maximum of string

Cause: The SIZE argument is too small.

Action: Increase the SIZE argument.

ORA-02455: The number of cluster key column must be 1

Cause: When specifing the HASH IS option, the number of key columns must be 1.

Action: Either do not specify the HASH IS option or reduce the number of key columns.

ORA-02456: The HASH IS column specification must be NUMBER(*,0)

Cause: The column specification must specify an integer.

Action: Specify the column definition as type NUMBER(precision, 0).

ORA-02457: The HASH IS option must specify a valid column

Cause: The HASH IS column name is not specified in the cluster definition.

Action: Specify a valid column name.

ORA-02458: HASHKEYS must be specified for a HASH CLUSTER

Cause: The HASHKEYS option must be specified when creating a HASH CLUSTER.

Action: Specify the HASHKEYS option.

ORA-02459: Hashkey value must be a positive integer

Cause: The value of the hash key was not a positive number.

Action: Specify a positive integer.

ORA-02460: Inappropriate index operation on a hash cluster

Cause: An attempt to create a cluster index was issued on a hash cluster.

Action: Do not attempt to create such an index.

ORA-02461: Inappropriate use of the INDEX option

Cause: This option is only valid for non hash clusters.

Action: Do not specify this option.

ORA-02462: Duplicate INDEX option specified

Cause: The INDEX option is specified more than once.

Action: Only specify the INDEX option once.

ORA-02463: Duplicate HASH IS option specified

Cause: The HASH IS option is specified more than once.

Action: Only specify the HASH IS option once.

ORA-02464: Cluster definition can not be both HASH and INDEX

Cause: The cluster can either be a hash or indexed cluster – not both.

Action: Remove either the HASH IS or INDEX options.

ORA-02465: Inappropriate use of the HASH IS option

Cause: This option is only valid for clusters

Action: Do not specify this option

ORA-02466: The SIZE and INITRANS options cannot be altered for HASH CLUSTERS.

Cause: An attempt was made to change the SIZE and INITRANS options after the hash cluster was created.

Action: Do not specify this option.

ORA-02467: Column referenced in expression not found in cluster definition

Cause: A column in the hash is expression was not present in cluster definition.

Action: Recreate the cluster and correct the error in hash expression.

ORA-02468: Constant or system variable wrongly specified in expression

Cause: A constant or system variable was specified in the hash expression.

Action: Recreate the cluster and correct the error in hash expression.

ORA-02469: Hash expression does not return an Oracle Number.

Cause: Result of evaluating hash expression is not an Oracle Number.

Action: Recreate the cluster and correct the error in hash expression.

ORA-02470: TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.

Cause: TO_DATE, USERENV and SYSDATE are not allowed in hash expressions.

Action: Recreate the cluster and correct the error in hash expression.

ORA-02471: SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expre\ssion.

Cause: SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed in hash expression\s.

Action: Recreate the cluster and remove the offending keywords.

ORA-02472: PL/SQL functions not allowed in hash expressions

Cause: A PL/SQL function was used in the hash expression.

Action: Recreate the cluster and remove the PL/SQL function.

ORA-02473: Error while evaluating the cluster’s hash expression.

Cause: An error occurred while evaluating the clusters hash expression.

Action: Correct the query and retry.

ORA-02474: Fixed hash area extents used (string) exceeds maximum allowed (string)

Cause: The number of extents required for creating the fixed hash area exceeds the maximum number allowed.

Action: Reduce the number of extents required by increasing the extent allocation sizes within the STORAGE clause.

ORA-02475: maximum cluster chain block count of string has been exceeded

Cause: The number of blocks in a cluster chain exceeds the maximum number allowed.

Action: Increase SIZE parameter in CREATE CLUSTER statement or reconsider suitability of cluster key.

ORA-02476: can not create index due to parallel direct load on table

Cause: A parallel direct load is occurring to the specified table.

Action: Retry statement after load is complete.

ORA-02477: can not perform parallel direct load on object string

Cause: A parallel direct load is not possible because an index is is being created on the table.

Action: Retry load after index creation is complete.

ORA-02478: merge into base segment would overflow MAXEXTENTS limit

Cause: Merge of temporary segment into base segment failed because MAXEXTENTS was larger than the total in the temp and base segments

Action: Use a larger value for MAXEXTENTS on the base segment or make the extents in the temporary segments larger

ORA-02479: error while translating file name for parallel load

Cause: An invalid file name was specified to load data into.

Action: Specify a valid database file.

ORA-02481: Too many processes specified for events (max string)

Cause: Too many processes specified than allowed per event.

Action: Enter fewer processes by using ranges or wildcards if possible.

ORA-02482: Syntax error in event specification (string)

Cause: Illegal event string

Action: Enter a legal event string

ORA-02483: Syntax error in process specification (string)

Cause: Illegal process string

Action: Enter a legal process string

ORA-02484: Invalid _trace_buffers parameter specification (string)

Cause: Bad process or size in _trace_buffers INIT.ORA parameter.

Action: None

ORA-02485: Invalid _trace_options parameter specification (string)

Cause: Bad syntax for _trace_options INIT.ORA parameter.

Action: None

ORA-02486: Error in writing trace file string

Cause: Error occurred in creating/writing the file.

Action: Check file name and make sure it is constructed properly. Also, check permissions for directories.

ORA-02487: Error in converting trace data

Cause: Incompatible binary trace data was specified.

Action: Check the format of the input data.

ORA-02488: Error encountered when accessing file [string] for trace conversion

Cause: An attempt was made to open or access the trace file during a trace conversion.

Action: Check the permissions for both input and output files. Also, check the file compatibility for the trace conversion.

ORA-02490: missing required file size in RESIZE clause

Cause: No value was specified for the RESIZE clause.

Action: Use correct syntax.

ORA-02491: missing required keyword ON or OFF in AUTOEXTEND clause

Cause: The keyword ON or OFF was not specified for the AUTOEXTEND clause.

Action: Use correct syntax.

ORA-02492: missing required file block increment size in NEXT clause

Cause: No value was specified for the NEXT clause.

Action: Use correct syntax.

ORA-02493: invalid file increment size in NEXT clause

Cause: A non-integer value was used for the NEXT clause of the DATAFILE list.

Action: Use correct syntax.

ORA-02494: invalid or missing maximum file size in MAXSIZE clause

Cause: UNLIMITED was not specified, or an invalid integer value was specified, for the MAXSIZE clause in the DATAFILE file list. The MAXSIZE value cannot be smaller than the SIZE value.

Action: Use correct syntax.

ORA-02495: cannot resize file string, tablespace string is read only

Cause: An attempt was made to resize a data file in a tablespace that is read only.

Action: Change the tablespace to read/write and retry the resize operation.

ORA-02700: osnoraenv: error translating ORACLE_SID

Cause: Two-task driver could not find the value of ORACLE_SID in the environment.

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