Release 8.1.5
A67785-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8i Error Messages Release 8.1.5 A67785-01 |
|
ORA-02100 PCC: out of memory (i.e., could not allocate)
Cause: SQLLIB was unable to allocate enough memory to execute the program.
Action: Allocate more memory to the user session and then rerun the program. If the error persists, call Oracle Customer Support for assistance.
ORA-02101 PCC: inconsistent cursor cache (uce/cuc mismatch)
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.
ORA-02102 PCC: inconsistent cursor cache (no cuc entry for this uce)
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.
ORA-02103 PCC: inconsistent cursor cache (out-of-range cuc ref)
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.
ORA-02104 PCC: inconsistent host cache (no cuc available)
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.
ORA-02105 PCC: inconsistent cursor cache (no cuc entry in cache)
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.
ORA-02106 PCC: inconsistent cursor cache (OraCursor nr is bad)
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.
ORA-02107 PCC: this pgm too old for run-time library: please re-PCC it
Cause: The program was precompiled by an older version of the Oracle Precompilers, which is incompatible with this release of SQLLIB.
Action: Precompile the program with a newer version of the Oracle Precompilers.
ORA-02108 PCC: invalid descriptor passed to run-time library
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.
ORA-02109 PCC: inconsistent host cache (out-of-range sit ref)
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.
ORA-02110 PCC: inconsistent host cache (invalid sqi type)
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.
ORA-02111 PCC: heap consistency error
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.
ORA-02112 PCC: SELECT..INTO returns too many rows
Cause: A SELECT...INTO statement returned more rows than can be stored in the host variable provided.
Action: There are three possible solutions:
ORA-02140 invalid tablespace name
Cause: An identifier does not follow ALTER TABLESPACE.
Action: Specify a tablespace name following ALTER TABLESPACE.
ORA-02141 invalid OFFLINE option
Cause: An option other than NORMAL or IMMEDIATE follows OFFLINE.
Action: The user must either specify no option following OFFLINE or one of the options NORMAL or IMMEDIATE.
ORA-02142 missing or invalid ALTER TABLESPACE option
Cause: A valid option is not present.
Action: Use one of the valid options: add, rename, default, online, offline, read only, read write, begin, and end.
ORA-02143 invalid STORAGE option
Cause: An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or PCTINCREASE was specified in the STORAGE clause.
Action: Specify only valid options.
ORA-02144 no option specified for ALTER CLUSTER
Cause: No ALTER CLUSTER options are specified.
Action: Specify one or more of the following options: PCTFREE, PCTUSED, SIZE, STORAGE.
ORA-02145 missing STORAGE option
Cause: No STORAGE options were specified following STORAGE (.
Action: Specify one or more STORAGE option between the parentheses.
ORA-02146 SHARED specified multiple times
Cause: The SHARED option was specified in a CREATE DATABASE statement multiple times.
Action: Only specify the SHARED option once.
ORA-02147 conflicting SHARED/EXCLUSIVE options
Cause: Both the SHARED and EXCLUSIVE options were specified in a CREATE DATABASE statement.
Action: Specify SHARED or EXCLUSIVE, but not both.
ORA-02148 EXCLUSIVE specified multiple times
Cause: The EXCLUSIVE option was specified in a CREATE DATABASE statement multiple times.
Action: Only specify the EXCLUSIVE option once.
ORA-02149 Specified partition does not exist
Cause: Partition not found for the object.
Action: Retry with correct partition name.
ORA-02153 invalid VALUES password string
Cause: An encoded password string does not follow the VALUES clause.
Action: Place a proper encoded password string after the VALUES clause.
ORA-02155 invalid DEFAULT tablespace identifier
Cause: An identifier does not follow DEFAULT TABLESPACE.
Action: Place a tablespace name after DEFAULT TABLESPACE.
ORA-02156 invalid TEMPORARY tablespace identifier
Cause: An identifier does not follow TEMPORARY TABLESPACE.
Action: Place a tablespace name after TEMPORARY TABLESPACE.
ORA-02157 no options specified for ALTER USER
Cause: No options were specified.
Action: Specify at least one ALTER USER option.
ORA-02158 invalid CREATE INDEX option
Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified.
Action: Choose one of the valid CREATE INDEX options.
ORA-02159 installed DLM does not support releasable locking mode
Cause: The parameter file specified GC_* parameters that allow locks to be release by the LCK process when not in use. This mode requires additional support from the DLM that is not available.
Action: Specify configuration parameters that do not require the additional function.
ORA-02160 index-organized table can not contain columns of type LONG
Cause: A column of type LONG defined for index-organized table.
Action: Do not use columns of type LONG in index-organized tables.
ORA-02161 invalid value for MAXLOGFILES
Cause: A number does not follow MAXLOGFILES.
Action: Specify a number after MAXLOGFILES.
ORA-02162 invalid value for MAXDATAFILES
Cause: A number does not follow MAXDATAFILES.
Action: Specify a number after MAXDATAFILES.
ORA-02163 invalid value for FREELIST GROUPS
Cause: A number does not follow FREELIST GROUPS.
Action: Specify a number after FREELIST GROUPS.
ORA-02164 DATAFILE clause specified more than once
Cause: The CREATE DATABASE command contains more than one DATAFILE clause.
Action: Specify at most one DATAFILE clause.
ORA-02165 invalid option for CREATE DATABASE
Cause: An invalid CREATE DATABASE option is present.
Action: Specify only valid CREATE DATABASE options.
ORA-02166 ARCHIVELOG and NOARCHIVELOG specified
Cause: Both ARCHIVELOG and NOARCHIVELOG are specified in a CREATE DATABASE statement.
Action: Specify at most one of these two options.
ORA-02167 LOGFILE clause specified more than once
Cause: The CREATE DATABASE command contains more than one LOGFILE clause.
Action: Specify at most one LOGFILE clause.
ORA-02168 invalid value for FREELISTS
Cause: A number does not follow FREELISTS.
Action: Specify a number after FREELISTS.
ORA-02169 FREELISTS storage option not allowed
Cause: An attempt was made to specify the FREELISTS storage option. This option may only be specified during create table or create index.
Action: Remove these options and retry the statement.
ORA-02170 FREELIST GROUPS storage option not allowed
Cause: An attempt was made to specify the FREELIST GROUPS storage option. This option may be specified only when using the CREATE TABLE command and when the ALLOW_FREELIST_GROUPS parameter is specified in the initialization parameter file.
Action: Retry the statement without the FREELIST GROUPS storage option or set the ALLOW_FREELIST_GROUPS parameter in the initialization parameter file.
ORA-02171 invalid value for MAXLOGHISTORY
Cause: A number does not follow MAXLOGHISTORY.
Action: Specify a number after MAXLOGHISTORY.
ORA-02172 The PUBLIC keyword is not appropriate for a disable thread
Cause: The PUBLIC keyword was specified for a disable.
Action: Remove the keyword and resubmit.
ORA-02173 invalid option for DROP TABLESPACE
Cause: Either a token other than INCLUDING was found following the tablespace name or some text was found following INCLUDING CONTENTS.
Action: Place nothing or only INCLUDING CONTENTS after the tablespace name.
ORA-02174 Missing required thread number
Cause: A thread number must be specified after THREAD keyword.
Action: Use correct syntax.
ORA-02175 invalid rollback segment name
Cause: In the CREATE or DROP ROLLBACK SEGMENT statements, an identifier was not found following ROLLBACK SEGMENT.
Action: Place the segment name following ROLLBACK SEGMENT.
ORA-02176 invalid option for CREATE ROLLBACK SEGMENT
Cause: An invalid option was specified in a CREATE ROLLBACK SEGMENT statement.
Action: Specify one of the valid options: TABLESPACE and STORAGE.
ORA-02177 Missing required group number
Cause: A group number must be specified after GROUP keyword.
Action: Check the syntax of the command, specify a group number after GROUP, and retry it.
ORA-02178 correct syntax is: SET TRANSACTION READ { ONLY | WRITE }
Cause: There is a syntax error in the user's statement.
Action: Correct the syntax as indicated.
ORA-02179 valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }
Cause: There is a syntax error in the user's statement.
Action: Correct the syntax as indicated.
ORA-02180 invalid option for CREATE TABLESPACE
Cause: An invalid option appears.
Action: Specify one of the valid options: DATAFILE, DEFAULT STORAGE, ONLINE, OFFLINE.
ORA-02181 invalid option to ROLLBACK WORK
Cause: A token other than TO follows ROLLBACK [WORK].
Action: Place nothing or TO SAVEPOINT name after ROLLBACK [WORK].
ORA-02182 savepoint name expected
Cause: An identifier does not follow ROLLBACK [WORK] TO [SAVEPOINT].
Action: Place a savepoint name following TO [SAVEPOINT].
ORA-02183 valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED }
Cause: There is a syntax error in the user's statement.
Action: Correct the syntax as indicated.
ORA-02184 resource quotas are not allowed in REVOKE
Cause: In a revoke statement, a resource quota was specified.
Action: Specify resource privilege without the quota.
ORA-02185 a token other than WORK follows COMMIT
Cause: A token other than WORK follows COMMIT.
Action: Place either nothing or WORK after COMMIT.
ORA-02186 tablespace resource privilege may not appear with other privileges
Cause: An attempt was made to grant or revoke a resource quota in the same statement in which other privileges are granted or revoked.
Action: Use a separate grant or revoke statement for the resource quota privilege.
ORA-02187 invalid quota specification
Cause: In a grant or revoke statement, an attempt was made to grant a tablespace quota above the upper limit.
Action: Grant a smaller tablespace quota.
ORA-02189 ON tablespace required
Cause: In a grant or revoke statement, the user specified a tablespace quota but did not follow it with the ON tablespace clause.
Action: Specify the tablespace on which the quota is to be applied with the ON tablespace clause.
ORA-02190 keyword TABLES expected
Cause: The keyword TABLES is expected following DROP CLUSTER name INCLUDING.
Action: Place TABLES after INCLUDING.
ORA-02191 correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT rbs
Cause: There is a syntax error in the user's statement.
Action: Correct the syntax as indicated.
ORA-02192 PCTINCREASE not allowed for rollback segment storage clauses
Cause: The storage parameter PCTINCREASE was specified in a CREATE or ALTER ROLLBACK SEGMENT command.
Action: Retry the command without the PCTINCREASE clause.
ORA-02194 event specification syntax error string (minor error string) near 'string'
Cause: There is a syntax error in an event specification.
Action: Check syntax and spelling and try again.
ORA-02195 Attempt to create string object in a string tablespace
Cause: The object type is inconsistent with a tablespace contents.
Action: Create an object in a different tablespace, or change the user defaults.
ORA-02196 PERMANENT/TEMPORARY option already specified
Cause: In CREATE TABLESPACE, the PERMANENT and/or TEMPORARY options were specified more than once.
Action: Specify at least one of REBUILD, INITRANS, MAXTRANS, or STORAGE.
For more information about the parameters of CREATE TABLESPACE, see Oracle8i SQL Reference.
ORA-02197 file list already specified
Cause: In CREATE TABLESPACE, more than one DATAFILE/TEMPFILE clause was specified.
Action: Merge the DATAFILE/TEMPFILE clauses into a single clause.
ORA-02198 ONLINE/OFFLINE option already specified
Cause: In CREATE TABLESPACE, the ONLINE and/or OFFLINE options were specified more than once.
Action: Specify at most one of ONLINE or OFFLINE.
ORA-02199 missing DATAFILE/TEMPFILE clause
Cause: A CREATE TABLESPACE statement has no DATAFILE/TEMPFILE clause.
Action: Specify a DATAFILE/TEMPFILE clause.
ORA-02200 WITH GRANT OPTION not allowed for PUBLIC
Cause: An attempt was made to GRANT to PUBLIC WITH GRANT OPTION.
Action: Remove the WITH GRANT OPTION clause.
ORA-02201 sequence not allowed here
Cause: An attempt was made to reference a sequence in a from-list.
Action: A sequence can only be referenced in a select-list.
ORA-02202 no more tables permitted in this cluster
Cause: An attempt was made to create a table in a cluster which already contains 32 tables.
Action: Up to 32 tables may be stored per cluster.
ORA-02203 INITIAL storage options not allowed
Cause: An attempt was made to alter the INITIAL storage option of a table, cluster, index, or rollback segment. These options may only be specified when the object is created.
Action: Remove these options and retry the statement.
ORA-02204 ALTER, INDEX, REFERENCE and EXECUTE not allowed for views
Cause: An attempt was made to grant or revoke an invalid privilege on a view.
Action: Do not attempt to grant or revoke any of ALTER, INDEX, or REFERENCES privileges on views.
ORA-02205 only SELECT and ALTER privileges are valid for sequences
Cause: An attempt was made to grant or revoke an invalid privilege on a sequence.
Action: Do not attempt to grant or revoke DELETE, INDEX, INSERT, UPDATE, REFERENCES or EXECUTE privilege on sequences.
ORA-02206 duplicate INITRANS option specification
Cause: INITRANS is specified more than once.
Action: Specify INITRANS at most once.
ORA-02207 invalid INITRANS option value
Cause: The INITRANS value is not an integer between 1 and 255 and less than or equal to the MAXTRANS value.
Action: Choose a valid INITRANS value.
ORA-02208 duplicate MAXTRANS option specification
Cause: MAXTRANS is specified more than once.
Action: Specify MAXTRANS at most once.
ORA-02209 invalid MAXTRANS option value
Cause: The MAXTRANS value is not an integer between 1 and 255 and greater than or equal to the INITRANS value.
Action: Choose a valid MAXTRANS value.
ORA-02210 no options specified for ALTER TABLE
Cause: No ALTER TABLE option was specified.
Action: Specify at least one alter table option.
ORA-02211 invalid value for PCTFREE or PCTUSED
Cause: The specified value for PCTFREE or PCTUSED is not an integer between 0 and 100.
Action: Choose an appropriate value for the option.
ORA-02212 duplicate PCTFREE option specification
Cause: PCTFREE option specified more than once.
Action: Specify PCTFREE at most once.
ORA-02213 duplicate PCTUSED option specification
Cause: PCTUSED option specified more than once.
Action: Specify PCTUSED at most once.
ORA-02214 duplicate BACKUP option specification
Cause: The BACKUP option to ALTER TABLE is specified more than once.
Action: Specify the option at most once.
ORA-02215 duplicate tablespace name clause
Cause: There is more than one TABLESPACE clause in the CREATE TABLE, CREATE INDEX, or CREATE ROLLBACK SEGMENT statement.
Action: Specify at most one TABLESPACE clause.
ORA-02216 tablespace name expected
Cause: A tablespace name is not present where required by the syntax for one of the following statements: CREATE/DROP TABLESPACE, CREATE TABLE, CREATE INDEX, or CREATE ROLLBACK SEGMENT.
Action: Specify a tablespace name where required by the syntax.
ORA-02217 duplicate storage option specification
Cause: A storage option (INIITAL, NEXT, MINEXTENTS, MAXEXTENTS, PCTINCREASE) is specified more than once.
Action: Specify all storage options at most once.
ORA-02218 invalid INITIAL storage option value
Cause: The specified value must be an integer.
Action: Choose an appropriate integer value.
ORA-02219 invalid NEXT storage option value
Cause: The specified value must be an integer.
Action: Choose an appropriate integer value.
ORA-02220 invalid MINEXTENTS storage option value
Cause: The specified value must be a positive integer less than or equal to MAXEXTENTS.
Action: Specify an appropriate value.
ORA-02221 invalid MAXEXTENTS storage option value
Cause: The specified value must be a positive integer greater than or equal to MINEXTENTS.
Action: Specify an appropriate value.
ORA-02222 invalid PCTINCREASE storage option value
Cause: The specified value must be a positive integer.
Action: Specify an appropriate value.
ORA-02223 invalid OPTIMAL storage option value
Cause: The specified value must be an integer.
Action: Choose an appropriate integer value.
ORA-02224 EXECUTE privilege not allowed for tables
Cause: An attempt was made to grant or revoke an invalid privilege on a table.
Action: Do not attempt to grant or revoke EXECUTE privilege on tables.
ORA-02225 only EXECUTE privilege is valid for procedures
Cause: An attempt was made to grant or revoke an invalid privilege on a procedure, function or package.
Action: Do not attempt to grant or revoke any privilege besides EXECUTE on procedures, functions or packages.
ORA-02226 invalid MAXEXTENTS value (max allowed: string)
Cause: The MAXEXTENTS specified is too large for the database block size. This applies only to SYSTEM rollback segment.
Action: Specify a smaller value.
ORA-02227 invalid cluster name
Cause: A cluster name was not properly formed.
Action: Check the rules for forming object names and enter an appropriate cluster name.
ORA-02228 duplicate SIZE specification
Cause: The SIZE option is specified more than once.
Action: Specify the SIZE option at most once.
ORA-02229 invalid SIZE option value
Cause: The specified value must be an integer number of bytes.
Action: Specify an appropriate value.
ORA-02230 invalid ALTER CLUSTER option
Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or SIZE is specified in an ALTER CLUSTER statement.
Action: Specify only legal options.
ORA-02231 missing or invalid option to ALTER DATABASE
Cause: An option other than ADD, DROP, RENAME, ARCHIVELOG, NOARCHIVELOG, MOUNT, DISMOUNT, OPEN, or CLOSE is specified in the statement.
Action: Specify only legal options.
ORA-02232 invalid MOUNT mode
Cause: A mode other than SHARED or EXCLUSIVE follows the MOUNT keyword in an ALTER DATABASE statement.
Action: Specify either SHARED, EXCLUSIVE, or nothing following MOUNT.
ORA-02233 invalid CLOSE mode
Cause: A mode other than NORMAL or IMMEDIATE follows the CLOSE keyword in an ALTER DATABASE statement.
Action: Specify either NORMAL, IMMEDIATE, or nothing following CLOSE.
ORA-02234 changes to this table are already logged
Cause: The log table to be added is a duplicate of another.
Action: Do not add this change log to the system; check that the replication product's system tables are consistent.
ORA-02235 this table logs changes to another table already
Cause: The table to be altered is already a change log for another table.
Action: Do not log changes to the specified base table to this table; check that the replication product's system tables are consistent.
ORA-02236 invalid file name
Cause: A character string literal was not used in the file name list of a LOGFILE, DATAFILE, or RENAME clause.
Action: Use correct syntax.
ORA-02237 invalid file size
Cause: A non-integer value was specified in the SIZE or RESIZE clause.
Action: Use correct syntax.
ORA-02238 filename lists have different numbers of files
Cause: In a RENAME clause in ALTER DATABASE or TABLESPACE, the number of existing file names does not equal the number of new file names.
Action: Make sure there is a new file name to correspond to each existing file name.
ORA-02239 there are objects which reference this sequence
Cause: The sequence to be dropped is still referenced by other objects.
Action: Make sure the sequence name is correct or drop the constraint or object that references the sequence.
ORA-02240 invalid value for OBJNO or TABNO
Cause: A number does not follow either OBJNO or TABNO.
Action: Specify a number after OBJNO or TABNO.
ORA-02241 must of form EXTENTS (FILE n BLOCK n SIZE n, ...)
Cause: There was an error in the extent storage clause.
Action: Respecify the storage clause using the correct syntax and retry the command.
ORA-02242 no options specified for ALTER INDEX
Cause: No options specified.
Action: Specify at least one of REBUILD, INITRANS, MAXTRANS, or STORAGE.
ORA-02243 invalid ALTER INDEX or ALTER SNAPSHOT option
Cause: An option other than INITRANS, MAXTRANS, or STORAGE is specified in an ALTER INDEX statement or in the USING INDEX clause of an ALTER SNAPSHOT statement.
Action: Specify only legal options.
ORA-02244 invalid ALTER ROLLBACK SEGMENT option
Cause: The STORAGE option is expected but not found.
Action: Specify the STORAGE option.
ORA-02245 invalid ROLLBACK SEGMENT name
Cause: An identifier was expected, but not found, following ALTER [PUBLIC] ROLLBACK SEGMENT.
Action: Place a rollback segment name following SEGMENT.
ORA-02246 missing EVENTS text
Cause: A character string literal was expected, but not found, following ALTER SESSION SET EVENTS.
Action: Place the string literal containing the events text after EVENTS.
ORA-02247 no option specified for ALTER SESSION
Cause: The option SET EVENTS was expected, but not found, following ALTER SESSION.
Action: Place the SET EVENTS option after ALTER SESSION.
ORA-02248 invalid option for ALTER SESSION
Cause: An option other than SET EVENTS was found following the ALTER SESSION command.
Action: Specify the SET EVENTS option after the ALTER SESSION command and try again.
ORA-02249 missing or invalid value for MAXLOGMEMBERS
Cause: A valid number does not follow MAXLOGMEMBERS. The value specified must be between 1 and the port-specific maximum number of log file members.
Action: Specify a valid number after MAXLOGMEMBERS.
ORA-02250 missing or invalid constraint name
Cause: The constraint name is missing or invalid.
Action: Specify a valid identifier name for the constraint name.
ORA-02251 subquery not allowed here
Cause: Subquery is not allowed here in the statement.
Action: Remove the subquery from the statement.
ORA-02252 check constraint condition not properly ended
Cause: The specified search condition for the check constraint is not properly ended.
Action: End the condition properly.
ORA-02253 constraint specification not allowed here
Cause: Constraint specification is not allowed here in the statement.
Action: Remove the constraint specification from the statement.
ORA-02254 DEFAULT expression not allowed here
Cause: Default value expression is not allowed for the column here in the statement.
Action: Remove the default value expression from the statement.
ORA-02255: NOT NULL not allowed after DEFAULT NULL
Cause: A NOT NULL specification conflicts with the NULL default value.
Action: Remove either the NOT NULL or the DEFAULT NULL specification and try again.
ORA-02256 number of referencing columns must match referenced columns
Cause: The number of columns in the foreign-key referencing list is not equal to the number of columns in the referenced list.
Action: Make sure that the referencing columns match the referenced columns.
ORA-02257 maximum number of columns exceeded
Cause: The number of columns in the key list exceeds the maximum number.
Action: Reduce the number columns in the list.
ORA-02258 duplicate or conflicting NULL and/or NOT NULL specifications
Cause: A duplicate or conflicting NULL and/or NOT NULL was specified.
Action: Remove one of the conflicting specifications and try again.
ORA-02259 duplicate UNIQUE/PRIMARY KEY specifications
Cause: A duplicate unique or primary key was specified.
Action: Remove the duplicate specification and try again.
ORA-02260 table can have only one primary key
Cause: Two or more primary keys were specified for the same table.
Action: Remove the extra primary keys and try again.
ORA-02261 such unique or primary key already exists in the table
Cause: A unique or primary key was specified that already exists for the table.
Action: Remove the extra key and try again.
ORA-02262 ORA-nnnnn occurs while type-checking column default value expression
Cause: New column datatype causes type-checking error for existing column default value expression.
Action: Remove the default value expression or do not alter the column datatype.
ORA-02263 need to specify the datatype for this column
Cause: The required datatype for the column is missing.
Action: Specify the required datatype.
ORA-02264 name already used by an existing constraint
Cause: The specified constraint name has to be unique.
Action: Specify a unique constraint name for the constraint.
ORA-02265 cannot derive the datatype of the referencing column
Cause: The datatype of the referenced column is not defined as yet.
Action: Make sure that the datatype of the referenced column is defined before referencing it.
ORA-02266 unique/primary keys in table referenced by enabled foreign keys
Cause: An attempt was made to drop or truncate a table with unique or primary keys referenced by foreign keys enabled in another table.
Action: Before dropping or truncating the table, disable the foreign key constraints in other tables. You can see what constraints are referencing a table by issuing the following command:
select constraint_name, table_name, status from user_constraints where r_constraint_name in ( select constraint_name from user_constraints where table_name ='tabnam');
ORA-02267 column type incompatible with referenced column type
Cause: The datatype of the referencing column is incompatible with the datatype of the referenced column.
Action: Select a compatible datatype for the referencing column.
ORA-02268 referenced table does not have a primary key
Cause: The referenced table does not have a primary key.
Action: Specify explicitly the referenced table unique key.
ORA-02269 key column cannot be of LONG datatype
Cause: An attempt was made to define a key column of datatype LONG. This is not allowed.
Action: Change the datatype of the column or remove the LONG column from the key, and try again.
ORA-02270 no matching unique or primary key for this column-list
Cause: An attempt was made to reference a unique or primary key in a table with a CREATE or ALTER TABLE statement when no such key exists in the referenced table.
Action: Add the unique or primary key to the table or find the correct names of the columns with the primary or unique key, and try again.
ORA-02271 table does not have such constraint
Cause: An attempt was made to reference a table using a constraint that does not exist.
Action: Check the spelling of the constraint name or add the constraint to the table, and try again.
ORA-02272 constrained column cannot be of LONG datatype
Cause: A constrained column cannot be defined as datatype LONG. This is not allowed.
Action: Change the datatype of the column or remove the constraint on the column, and try again.
ORA-02273 this unique/primary key is referenced by some foreign keys
Cause: A unique or primary key referenced by foreign keys cannot be dropped.
Action: Remove all references to the key before dropping it.
ORA-02274 duplicate referential constraint specifications
Cause: A referential constraint was specified more than once. This is not allowed.
Action: Remove the duplicate specification.
ORA-02275 such a referential constraint already exists in the table
Cause: An attempt was made to specify a referential constraint that already exists. This would result in duplicate specifications and so is not allowed.
Action: Be sure to specify a constraint only once.
ORA-02276 default value type incompatible with column type
Cause: The type of the evaluated default expression is incompatible with the datatype of the column.
Action: Change the type of the column, or modify the default expression.
ORA-02277 invalid sequence name
Cause: The specified sequence name is not a valid identifier name.
Action: Specify a valid identifier name for the sequence name.
ORA-02278 duplicate or conflicting MAXVALUE/NOMAXVALUE specifications
Cause: Duplicate or conflicting MAXVALUE and/or NOMAXVALUE specifications.
Action: Remove one of the conflicting specifications and try again.
ORA-02279 duplicate or conflicting MINVALUE/NOMINVALUE specifications
Cause: Duplicate or conflicting MINVALUE and/or NOMINVALUE clauses were specified.
Action: Remove one of the conflicting specifications and try again.
ORA-02280 duplicate or conflicting CYCLE/NOCYCLE specifications
Cause: Duplicate or conflicting CYCLE and/or NOCYCLE clauses were specified.
Action: Remove one of the conflicting specifications and try again.
ORA-02281 duplicate or conflicting CACHE/NOCACHE specifications
Cause: Duplicate or conflicting CACHE and/or NOCACHE clauses were specified.
Action: Remove one of the conflicting specifications and try again.
ORA-02282 duplicate or conflicting ORDER/NOORDER specifications
Cause: Duplicate or conflicting ORDER and/or NOORDER clauses were specified.
Action: Remove one of the conflicting specifications and try again.
ORA-02283 cannot alter starting sequence number
Cause: An attempt was made to alter a starting sequence number. This is not allowed.
Action: Do not try to alter a starting sequence number.
ORA-02284 duplicate INCREMENT BY specifications
Cause: A duplicate INCREMENT BY clause was specified.
Action: Remove the duplicate specification and try again.
ORA-02285 duplicate START WITH specifications
Cause: A duplicate START WITH clause was specified.
Action: Remove the duplicate specification and try again.
ORA-02286 no options specified for ALTER SEQUENCE
Cause: No ALTER SEQUENCE option was specified.
Action: Check the syntax. Then specify at least one ALTER SEQUENCE option.
ORA-02287 sequence number not allowed here
Cause: The specified sequence number reference, CURRVAL or NEXTVAL, is inappropriate at this point in the statement.
Action: Check the syntax. Then remove or relocate the sequence number.
ORA-02288 invalid OPEN mode
Cause: A mode other than RESETLOGS was specified in an ALTER DATABASE OPEN statement. RESETLOGS is the only valid OPEN mode.
Action: Remove the invalid mode from the statement or replace it with the keyword RESETLOGS, and try again.
ORA-02289 sequence does not exist
Cause: The specified sequence does not exist, or the user does not have the required privilege to perform this operation.
Action: Make sure the sequence name is correct, and that you have the right to perform the desired operation on this sequence.
ORA-02290 check constraint (string.string) violated
Cause: The value or values attempted to be entered in a field or fields violate a defined check constraint.
Action: Enter values that satisfy the constraint.
ORA-02291 integrity constraint (string.string) violated - parent key not found
Cause: A foreign key value has no matching primary key value.
Action: Delete the foreign key or add a matching primary key.
ORA-02292 integrity constraint (string.string) violated - child record found
Cause: An attempt was made to delete a row that is referenced by a foreign key.
Action: It is necessary to DELETE or UPDATE the foreign key before changing this row.
ORA-02293 cannot validate (string.string) - check constraint violated
Cause: An attempt was made via an ALTERTABLE statement to add a check constraint to a populated table that had no complying values.
Action: Retry the ALTER TABLE statement, specifying a check constraint on a table containing complying values. For more information about ALTER TABLE, see Oracle8i SQL Reference.
ORA-02294 cannot enable (string.string) - constraint changed during validation
Cause: While one DDL statement was attempting to enable this constraint, another DDL changed this same constraint.
Action: Try again, with only one DDL changing the constraint this time.
ORA-02295 found more than one enable/disable clause for constraint
Cause: An attempt was made via a CREATE or ALTER TABLE statement to specify more than one ENABLE and/or DISABLE clause for a given constraint.
Action: Only one ENABLE or DISABLE clause may be specified for a given constraint.
ORA-02296 cannot enable (string.string) - null values found
Cause: An ALTER TABLE command with an ENABLE CONSTRAINT clause failed because the table contains values that do not satisfy the constraint.
Action: Make sure that all values in the table satisfy the constraint before issuing an ALTER TABLE command with an ENABLE CONSTRAINT clause. For more information about ALTER TABLE and ENABLE CONSTRAINT, see Oracle8i SQL Reference.
ORA-02297 cannot disable constraint (string.string) - dependencies exist
Cause: An alter table disable constraint failed because the table has foreign keys that are dependent on the constraint.
Action: Either disable the foreign key constraints or use a DISABLE CASCADE command.
ORA-02298 cannot validate (string.string) - parent keys not found
Cause: An ALTER TABLE ENABLE CONSTRAINT command failed because the table has orphaned child records.
Action: Make sure that the table has no orphaned child records before issuing an ALTER TABLE ENABLE CONSTRAINT command. For more information about ALTER TABLE and ENABLE CONSTRAINT, see Oracle8i SQL Reference.
ORA-02299 cannot validate (string.string) - duplicate keys found
Cause: An ALTER TABLE ENABLE CONSTRAINT command failed because the table has duplicate key values.
Action: Make sure that the table has no duplicate key values before issuing an ALTER TABLE ENABLE CONSTRAINT command. For more information about ALTER TABLE and ENABLE CONSTRAINT, see Oracle8i SQL Reference.
ORA-02300 invalid value for OIDGENERATORS
Cause: A number was not specified for the value of OIDGENERATORS.
Action: Specify a number for OIDGENERATORS.
ORA-02301 maximum number of OIDGENERATORS is 255
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.
ORA-02302 invalid or missing type name
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.
ORA-02303 cannot drop or replace a type with type or table dependents
Cause: An attempt was made to drop or replace a type that has dependents.
Action: Drop all type(s) and table(s) depending on the type, then retry the operation, or use the FORCE option.
ORA-02304 invalid object identifier literal
Cause: An attempt was made to enter an object identifier literal for CREATE TYPE that is either:
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.
ORA-02305 only EXECUTE privilege is valid for types
Cause: An attempt was made to GRANT or REVOKE an invalid privilege (not EXECUTE) on a type.
Action: GRANT or REVOKE only the EXECUTE privilege on types.
ORA-02306 cannot create a type that already has valid dependent(s)
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.
ORA-02307 cannot alter with REPLACE option a type that is not valid
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.
ORA-02308 invalid option string for object type column
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.
ORA-02309 atomic NULL violation
Cause: An attempt was made to access the attributes of a NULL object instance.
Action: Ensure that the object instance is non-NULL before accessing.
ORA-02310 exceeded maximum number of allowable columns in table
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.
ORA-02311 cannot alter with COMPILE option a valid type with type or table dependents
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.
ORA-02312 cannot create extent table for VALUE ADT
Cause: An attempt was made to create extent table for VALUE Object Type.
Action: Specify object type when creating extent table.
ORA-02313 object type contains non-queryable type string attribute
Cause: The specified object type contains a nested attribute whose type is non-queryable.
Action: Use an object type with queryable attribute types.
ORA-02314 cannot create index on object type column or attribute
Cause: An attempt was made to create an index on an object type column.
Action: index can only be created on simple, scalar columns or attributes.
ORA-02315 incorrect number of arguments for default constructor
Cause: The number of arguments specified for the default constructor does not match the number of attributes of the object type.
Action: Specify the correct number of arguments for the default constructor and retry the operation.
ORA-02316 incorrect number of attributes in object type column
Cause: The number of attributes in object type operand does not match number of attributes in object type column to be updated.
Action: Make sure both object type attributes match.
ORA-02317 invalid operation for object type operands
Cause: An invalid operation on object type operands was specified.
Action: Make sure the correct operation is requested to be performed on object type operands.
ORA-02318 invalid REF function on non-object table
Cause: An invalid REF operator was specified for a non-object table. REF operator can only be specified on an object table.
Action: Do not specify a REF operator on a non-object table.
ORA-02319 invalid column argument to REF operator
Cause: An invalid REF column argument was specified. The argument to a REF operator can only be the object type column of the object table.
Action: Specify a valid REF column argument.
ORA-02320 failure in creating storage table for nested table column string
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 Customer Support.
ORA-02321 object type's default constructor expected
Cause: The expected constructor was not found.
Action: Specify an ADT default constructor.
ORA-02322 failure in accessing storage table of the nested table column
Cause: An error occurred 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 Customer Support.
ORA-02323 fail in string inner table for column string
Cause: An error occurred while performing DML on the nested table column.
Action: If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Customer Support.
ORA-02324 more than one column in the SELECT list of THE subquery
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.
ORA-02325 zero rows returned by THE subquery
Cause: THE subquery evaluation returns no rows whereas it is supposed to return a single row.
Action: Change the subquery within THE operator to return exactly one row.
ORA-02326 missing THE keyword
Cause: Subquery used to return an inner nested table is enclosed by THE operator.
Action: Put THE operator around the subquery; for example, THE(subquery).
ORA-02327 cannot create index on expression with datatype string
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.
ORA-02328 REF column cannot be specified on VALUE ADT
Cause: An attempt was made to create a REF column of VALUE ADT.
Action: Remove the REF specifier from the column specification.
ORA-02329 column of datatype string cannot be unique or a primary key
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.
ORA-02330 datatype specification not allowed
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.
ORA-02331 cannot create constraint on column of datatype string
Cause: An attempt was made to create a constraint on a column possessing a non-constrainable datatype: VARRAY, nested table, object, LOB, FILE, or REF.
Action: Change the column datatype, or remove the constraint.
ORA-02332 cannot create index on attributes of this column
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.
ORA-02333 cannot create constraints on attributes of this column
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.
ORA-02334 cannot infer type for column
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.
ORA-02335 invalid datatype for cluster 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.
ORA-02336 column attribute cannot be accessed
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.
ORA-02337 not an object type column
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.
ORA-02338 missing or invalid column constraint specification
Cause: A column constraint was not specified.
Action: Remove the column specification or specify a column constraint. Then retry the operation.
ORA-02339 invalid column specification
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.
ORA-02340 invalid column specification
Cause: An attempt was made to specify an UNPACKED column within a packed table.
Action: Remove the UNPACKED keyword in the column specification.
ORA-02341 cannot refer to non-queryable type string in SQL
Cause: Attempt to refer to an object type attribute that is of a non-queryable type in SQL.
Action: Change attribute type to a SQL-queryable type, or reference the attribute through a 3GL.
ORA-02342 replacement type has compilation errors
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.
ORA-02344 cannot revoke execute on a type with table dependents
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.
ORA-02345 cannot create a view with column based on CURSOR operator
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.
ORA-02347 cannot grant privileges on columns of an object table
Cause: An attempt was made to grant privileges on the columns of an object table.
Action: Choose another table. Privileges cannot be granted on columns of an object table.
ORA-02348 invalid attribute type
Cause: Object type columns cannot have attributes of type LOB or nested table.
Action: Remove the invalid attribute from the type.
ORA-02349 invalid user-defined type - type is incomplete
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.
ORA-02350 cannot insert into attributes of a packed typed table
Cause: A column list was specified in an INSERT statement.
Action: Drop the column list specification statement.
ORA-02351 Record string: Rejected - Error on table string, column string
Cause: The record indicated caused an Oracle error on insert.
Action: Determine the Oracle error and correct the record.
ORA-02352 Direct path connection must be homogeneous
Cause: The user-side to kernel-side connection is heterogeneous.
Action: Make the connection between identical hardware and operating systems.
ORA-02353 Multibyte character error
Cause: Text specified by POSITION or terminated by newlines is invalid.
Action: Edit the control file or the datafile to fix alignment of column.
ORA-02354 Conversion initialization error occurred on field string
Cause: An error occurred during conversion initialization for a field. This is an internal error.
Action: Contact customer support.
ORA-02355 Conversion error occurred on CONSTANT field string
Cause: A CONSTANT field caused an Oracle error; all rows will be rejected.
Action: Determine the Oracle error and correct the record.
ORA-02356 The database is out of space. The load cannot continue
Cause: The load was discontinued due to space exhaustion in the database.
Action: Add space for the specified table.
ORA-02357 Packed Decimal conversion error
Cause: The column could not be converted from packed decimal to character.
Action: Check the column and make it conform to packed decimal format.
ORA-02358 Zoned Decimal conversion error
Cause: The column could not be converted from packed decimal to character.
Action: Check the column and make it conform to packed decimal format.
ORA-02359 Field in data file exceeded maximum specified length
Cause: The field is too long for the specified column.
Action: Shorten the field so that its length is less than or equal to the column length.
ORA-02360 Column not found before end of logical record (use TRAILING NULLCOLS)
Cause: A column started after the end of the logical record had been reached.
Action: Use the TRAILING NULLCOLS option or supply data for the column.
ORA-02361 Initial enclosing character not found
Cause: The initial enclosing character of an enclosed field was not found.
Action: Supply the character before the start of the field.
ORA-02362 Logical record ended - second enclosing character not present
Cause: The second enclosing character of an enclosed field was not found.
Action: Supply the character after the end of the field.
ORA-02363 No terminator found after TERMINATED and ENCLOSED field
Cause: No terminator was found after a terminated and enclosed field.
Action: Supply the character after the end of the field.
ORA-02364 Record string: Discarded - failed all WHEN clauses
Cause: The record was not loaded because it failed the WHEN clauses of all the tables.
Action: No action required.
ORA-02365 Index string was made Index Unusable due to
Cause: The index was not loaded. The cause of the error is stated after the message.
Action: Correct the cause of the error, then reload.
ORA-02366 The following index(es) on table string were processed:
Cause: The indexes listed for the named table were loaded.
Action: No action required.
ORA-02367 Index string was loaded.
Cause: The index specified in the message was loaded.
Action: No action required.
ORA-02368 Record string: Discarded - all columns null.
Cause: The record was not loaded because all of the columns in the table were null for that record.
Action: No action required.
ORA-02369 Warning: Variable length field was truncated.
Cause: A variable length field was truncated by the end of the logical record.
Action: This is just a warning, but since a variable length field has the length embedded in the data for each row, you may want to check your data.
ORA-02370 Record string - Warning on table string, column string
Cause: The record indicated caused an warning.
Action: Determine the warning and correct the record if necessary.
ORA-02371 Loader must be at least version string.string.string.string.string for direct path
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.
ORA-02372 Relative start position > absolute field end position.
Cause: A field specified as POSITION(*+n:y) had its relative start occur after the absolute position y.
Action: Check that you are not missing a delimiter and that the values of n and y are correct.
ORA-02373 Error parsing insert statement for table string.
Cause: A parsing error occurred.
Action: Check the message following this parsing error message.
ORA-02374 No more slots for read buffer queue.
Cause: There are no free read buffers.
Action: Use the READBUFFERS keyword in the loader to increase the number of read buffers.
ORA-02375 Record string: Rejected - Error on table string
Cause: The record indicated caused an Oracle error on insert.
Action: Determine the Oracle error and correct the record. The offending column(s) are not known.
ORA-02376 invalid or redundant resource
Cause: A resource that is not defined or that is specified twice appears in the CREATE or ALTER PROFILE statement.
Action: Define the resource before issuing a CREATE or ALTER PROFILE command. Also check the statement to see that each resource is listed only once.
ORA-02377 invalid resource limit
Cause: An invalid resource limit of 0 was specified.
Action: Specify a resource limit greater than 0.
ORA-02378 duplicate resource name string
Cause: The same resource was specified twice in a CREATE or ALTER PROFILE statement.
Action: Issue the statement again, carefully checking that each resource is used only once.
ORA-02379 profile string already exists
Cause: An attempt was made to create a profile that already exists.
Action: Create the profile with a name not already used by another profile.
ORA-02380 profile string does not exist
Cause: An attempt was made to assign a user to a non-existent profile.
Action: Assign the user to an existing profile.
ORA-02381 cannot drop PUBLIC_DEFAULT profile
Cause: An attempt was made to drop the PUBLIC_DEFAULT profile.
Action: The PUBLIC_DEFAULT profile cannot be dropped.
ORA-02382 profile string has users assigned, cannot drop without CASCADE
Cause: An attempt was made to drop a profile that had users assigned to it without using the CASCADE option of the DROP PROFILE statement. A profile that has users assigned to it cannot be dropped, unless the CASCADE option is specified. CASCADE reassigns users to the PUBLIC_DEFAULT profile before dropping the profile.
Action: To reassign all users to the PUBLIC_DEFAULT profile, issue the DROP PROFILE statement with the CASCADE option.
ORA-02383 illegal cost factor
Cause: A negative value or UNLIMITED cost was specified for this resource in the ALTER RESOURCE COST statement.
Action: Only positive integer values can be specified for resources in the ALTER RESOURCE COST statement. Issue the statement again, using a positive integer value for each resource specified.
ORA-02390 exceeded COMPOSITE_LIMIT, you are being logged off
Cause: The COMPOSITE_LIMIT for the profile is exceeded. That is, the weighted sum of the connection time, logical reads per session, CPU usage per session, and private SGA space used during the session exceeded the limit set by the COMPOSITE_LIMIT clause set in the user profile.
Action: If this happens often, ask the database administrator to raise the COMPOSITE_LIMIT of the user profile, or determine which resource is used the most and raise the limit on that resource.
ORA-02391 exceeded simultaneous SESSIONS_PER_USER limit
Cause: An attempt was made to exceed the maximum number of concurrent sessions allowed by the SESSIONS_PER_USER clause of the user profile.
Action: End one or more concurrent sessions or ask the database administrator to increase the SESSIONS_PER_USER limit of the user profile. For more information about SESSIONS_PER_USER and the database administrator's specific tasks of adjusting concurrent sessions, see Oracle8i SQL Reference and the Oracle8i Administrator's Guide
ORA-02392 exceeded session limit on CPU usage, you are being logged off
Cause: An attempt was made to exceed the maximum CPU usage allowed by the CPU_PER_SESSION clause of the user profile.
Action: If this happens often, ask the database administrator to increase the CPU_PER_SESSION limit of the user profile.
ORA-02393 exceeded call limit on CPU usage
Cause: An attempt was made to exceed the maximum CPU time for a call, a parse, execute, or fetch, allowed by the CPU_PER_CALL clause of the user profile.
Action: If this happens often, ask the database administrator to increase the CPU_PER_CALL limit of the user profile.
ORA-02394 exceeded session limit on IO usage, you are being logged off
Cause: An attempt was made to exceed the maximum I/O allowed by the LOGICAL_READS_PER_SESSION clause of the user profile.
Action: If this happens often, ask the database administrator to increase the LOGICAL_READS_PER_SESSION limit of the user profile.
ORA-02395 exceeded call limit on IO usage
Cause: An attempt was made to exceed the maximum I/O for a call, a parse, execute, or fetch, allowed by the LOGICAL_READS_PER_CALL clause of the user profile.
Action: If this happens often, ask the database administrator to increase the LOGICAL_READS_PER_CALL limit of the user profile.
ORA-02396 exceeded maximum idle time, please connect again
Cause: A user has exceeded the maximum time allowed to remain idle.
Action: The user must reconnect to the database.
ORA-02397 exceeded PRIVATE_SGA limit, you are being logged off
Cause: This error occurs only when using a multi-threaded server.
Action: Contact the database administrator to expand the PRIVATE_SGA limit.
ORA-02398 exceeded procedure space usage
Cause: Stored procedures used up too much space in the SYSTEM tablespace.
Action: Use fewer stored procedures or add an additional file to the system tablespace.
ORA-02399 exceeded maximum connect time, you are being logged off
Cause: A user has exceeded the maximum time allowed to be connected to the database.
Action: The user must reconnect to the database.
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-02420 missing schema authorization clause
Cause: The AUTHORIZATION clause is missing from a create schema statement.
Action: Proceed the schema authorization identifier with the AUTHORIZATION keyword.
ORA-02421 missing or invalid schema authorization identifier
Cause: One of the following:
Action: If the cause is
ORA-02422 missing or invalid schema element
Cause: A statement other than a CREATE TABLE, CREATE VIEW, or GRANT appears in a CREATE SCHEMA statement.
Action: See Oracle8i SQL Reference or the valid elements of the CREATE SCHEMA statement.
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: Check that the schema names match the one given in the CREATE SCHEMA statement.
ORA-02424 potential circular view references or unknown referenced tables
Cause: The CREATE SCHEMA statement contains a view that depends on other views contained in the CREATE SCHEMA statement, or they contain references to non-existing tables.
Action: Create the dependent views in a separate CREATE SCHEMA statement and ensure that 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 message. Follow the appropriate actions as suggested by the subsequent messages.
ORA-02426 privilege grant failed
Cause: A GRANT statement failed in the CREATE SCHEMA statement.
Action: The cause for failure will be presented below this message. Follow appropriate actions, as suggested by the subsequent messages.
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 message. Follow appropriate actions, as suggested by the subsequent messages.
ORA-02428 could not add foreign key reference
Cause: Oracle could not add a foreign key reference because of an error in the declaration. Either the referenced table does not exist or the table does not have a unique key.
Action: Check that the referenced table exists and/or has a unique key.
ORA-02429 cannot drop index used for enforcement of unique/primary key
Cause: An attempt was made to drop an index that is being used as the enforcement mechanism for a unique or primary key.
Action: Drop the integrity constraint instead of dropping the index.
ORA-02430 cannot enable constraint (string) - no such constraint
Cause: The named constraint does not exist for this table.
Action: Check that a constraint exists before trying to enable it.
ORA-02431 cannot disable constraint (string) - no such constraint
Cause: The named constraint does not exist for this table.
Action: Check that a constraint exists before trying to disable it.
ORA-02432 cannot enable primary key - primary key not defined for table
Cause: An attempt was made to enable a primary key that is not defined for the table.
Action: Add a primary key definition for the table.
ORA-02433 cannot disable primary key - primary key not defined for table
Cause: An attempt was made to disable a primary key that is not defined for the table.
Action: Check that a primary key exists before trying to disable it.
ORA-02434 cannot enable unique(string) - unique key not defined for table
Cause: An attempt was made to enable a unique key that is not defined for the table.
Action: Check that a unique key exists before trying to enable it.
ORA-02435 cannot disable unique(string) - unique key not defined for table
Cause: An attempt was made to disable a unique key that is not defined for the table.
Action: Check that a unique key exists before trying to disable it.
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.
ORA-02437 cannot validate (string.string) - primary key violated
Cause: An attempt was made 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: An attempt was made to define a column check constraint that references another column.
Action: Define it as a table check constraint.
ORA-02439 Unique index on a deferrable constraint is not allowed
Cause: An attempt was made 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: Integrity constraints on a table cannot be created when creating the table using the CREATE TABLE... AS SELECT... form.
Action: First, create the table, and then alter the table to add the desired integrity constraints.
ORA-02441 Cannot drop nonexistent primary key
Cause: An attempt was made to drop the primary key constraint on a table, but there is no primary key constraint on this table.
Action: Ensure the correct table name is entered in the statement. Otherwise, no action required.
ORA-02442 Cannot drop nonexistent unique key
Cause: An attempt was made to drop a unique key constraint for a column that does not have a unique key constraint.
Action: Make certain the correct column name was entered. Otherwise, no action required.
ORA-02443 Cannot drop constraint - nonexistent constraint
Cause: An attempt was made to drop a constraint that does not exist.
Action: Make certain the constraint and table name are correct and attempt the procedure again.
ORA-02444 Cannot resolve referenced object in referential constraints
Cause: An attempt was made to define a foreign key with a reference to a schema object that cannot be resolved to a base table reference.
Action: Define referential constraints only with schema objects resolving to a base table.
ORA-02445 Exceptions table not found
Cause: The explicitly or implicitly declared exceptions table does not exist.
Action: If the correct exceptions table name was used, then create the table and retry the enable command.
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: Choose a constraint that does exist or do not perform this operation.
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