ORACLE common error code processing
ORA-00903 invalid table name An attempt was made to create an index on a table that does not exist. Set the correct table name.
ORA-00904 invalid identifier An attempt was made to create an index on a column that does not exist. Check the column names in the table and determine which column names should be used.
ORA-01408 An attempt was made to create an index on an already indexed list, while a column set with the same order already exists. Make sure the columns are in the correct order. If the index already exists, you don't need to create it again.
ORA-00959 tablespace already exists An attempt was made to create an index in a non-existent tablespace. Use the DBA_TABLESPACES or USER_TABLESPACES view to find out the correct tablespace name.
ORA-01418 The specified index does not exist. An attempt was made to drop an index that does not exist. Check the ALL_INDEXES view to determine the actual name of the index to be dropped.
ORA-01631, ORA-01632 The maximum area code index expansion that can be achieved in the index exceeds the value set by maxextents, and the expansion operation will fail. At this time, you need to increase the index's maxextents setting value or use larger initial and next setting values to re-create the index.
ORA-01467 sort key too long The database will encounter problems with sort operations. These problems may be caused by sorting too many columns, or may be caused by using too many group functions, or they may be caused by errors in the operation of the ORACLE database itself. The ORDER BY clause should be used to reduce the number of columns because a sort operation is limited by the database block size. It should be noted that this error has nothing to do with sort_area_size.
ORA-01031 Insufficient permissions The permissions to create the index are incorrect. If you create an index in a schema other than your own, you need to make sure you have create any index permissions; if you create a function-based index, you need to make sure you have query rewrite permissions.
ORA-01654 cannot extend object "data in tablespace". An attempt was made to add additional extents to the listed index, and the operation failed. Possible reasons are:
- Free space in tablespace has been exhausted
- Not enough adjacent data files exist in the tablespace
- The value set by Pctincrease is incorrect.
Solutions include adding space to the table space or resetting the next parameter value for the index."
ORA-02243 The option to modify the index or modify the materialized view is invalid. The alter index command with a syntax error was used. Check the correctness of the command and correct it.
ORA-02429 cannot drop an index used to enforce a unique key/primary key constraint An attempt was made to drop an index used to enforce a primary key or unique key constraint on a table. The constraint needs to be dropped to allow the index to be dropped.
ORA-01452 cannot create unique index An attempt was made to create a unique index on a table where the rows in the index are not unique. This error may also occur when trying to recreate an UNUSABLE index and a failed data load operation creates duplicate keys.
ORA-0922 Missing or invalid option An attempt was made to create a view using invalid options. Check to ensure that the video's constraints have been defined correctly, including the use of the disable novalidate key.
ORA-0942 table or view does not exist Create a view on a table that does not exist. Check whether the syntax of the CREATE VIEW statement is correct.
ORA-1779 cannot modify a column mapped to a non-key reserved table. Trying to execute a DML statement on a view that is not reserved. Check the syntax of the statements used on the view to determine why no keys are retained. Check whether all tables in this view have primary keys. Rewrite and re-create the view, and then re-execute the DML statement.
ORA-2261 A unique key or primary key already exists in the table. A view constraint is to be created on the view, but a similar constraint already exists.
ORA-2443 cannot drop constraint - non-existent constraint An attempt was made to drop a non-existent constraint.
ORA-4031 View view_name is wrong. The view to be used is invalid. Recompile the view and use the show errors command to determine the cause of the problem. It may be that the table, procedure or function to be called by the view is missing.
ORA-00904 invalid identifier issued a statement that referenced a column that does not exist in the referencing object. For example: trying to create a cluster without a cluster key.
ORA-00906 Syntax error in statement using missing left bracket. Find the error, modify it and re-execute the statement.
ORA-00907 Missing closing bracket and syntax error in statement used. Find the error, modify it and re-execute the statement.
ORA-00941 Missing cluster name. Forgot to include the cluster name in the create cluster command.
ORA-00943 The cluster does not exist. Issue the alter cluster or drop cluster statement on a non-existent cluster.
ORA-00944 Insufficient number of columns in the cluster. Attempt to create and join the cluster. The table in , but the table does not contain a sufficient number of columns to match the cluster.
ORA-00945: The specified column does not exist in the cluster. An attempt was made to create a table that was added to the cluster, but the correct column was not specified in the cluster.
ORA-00951 To drop a non-empty cluster An attempt was made to drop a non-empty cluster. You should first delete the table added to the cluster, or use the including table clause to solve this problem.
ORA-00955 The name you want to use is being used by an existing object. The name you want to use already exists in the table space. Determine which object is using this name, and then determine whether the object or the table you created should be renamed.
ORA-00959 tablespace does not exist. An attempt was made to create an object in a non-existent tablespace. Check the table space name used in the CREATE statement, or create the table space.
ORA-01031 Insufficient Privileges There is insufficient privilege to perform the requested operation. The database administrator should use the GRANT command to grant appropriate permissions.
ORA-01447 ALTER TABLE command cannot be used for column operations in a cluster. The column specified in the ALTER TABLE MODIFY command is part of the cluster key. Modification of columns in the cluster key is not allowed.
ORA-01655 cannot extend cluster in tablespace The cluster does not have enough space in the listed tablespace to allocate to another extent. Allocate more space to the tablespace.
ORA-01656 Maximum area code in cluster reached The area code in the cluster has reached the maximum specified area code. Use the ALTER CLUSTER command to change the maximum area code allowed in the cluster storage parameters to a larger number.
ORA-01701 inappropriate cluster used An attempt was made to specify the name of a cluster in a statement where the cluster is not allowed. This statement needs to be modified to solve the problem.
ORA-01715 UNIQUE clause cannot be used in a clustered index. An attempt to use the UNIQUE clause to create a clustered index is not allowed.
ORA-01716 Adding table to cluster has column definitions incompatible with column definitions in the cluster An attempt was made to add a table to the cluster where the column data types of the table are not the same as the column data types of the cluster key. You can solve this problem by using different column data types, or by matching the data types.
ORA-01769 Multiple uses of CLUSTER option Description An attempt was made to specify two or more CLUSTER clauses when creating a table used to sum the cluster. Only one CLUSTER clause should be used.
ORA-01770 CLUSTER option not allowed in CREATE CLUSTER command An attempt was made to add a CLUSTER clause to the CREATE CLUSTER command. This clause should be deleted.
ORA-01771 Illegal option included in command using clustered table When using ALTER command or CREATE command on clustered table, an attempt was made to include one of the following options: intrans\maxtrans\pctfree\pctused\storage\
tablespace .These options are only allowed to be used in the ALTER command or CREATE command of the cluster, but not in the ALTER command or CREATE command of the table in the cluster.
ORA-01782 The UNRECOVERABLE clause cannot be specified for the cluster or for a table in the cluster. An attempt was made to create a cluster using the UNRECOVERABLE clause. This operation is not allowed.
ORA-01794 maximum number of cluster key columns is 32 The number of cluster key columns used to create the cluster exceeds 32. Clusters can only be created with a maximum of 32 columns of cluster keys.
ORA-02033 The cluster index created for the cluster already exists on the cluster. The index to be created already exists on the cluster.
ORA-2202 not allowed to add more tables to the cluster The number of tables added to the cluster exceeds 32. Use up to 32 tables in the cluster.
ORA-02227 invalid cluster name An invalid cluster name was included in the statement. A valid cluster name should be used.
ORA-02228 Multiple occurrences of SIZE clause in a statement containing two or more SIZE clauses. Only one SIZE clause should be used.
ORA-02229 invalid SIZE option value The specified SIZE value is invalid. The correct SIZE value should be used
ORA-03292 The table performing the truncation operation is part of the cluster The table you want to perform the truncation operation on is part of the cluster. This operation is not allowed. The TRUNCATE CLUSTER command should be used to solve this problem.
ORA-00955 The name you are trying to use is already in use by an existing object. The name you are trying to assign to the sequence is already in use by an object in the database namespace. You should make sure that the sequence does not already exist in the namespace.
ORA-04003 sequence parameter START WITH exceeds the maximum allowed size (28 bits) Choose to use a smaller START WITH parameter value.
ORA-08004 sequence number exceeds the value of MAXVALUE, and the sequence cannot be instantiated. All available sequence numbers in the given sequence have been used up. There are options to delete and recreate sequences. You can use the ALTER SEQUENCE command to increase the MAXVALUE setting for the sequence; or use ALTER SEQUENCE CYCLE to allow index cycles.
ORA-02287 Sequence numbers are not allowed at this location. An attempt was made to use a sequence in SQL at a location where sequences are not allowed. Check the SQL statement and find the illegal sequence number used in the statement.
ORA-01722 invalid number This error usually indicates that incorrect syntax was used in the CREATE SEQUENCE command. Check the command to make sure it is executed correctly.
ORA-01031 Insufficient permissions There are no permissions required to create the sequence. Ask the database administrator to grant the appropriate permissions and then perform the create operation again.
ORA-04014 Decreasing sequence of CYCLE type must specify the MINVALUE parameter to define a descending sequence, and define the type of the sequence as CYCLE type. The MINVALUE parameter needs to be added to specify when the sequence will loop.
ORA-04015 Increasing sequence of CYCLE type must specify the MAXVALUE parameter to define an increasing sequence, and define the type of the sequence as CYCLE type. You need to add the MAXVALE parameter to specify when the sequence will loop.