Oracle7 Server Messages
02430-02449: Constraint Enabling & Disabling
This section lists messages generated when commands are used that affect constraints on a table.
ORA-02430 cannot enable constraint name - 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 name - 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(str) - 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 str - 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 enable name - primary key violated
Cause: | An attempt was made to enable a primary key constraint on a column that contains either duplicate values or null. | |
Action: | Remove the duplicate values or null before enabling the primary
key constraint. | |
For more information about removing integrity constraints from columns, see the index entry on "integrity constraints, removing from columns" in Oracle7 Server SQL Reference.
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: | This is not permitted for column check constraints. Create this constraint as a table check constraint. | |
ORA-02439 non-unique index exists on unique/primary key constraint
Cause: | An attempt was made to enable a primary key or unique constraint on a column that has an existing non-unique index. | |
Action: | Drop the non-unique index on the column or do not attempt to enable
this constraint. | |
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 non-existent 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 non-existent 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 - non-existent 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. | |