Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 02140-02299: SQL Parsing Messages

This section lists some of the messages generated when SQL statements are parsed by the Oracle Server.

##### ORA-02140: invalid tablespace name

Cause: A valid tablespace name does not follow ALTER TABLESPACE.

Action: Specify a valid tablespace name following ALTER TABLESPACE.

##### ORA-02141: invalid OFFLINE option

Cause: An option other than NORMAL or IMMEDIATE follows OFFLINE in an ALTER TABLESPACE statement.

Action: The user must either specify no option following OFFLINE or one of these options: NORMAL or IMMEDIATE.

##### ORA-02142: missing or invalid ALTER TABLESPACE option

Cause: An invalid option was specified after ALTER TABLESPACE.

Action: Use one of the valid options, such as ADD DATAFILE, RENAME DATAFILE, DEFAULT STORAGE, ONLINE, OFFLINE, BEGIN BACKUP, or END BACKUP.

##### ORA-02143: invalid STORAGE option

Cause: An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, FREELISTS, FREELIST GROUPS, or PCTINCREASE was specified in an ALTER INDEX statement or in the USING INDEX clause of an ALTER SNAPSHOT statement.

Action: Check syntax, specify only valid options, and try again.

##### ORA-02144: no option specified for ALTER CLUSTER

Cause: No valid ALTER CLUSTER options were specified.

Action: Specify one or more valid options, such as PCTFREE, PCTUSED, SIZE, INITRANS, MAXTRANS, or STORAGE.

##### ORA-02145: missing STORAGE option

Cause: No STORAGE options were specified following the keyword STORAGE.

Action: Check syntax, specify one or more valid STORAGE options, and try again.

##### ORA-02146: SHARED specified multiple times

Cause: The SHARED option was specified more than once in a CREATE DATABASE statement.

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 more than once.

Action: Only specify the EXCLUSIVE option once.

##### ORA-02149: specified partition does not exist

Cause: Partition not found the base object.

Action: Enter the correct partition specification and retry the operation.

##### 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: A valid tablespace name does not follow DEFAULT TABLESPACE.

Action: Place a valid tablespace name after DEFAULT TABLESPACE and try again.

##### ORA-02156: invalid TEMPORARY tablespace identifier

Cause: A valid tablespace name does not follow TEMPORARY TABLESPACE.

Action: Place a valid tablespace name after TEMPORARY TABLESPACE and try again.

##### ORA-02157: no options specified for ALTER USER

Cause: No options were specified.

Action: Specify at least one ALTER USER option and try again.

##### ORA-02158: invalid CREATE INDEX option

Cause: An option other than PCTFREE, INITRANS, MAXTRANS, NOSORT, STORAGE, or TABLESPACE was specified.

Action: Specify one of the valid CREATE INDEX options and try again.

##### ORA-02159: installed DLM does not support releasable locking mode

Cause: The parameter file specified GC_*PARAMETERS that allow locks to be released by the LCK process when not in use. This mode required additional support in DLM that was not available.

Action: Specify configuration parameters that do not require the additional function.

  For more information about the distributed lock manager(DLM), see the index entry on "LCK" in Oracle8 Server Concepts and the index entries on "distributed lock manager" and on "distributed lock manager, LCKn process" in Oracle8 Parallel Server Concepts & Administration.

##### 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 and try again.

##### ORA-02162: invalid value for MAXDATAFILES

Cause: A number does not follow MAXDATAFILES.

Action: Specify a number after MAXDATAFILES and try again.

##### ORA-02163: invalid value for FREELIST GROUPS

Cause: A number does not follow FREELIST GROUPS.

Action: Specify a number after FREELIST GROUPS and try again.

##### ORA-02164: DATAFILE clause specified more than once

Cause: The CREATE DATABASE statement contains more than one DATAFILE clause.

Action: Specify at most one DATAFILE clause and try again.

##### ORA-02165: invalid option for CREATE DATABASE

Cause: An invalid CREATE DATABASE option is present.

Action: Specify only valid CREATE DATABASE options and try again.

##### ORA-02166: ARCHIVELOG and NOARCHIVELOG specified

Cause: Both ARCHIVELOG and NOARCHIVELOG are specified in a CREATE DATABASE statement.

Action: Specify either of these two options, but not both, and try again.

##### ORA-02167: LOGFILE clause specified more than once

Cause: The CREATE DATABASE statement contains more than one LOGFILE clause.

Action: Specify at most one LOGFILE clause and try again.

##### ORA-02168: invalid value for FREELISTS

Cause: A number does not follow the FREELISTS storage option of the CREATE TABLE or CREATE INDEX statement.

Action: Specify a number after FREELISTS and try again.

##### ORA-02169: FREELISTS storage option not allowed

Cause: An attempt was made to specify the FREELISTS storage option when performing an operation other than CREATE TABLE or CREATE INDEX.

Action: Check the syntax of the statement, remove this option, then re-execute 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 when disabling a thread.

Action: Check the syntax of the command and retry.

##### ORA-02173: invalid option for DROP TABLESPACE

Cause: Something other than INCLUDING CONTENTS was found following the tablespace name, or text other than CASCADE CONSTRAINTS was found following INCLUDING CONTENTS.

Action: Place either nothing or only INCLUDING CONTENTS after the tablespace name, or place either nothing or only CASCADE CONSTRAINTS after INCLUDING CONTENTS and try again.

##### 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, a valid rollback segment name does not follow ROLLBACK SEGMENT.

Action: Place a valid rollback segment name after ROLLBACK SEGMENT and try again.

##### 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 or STORAGE, and try again.

##### 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 and try again.

##### ORA-02179: valid options: ISOLATION LEVEL {SERIALIZABLE | READ COMMITTED}

Cause: There was 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 follows CREATE TABLESPACE.

Action: Specify one of the valid options: DATAFILE, DEFAULT STORAGE, ONLINE, or OFFLINE, and try again.

##### ORA-02181: invalid option to ROLLBACK WORK

Cause: A word other than TO follows ROLLBACK [WORK].

Action: Place either nothing or TO SAVEPOINT after ROLLBACK [WORK] and try again.

##### ORA-02182: savepoint name expected

Cause: A valid savepoint name does not follow ROLLBACK [WORK] TO [SAVEPOINT].

Action: Place a savepoint name following TO [SAVEPOINT] and try again.

##### ORA-02183: valid options: ISOLATION_LEVEL {SERIALIZABLE | READ COMMITTED}

Cause: There was 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 the resource privilege without the quota and try again.

##### 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 and try again.

##### 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 and try again.

##### 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 and try again.

##### ORA-02189: required clause: ON tablespace

Cause: The GRANT or REVOKE statement specifying a tablespace quota requires the ON tablespace clause.

Action: Correct the syntax and try again.

##### ORA-02190: keyword TABLES expected

Cause: The keyword TABLES is expected following DROP CLUSTER cluster name INCLUDING.

Action: Place the keyword TABLES after INCLUDING and try again.

##### ORA-02191: correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT name

Cause: There is a syntax error in the SET TRANSACTION statement.

Action: Correct the syntax error and retry the statement.

##### 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 num minor error num near name

Cause: There is a syntax error in an event specification.

Action: Check syntax and spelling and try again.

##### ORA-02195: attempt to create name object in a name tablespace

Cause: The object type was inconsistent with tablespace contents.

Action: Create the object in a different tablespace, or change the user defaults.

  For more information about auditing schema objects, see the index entry on "AUDIT command" in Oracle8 Server SQL Reference.

##### 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 the index entry on "CREATE TABLESPACE" in Oracle8 Server SQL Reference.

##### ORA-02197: file list already specified

Cause: In a CREATE TABLESPACE statement, more than one DATAFILE clause was specified.

Action: Merge the DATAFILE clauses into a single clause specifying multiple files and try again.

##### ORA-02198: ONLINE/OFFLINE option already specified

Cause: In a CREATE TABLESPACE statement, the ONLINE and/or OFFLINE options were specified more than once.

Action: Specify either ONLINE or OFFLINE, but not both, and try again.

##### ORA-02199: missing DATAFILE clause

Cause: A CREATE TABLESPACE statement has no DATAFILE clause.

Action: Specify the missing DATAFILE clause and try again.

##### ORA-02200: WITH GRANT OPTION not allowed for PUBLIC

Cause: An attempt was made to GRANT to PUBLIC WITH GRANT OPTION.

Action: Remove either the PUBLIC or the WITH GRANT OPTION clause and try again.

##### ORA-02201: sequence not allowed here

Cause: An attempt was made to reference a sequence in a FROM list. This is not permitted. A sequence can only be referenced in a SELECT list.

Action: Check the statement syntax, correct the reference, and try again.

##### ORA-02202: no more tables permitted in this cluster

Cause: An attempt was made to create a table in a cluster that already contains 32 tables. No more than 32 tables may be stored in a cluster.

Action: Do not try to cluster more than 32 tables.

##### ORA-02203: INITIAL storage options not allowed

Cause: The user attempted to alter the INITIAL storage option of a table, cluster, index, or rollback segment. This option may be specified only when the object is created.

Action: Remove the INITIAL option and try again.

##### 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 the privileges ALTER, INDEX, or REFERENCES 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 the privileges DELETE, INDEX, INSERT, UPDATE, REFERENCES, or EXECUTE on sequences.

##### ORA-02206: duplicate INITRANS option specification

Cause: INITRANS is specified more than once.

Action: Specify INITRANS only once and try again.

##### ORA-02207: invalid INITRANS option value

Cause: The INITRANS value is not an integer between 2 and 255, or it is not less than or equal to the MAXTRANS value.

Action: Specify a valid INITRANS value and try again.

##### ORA-02208: duplicate MAXTRANS option specification

Cause: The MAXTRANS option is specified more than once.

Action: Specify MAXTRANS only once and try again.

##### ORA-02209: invalid MAXTRANS option value

Cause: The MAXTRANS value is not an integer between 2 and 255, or it is not greater than or equal to the INITRANS value.

Action: Specify a valid MAXTRANS value and try again.

##### ORA-02210: no options specified for ALTER TABLE

Cause: No ALTER TABLE option was specified.

Action: Specify at least one ALTER TABLE option and try again.

##### 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: Specify an appropriate value for the option and try again.

##### ORA-02212: duplicate PCTFREE option specification

Cause: The PCTFREE option was specified more than once.

Action: Specify the PCTFREE option only once and try again.

##### ORA-02213: duplicate PCTUSED option specification

Cause: The PCTUSED option was specified more than once.

Action: Specify the PCTUSED option only once and try again.

##### ORA-02214: duplicate BACKUP option specification

Cause: The BACKUP option to ALTER TABLE was specified more than once.

Action: Specify the BACKUP option only once and try again.

##### ORA-02215: duplicate tablespace name clause

Cause: There is more than one TABLESPACE clause in one of the following statements: GRANT/REVOKE RESOURCE, CREATE TABLE, CREATE INDEX, CREATE/DROP TABLESPACE, CREATE CLUSTER, and CREATE ROLLBACK SEGMENT.

Action: Check the statement syntax, specify only one TABLESPACE clause, and try again.

##### ORA-02216: tablespace name expected

Cause: A valid tablespace name is not present where required in one of the following statements: CREATE TABLE, CREATE INDEX, CREATE/DROP TABLESPACE, CREATE CLUSTER, and CREATE ROLLBACK SEGMENT.

Action: Check the statement syntax, specify a valid tablespace name where required, and try again.

##### ORA-02217: duplicate storage option specification

Cause: A storage option, such as INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or PCTINCREASE, was specified more than once.

Action: Specify storage options only once and try again.

##### ORA-02218: invalid INITIAL storage option value

Cause: The specified value must be an integer.

Action: Specify an appropriate integer value and try again.

##### ORA-02219: invalid NEXT storage option value

Cause: The specified value must be an integer.

Action: Specify an appropriate integer value and try again.

##### ORA-02220: invalid MINEXTENTS storage option value

Cause: The specified value must be a positive integer that is less than or equal to MAXEXTENTS.

Action: Specify an appropriate integer value and try again.

##### 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 integer value and try again.

##### ORA-02222: invalid PCTINCREASE storage option value

Cause: The specified value must be a positive integer.

Action: Specify an appropriate integer value and try again.

##### ORA-02223: invalid OPTIMAL storage option value

Cause: The specified value must be an integer.

Action: Chose an appropriate integer value for the OPTIMAL storage option.

##### 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 the 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 other than EXECUTE on procedures, functions, or packages.

##### ORA-02226: invalid MAXEXTENTS value max allowed: num

Cause: The value specified for MAXEXTENTS is too large for the database block.

Action: Specify a value for MAXEXTENTS that is smaller than the number given in the message.

##### 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 only once and try again.

##### ORA-02229: invalid SIZE option value

Cause: The specified value must be an integer number of bytes.

Action: Specify an appropriate integer value and try again.

##### ORA-02230: invalid ALTER CLUSTER option

Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or SIZE was specified in an ALTER CLUSTER statement.

Action: Specify only valid options in the ALTER CLUSTER statement and try again.

##### ORA-02231: missing or invalid option to ALTER DATABASE

Cause: An invalid option was specified in the statement.

Action: Check the syntax of the ALTER DATABASE command. Specify only valid options in the ALTER DATABASE statement and try again.

##### ORA-02232: invalid MOUNT mode

Cause: A mode other than SHARED or EXCLUSIVE follows the keyword MOUNT in an ALTER DATABASE statement.

Action: Specify either SHARED, EXCLUSIVE, or nothing following the keyword MOUNT in the ALTER DATABASE statement and try again.

##### ORA-02233: invalid CLOSE mode

Cause: A mode other than NORMAL or IMMEDIATE follows the keyword CLOSE in an ALTER DATABASE statement.

Action: Specify either NORMAL, IMMEDIATE, or nothing following the keyword CLOSE in the ALTER DATABASE statement and try again.

##### 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 filename

Cause: In a LOGFILE, DATAFILE, or RENAME clause, a character string literal was expected, but not found, in a filename list.

Action: Specify filenames using character string literals and try again.

##### ORA-02237: invalid file size

Cause: An integer file size does not follow SIZE in a LOGFILE or DATAFILE file list.

Action: Specify an appropriate file size following the keyword SIZE and try again.

##### ORA-02238: filename lists have different numbers of files

Cause: In a RENAME clause in ALTER DATABASE or TABLESPACE, the number of existing filenames does not equal the number of new filenames.

Action: Make sure a new filename corresponds to each existing filename and try again.

##### ORA-02239: there are objects that 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 OBJNO or TABNO.

Action: Specify a number after OBJNO or TABNO.

##### ORA-02241: must be of form EXTENTS FILE num BLOCK num SIZE num,...

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 were specified after ALTER INDEX.

Action: Specify the INITRANS, MAXTRANS, or STORAGE option in the ALTER INDEX statement and try again.

##### ORA-02243: invalid ALTER INDEX or ALTER SNAPSHOT option

Cause: An option other than INITRANS, MAXTRANS, or STORAGE was specified in an ALTER INDEX statement or in the USING INDEX clause of an ALTER SNAPSHOT statement.

Action: Specify only valid options and try again.

##### ORA-02244: invalid ALTER ROLLBACK SEGMENT option

Cause: An option other than STORAGE was found.

Action: Specify the STORAGE option and try again.

##### ORA-02245: invalid ROLLBACK SEGMENT name

Cause: A rollback segment name was expected, but not found, following ALTER [PUBLIC] ROLLBACK SEGMENT.

Action: Place a rollback segment name after SEGMENT and try again.

##### ORA-02246: missing EVENTS text

Cause: A character string literal was expected, but not found, following the ALTER SESSION SET EVENTS command.

Action: Place the string literal containing the EVENTS text after the keyword EVENTS and try again.

##### ORA-02247: no option specified for ALTER SESSION

Cause: The option SET EVENTS was expected, but not found, following the ALTER SESSION command.

Action: Place the SET EVENTS option after the ALTER SESSION command and try again.

##### 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 operating system-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 constraint name and try again.

##### ORA-02251: subquery not allowed here

Cause: A subquery is not allowed at this point in the statement.

Action: Remove or relocate the subquery and try again.

##### ORA-02252: check constraint condition not properly ended

Cause: The specified search condition for the check constraint is not properly ended.

Action: Check and correct the search condition's syntax. Then retry the operation.

##### ORA-02253: constraint specification not allowed here

Cause: A constraint specification is not allowed at this point in the statement.

Action: Remove or relocate the constraint specification and try again.

##### ORA-02254: DEFAULT <expression> not allowed here

Cause: A default-value expression is not allowed for the column at this point in the statement.

Action: Remove or relocate the default-value expression and try again.

##### 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: Ensure 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 of 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-: num occurs while type-checking column default value expression

Cause: An attempt to alter a column's datatype caused a type-checking error because the new datatype conflicted with the existing column's default value expression.

Action: Remove the default value expression or do not alter the column's datatype, and try again.

##### ORA-02263: need to specify the datatype for this column

Cause: The required datatype for the column is missing.

Action: Specify the required datatype and try again.

##### ORA-02264: name already used by an existing constraint

Cause: The specified constraint name is not unique.

Action: Specify a unique constraint name for the constraint and try again.

##### 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: An attempt was made to perform an operation on a pair of columns with incompatible datatypes.

Action: Specify 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: Do not attempt to reference the table using a unique key, or create a unique key for the table.

##### 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 a 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: Modify the default expression or change the column's datatype, and try again.

##### ORA-02277: invalid sequence name

Cause: An invalid sequence name was specified.

Action: Check syntax and spelling, specify a valid sequence name, and try again.

##### 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 access privilege is required for this operation. Also, this error can occur if attempting to access a remote sequence through an invalid or non-existent database link.

Action: Check spelling of the sequence name or obtain the required access privilege. If necessary, create the sequence. All remote sequences accessed in a distributed transaction must be on the same node.

##### ORA-02290: check constraint str.name 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 str.name violated - parent key not found

Cause: An attempt was made to INSERT or UPDATE a foreign key value. The result was a value that is not in the parent key.

Action: UPDATE to or INSERT a value that is in the parent key.

##### ORA-02292: integrity constraint str.name 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 enable name - 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 the index entry on "ALTER TABLE" in Oracle8 Server SQL Reference.

##### ORA-02294: cannot add referential constraint - parent keys not found

Cause: An attempt was made via an ALTERTABLE statement to add a referential constraint to a populated table that had no matching parent values.

Action: Retry the ALTER TABLE statement, specifying a valid primary key in a parent table.

##### 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 name - 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 the index entries on "ALTER TABLE" and on "ENABLE clause" in Oracle8 Server SQL Reference.

##### ORA-02297: cannot disable constraint name.name - 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 enable name - 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 the index entries on "ALTER TABLE" and on "ENABLE clause" in Oracle8 Server SQL Reference.

##### ORA-02299: cannot enable name - 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 the index entries on "ALTER TABLE" and on "ENABLE clause" in Oracle8 Server SQL Reference.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index