Oracle 12c R2 Error Codes and Solution Suggestions from ORA-02300 to ORA-02500
- ORA-02300: invalid value for OIDGENERATORS
Cause: A number was not specified for the value of OIDGENERATORS.
Action: Specify a number for OIDGENERATORS.
Cause: A number greater than 255 was specified for the value of OIDGENERATORS.
Action: Make sure the number specified for OIDGENERATORS does not exceed 255.
Cause: An invalid or missing type name was entered in a statement.
Action: Enter a valid type name in the statement and retry the operation.
Cause: An attempt was made to drop or replace a type that has type or table dependents.
Action: For DROP TYPE, drop all type(s) and table(s) depending on the type and then retry the operation, or use the FORCE option. For CREATE TYPE, drop all type(s) and table(s) depending on the type and then retry the operation, or drop all table(s) depending on the type and retry with the FORCE option.
Cause: An attempt was made to enter an object identifier literal for CREATE TYPE that is either: – not a string of 32 hexadecimal characters – an object identifier that already identifies an existing object – an object identifier different from the original object identifier already assigned to the type
Action: Do not specify the object identifier clause or specify a 32 hexadecimal-character object identifier literal that is unique or identical to the originally assigned object identifier. Then retry the operation.
Cause: An attempt was made to GRANT or REVOKE an invalid privilege (not EXECUTE, DEBUG, or UNDER) on a type.
Action: GRANT or REVOKE only the EXECUTE, DEBUG, or UNDER privilege on types.
Cause: An attempt was made to create a type that already has some valid dependent(s) (these dependents depend on the fact that the type does not exist).
Action: Drop the dependents first before creating the type, or do not create the type.
Cause: An attempt was made to ALTER with REPLACE option a type that is not valid.
Action: Use the CREATE OR REPLACE TYPE command to modify the type.
Cause: An attempt was made to specify an invalid option, such as PACKED or UNPACKED, for the object type column.
Action: Remove the invalid option from column specification and retry the operation.
Cause: An attempt was made to acess the attributes of a NULL object instance.
Action: Ensure that the object instance is non-NULL before accessing.
Cause: The attributes in the object type column exceeded the maximum number of columns allowed in a table.
Action: Specify fewer attributes for the object type and retry the operation.
Cause: An attempt was made to ALTER with COMPILE option a type that is valid and has type or table dependents.
Action: No need to perform this operation.
Cause: The specified object type contains a nested attribute whose type is non-queryable.
Action: Use an object type with queryable attribute types.
Cause: The statement contains an illegal use of a type constructor.
Action: Refer to the SQL Reference manual for the correct statement syntax.
Cause: The number of arguments specified for the default constructor doesn’t match the number of attributes of the object type.
Action: Specify the correct number of arguments for the default constructor and retry the operation.
Cause: An error occurred while creating the storage table for the specified nested table column.
Action: See the messages that follow for more details. If the situation they describe can be corrected, do so; otherwise contact Oracle Support.
Cause: An error occured while performing DML on the storage table of the nested table column.
Action: If the situation described in the following messages can be corrected, do so; otherwise contact Oracle Support.
Cause: More than one column was selected in the THE subquery.
Action: Specify only one column in the SELECT list of the THE subquery and retry the operation.
Cause: An attempt was made to create an index on a non-indexable expression.
Action: Change the column datatype or do not create the index on an expression whose datatype is one of VARRAY, nested table, object, LOB, or REF.
Cause: An attempt was made to place a UNIQUE or a PRIMARY KEY constraint on a column of datatype VARRAY, nested table, object, LOB, FILE or REF.
Action: Change the column datatype or remove the constraint. Then retry the operation.
Cause: An attempt was made to specify the data type in the column constraint specification of an object table.
Action: Remove data type specification and retry the operation.
Cause: An attempt was made to create a constraint on a column posessing a non-constrainable datatype — VARRAY, nested table, object, LOB, FILE, or REF.
Action: Change the column datatype, or remove the constraint.
Cause: An attempt was made to create an index on an attributes of an object type column.
Action: Do not specify the index on the attribute.
Cause: An attempt was made to create a constraint on an attribute of an object type column.
Action: Remove the constraint or change the object type.
Cause: A datatype was not declared for this column (in the CREATE TABLE) and an attempt was made to create a constraint on an attribute of this column.
Action: Declare a datatype for the column.
Cause: An attempt was made to declare a CLUSTER column of datatype object, REF, nested table, VARRAY, LOB, or FILE.
Action: Remove the CLUSTER column or change the datatype of the column.
Cause: An attempt was made to extract an attribute of an object type column.
Action: Change the object type for the column and retry the operation.
Cause: An attempt was made to use dotted notation on a non-ADT column; that is, “a.b.c” where “a” is not an object type.
Action: Either change the column type to an object type or do not perform this operation.
Cause: A column constraint was not specified.
Action: Remove the column specification or specify a column constraint. Then retry the operation.
Cause: An attempt was made to specify the PACKED or UNPACKED keyword for a non-object type column.
Action: Remove the PACKED or UNPACKED keyword in the column specification and retry the operation.
Cause: An attempt was made to specify an UNPACKED column within a packed table.
Action: Remove the UNPACKED keyword in the column specification.
Cause: The use of the ALTER…REPLACE statement on a valid type caused a compilation error.
Action: Use the ALTER…REPLACE statement to replace the type with a valid type which does not cause compilation errors.
Cause: An attempt was made to revoke execute on a type that has dependents.
Action: Drop all table(s) depending on the type, then retry the operation, or use the FORCE option.
Cause: A CURSOR operator was used as one of the SELECT elements in the subquery of a CREATE VIEW or CREATE TABLE … AS SELECT statement.
Action: Remove the CURSOR operator and replace it with the CAST operator.
Cause: An attempt was made to grant privileges on the columns of an object table.
Action: n/a
Cause: An attempt was made to create a column of a VARRAY type which has an embedded LOB attribute. The LOB could be an attribute of a subtype of the declared type of VARRAY’s element.
Action: Remove offending attribute from type. If it is a subtype attribute then declare the VARRAY column NOT SUBSTITUTABLE.
Cause: An attempt was made to use an incomplete type definition as a column or table datatype.
Action: Complete the type definition and retry the operation.
Cause: An unexpected error condition was detected.
Action: Make a note of the error number and message and contact Oracle Support Services.
Cause: An OCI error has occurred.
Action: The table or column referenced may not be accessible. Contact Oracle Support Services if the problem cannot be resolved.
Cause: An OCI error has occurred.
Action: The table or column referenced may not be accessible. Contact Oracle Support Services if the problem cannot be resolved.
Cause: An error has occurred in a stream export or import operation. This message will be followed by another message giving more details about this error.
Action: See export/import documentation for an explanation of the second error message.
Cause: An attempt to open the specified file for data export/import failed.
Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if the problem cannot be resolved.
Cause: The load was discontinued due to space exhaustion in the database.
Action: Add space for the specified table.
Cause: The header may be corrupted.
Action: Contact Oracle Support Services.
Cause: An error has occurred in a stream export or import operation.
Action: Contact Oracle Support Services.
Cause: The specified file could not be used for this load because its database version was not compatible with the database version in the other files in the DUMPFILE clause.
Action: Verify all the files in the DUMPFILE clause are from the same unload operation.
Cause: An unexpected error occurred during initialization for data export/import.
Action: Contact Oracle Support Services.
Cause: An error occurred while trying to allocate memory. This is likely caused by insufficient memory.
Action: Reconnect to the instance and retry the operation.
Cause: An attempt to close the specified file for data export/import failed.
Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if the problem cannot be resolved.
Cause: An attempt to read from the specified file for data export/import failed.
Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if the problem cannot be resolved.
Cause: An attempt to write to the specified file for data export or import failed.
Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if the problem cannot be resolved.
Cause: An attempt to seek to the specified position in file failed.
Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if the problem cannot be resolved.
Cause: The table had some indexes which were loaded if there were no errors.
Action: None
Cause: A truncated or incomplete file was used for the load operation.
Action: Verify unload operation completed successfully and that the files had not been accidentally truncated.
Cause: A file could not be used for this load. See the following message for more information.
Action: Verify all the files in the DUMPFILE clause are from the same unload operation and that the unload was successful.
Cause: The specified file could not be used for this load because the internal number in the header was not valid.
Action: If the dump files were transferred over, verify the transfer operation was done correctly.
Cause: The specified file could not be used for this load because the internal metadata stored in this file does not match the metadata stored in the first file piece set.
Action: Verify all the files in the DUMPFILE clause are from the same unload operation.
Cause: The loader being used is incompatible with this version of the kernel.
Action: Upgrade your loader to at least the specified version or use the conventional path.
Cause: A conversion error occurred while loading data into a table. The message shows values for the field in the row that had the conversion error.
Action: None. This is only an informational message.
Cause: self-evident.
Action: Check the error given below this one.
Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row.
Action: See the message that follows for more information about the row that could not be loaded. To avoid this error, make sure the definition of the table being imported matches the definition of the table being exported.
Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row.
Action: See the message that follows for more information about the row that could not be loaded. To avoid this error, make sure the definition of the table being imported matches the definition of the table being exported.
Cause: a create, or alter profile command which names a resource not yet defined, or try to specify same resource twice.
Action: define resource first
Cause: A value of 0 or lower was specified for the limit.
Action: Specify a limit greater than 0. For password profile parameters, some additional restrictions apply: * For the INACTIVE_ACCOUNT_TIME profile parameter, the specified limit cannot be less than 15 days. * For the PASSWORD_GRACE_TIME profile parameter, 0 is allowed as a permissible value.
Cause: Try to create a profile which already exist
Action: n/a
Cause: Try to assign a user to a non-existant profile
Action: n/a
Cause: Try to drop PUBLIC_DEFAULT profile
Action: n/a
- ORA-02382: profile string has users assigned, cannot drop without CASCADE
- ORA-02383: illegal cost factor
Cause: Negative or UNLIMITED cost for this resourc
Action: n/a
- ORA-02390: exceeded COMPOSITE_LIMIT, you are being logged off
- ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit
Cause: An attempt was made to exceed the maximum number of concurrent sessions allowed by the SESSION_PER_USER clause of the user profile.
Action: End one or more concurrent sessions or ask the database administrator to increase the SESSION_PER_USER limit of the user profile.
- ORA-02392: exceeded session limit on CPU usage, you are being logged off
- ORA-02393: exceeded call limit on CPU usage
- ORA-02394: exceeded session limit on IO usage, you are being logged off
- ORA-02395: exceeded call limit on IO usage
- ORA-02396: exceeded maximum idle time, please connect again
Cause: as stated
Action: n/a
Cause: Only when using TP monitor
Action: expand limit
Cause: Stored procedured used up too much space in SYSTEM Tablespace
Action: Use less stored procedure
Cause: As stated
Action: n/a
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.
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.
Cause: The explicit plan table does not have the appropriate field definitions.
Action: Redefine the plan table to have the appropriate field definitions.
Cause: The specified plan table does cannot be found.
Action: Create the specified plan table or use an existing plan table.
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
Cause: the AUTHORIZATION clause is missing from a create schema statement.
Action: Preceed the schema authorization identifier with the AUTHORIZATION keyword.
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.
Cause: A statement other than a create table, create view, or grant privilege appears in a create schema statement.
Action: Self-evident.
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.
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.
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.
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.
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.
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
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.
Cause: the named constraint does not exist for this table.
Action: Obvious
Cause: the named constraint does not exist for this table.
Action: Obvious
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.
Cause: Attempted to disable a primary key tht is not defined for the table.
Action: None
Cause: attempted to enable a unique key that is not defined for the table.
Action: None
Cause: attempted to disable a unique key that is not deined for the table.
Action: None
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.
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.
Cause: attempted to define a column check constraint that references another column.
Action: define it as a table check constriant.
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.
Cause: create table foo (… ref. con. …) as select …;
Action: Create the table as select, then alter the table to add the constraints afterwards.
Cause: alter table drop primary key – primary key does not exist.
Action: None
Cause: alter table drop unique (col list) – unique specification does not exist.
Action: make sure column list for unique constraint is correct.
Cause: alter table drop constraint <constraint_name>
Action: make sure you supply correct constraint name.
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
Cause: the explicity or implicity declared exceptions table does not exist.
Action: Create the table then issue the enable command again.
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.
Cause: An attempt was made to defer a nondeferrable constraint
Action: Drop the constraint and create a new one that is deferrable
Cause: The named constraint does not exist
Action: Stop trying to do something with a nonexistant constraint
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”;
Cause: Missing IS keyword.
Action: Specify HASH IS option.
Cause: The HASHKEYS option is specified more than once.
Action: Only specify the HASHKEYS option once.
Cause: The specified HASHKEYS option must be an integer value.
Action: Specify an appropriate value.
Cause: The HASH IS option is specified more than once.
Action: only specify the HASH IS option once.
Cause: The SIZE argument is too small.
Action: Increase the SIZE argument.
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.
Cause: The column specification must specify an integer.
Action: Specify the column definition as type NUMBER(precision, 0).
Cause: The HASH IS column name is not specified in the cluster definition.
Action: Specify a valid column name.
Cause: The HASHKEYS option must be specified when creating a HASH CLUSTER.
Action: Specify the HASHKEYS option.
Cause: The value of the hash key was not a positive number.
Action: Specify a positive integer.
Cause: An attempt to create a cluster index was issued on a hash cluster.
Action: Do not attempt to create such an index.
Cause: This option is only valid for non hash clusters.
Action: Do not specify this option.
Cause: The INDEX option is specified more than once.
Action: Only specify the INDEX option once.
Cause: The HASH IS option is specified more than once.
Action: Only specify the HASH IS option once.
Cause: The cluster can either be a hash or indexed cluster – not both.
Action: Remove either the HASH IS or INDEX options.
Cause: This option is only valid for clusters
Action: Do not specify this option
Cause: An attempt was made to change the SIZE and INITRANS options after the hash cluster was created.
Action: Do not specify this option.
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.
Cause: A constant or system variable was specified in the hash expression.
Action: Recreate the cluster and correct the error in hash expression.
Cause: Result of evaluating hash expression is not an Oracle Number.
Action: Recreate the cluster and correct the error in hash expression.
Cause: An attempt was made to specify SYSDATE, UID, USER, ROWNUM, or LEVEL in hash expression.
Action: Re-create the cluster and correct the error in hash expression.
Cause: SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed in hash expressions.
Action: Recreate the cluster and remove the offending keywords.
Cause: A PL/SQL function was used in the hash expression.
Action: Recreate the cluster and remove the PL/SQL function.
Cause: An error occurred while evaluating the clusters hash expression.
Action: Correct the query and retry.
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.
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.
Cause: A parallel direct load is occurring to the specified table.
Action: Retry statement after load is complete.
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.
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
Cause: An invalid file name was specified to load data into.
Action: Specify a valid database file.
Cause: Too many processes specified than allowed per event.
Action: Enter fewer processes by using ranges or wildcards if possible.
Cause: Illegal event string
Action: Enter a legal event string
Cause: Illegal process string
Action: Enter a legal process string
Cause: Bad process or size in _trace_buffers INIT.ORA parameter.
Action: n/a
Cause: Bad syntax for _trace_options INIT.ORA parameter.
Action: n/a
Cause: Error occurred in creating/writing the file.
Action: Check file name and make sure it is constructed properly. Also, check permissions for directories.
Cause: Incompatible binary trace data was specified.
Action: Check the format of the input data.
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.
Cause: No value was specified for the RESIZE clause.
Action: Use correct syntax.
Cause: The keyword ON or OFF was not specified for the AUTOEXTEND clause.
Action: Use correct syntax.
Cause: No value was specified for the NEXT clause.
Action: Use correct syntax.
Cause: A non-integer value was used for the NEXT clause of the DATAFILE list.
Action: Use correct syntax.
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.
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.
Cause: An attempt was made to alter or drop an individual chunk tablespace which is part of a tablespace set.
Action: Use alter or drop only on the tablespace set.
Cause: In the CREATE TABLESPACE, the IN SHARD option was specified more than once.
Action: Remove all but one of the IN SHARD options.