3        Troubleshoot Database Error Messages

Object Registration

ORA-00955: name is already being used by an existing object

1.     Check if the bkp tables  (REV_TABLES_B_BKP, REV_TAB_COLUMNS_BKP, REV_TAB_REF_CONSTRAINTS_BKP, REV_TAB_CONSTRAINTS_BKP, REV_TABLE_CLASS_ASSIGNMENT_BKP, REV_TABLE_LOG_CLASS_ASMNT_BKP, REV_COLUMN_PROPERTIES_BKP , REV_TAB_COLUMNS_MLS_BKP, REV_VIRTUAL_TABLES_BKP, REV_TAB_CONSTRAINT_COLUMNS_BKP, REV_TAB_PARTITIONS_BKP, REV_TABLES_TL_BKP, REV_TAB_INDEXES_BKP , REV_SYNONYMS_BKP, AAI_DMM_TAB_PARTITIONS_BKP, AAI_DMM_TAB_PART_COLUMNS_BKP, AAI_DMM_TAB_SUBPARTITIONS_BKP, AAI_DMM_TAB_SUBPART_COL_BKP) are created.

2.     If they exist, drop them and then proceed with Object Registration using the RegisterObjects.sh utility.

For more details, see Object Registration.

Object Registration

ORA-01653: unable to extend the table by in tablespace

Add data file to the existing tablespace and proceed with object registration using the RegisterObjects.sh utility.

For more details, see Object Registration.

Object Registration

ORA-01400: cannot insert NULL into ("<<schema_name>>"."REV_TABLE_CLASS_ASSIGNMENT"."TABLE_CLASSIFICATION_CD")

1.     Ensure that the REV_TABLE_CLASSIFICATION_B and REV_TABLE_CLASSIFICATION_TL tables are populated during Infodom creation.

2.     If tables are empty or found with incorrect entries, correct them.

3.     Re-trigger Object Registration.

For more details, see Object Registration.

Model Upload

ORA-01408: such column list already indexed

1.     Ensure that the index is created as part of the model upload process. If the index is created outside the model upload process, then drop the same.

2.     Re-Trigger Model upload

An error can appear for any database object being created or maintained as part of Data Model Management. In such cases, ensure that the database (atomic schema) is consistent with the data model. Therefore, perform the necessary manipulations such as drop/alter/create at the database end to assure consistency and proceed with the model upload operation.

Model Upload

ORA-00955: name is already used by an existing object

Ensure that the existing table is created via model upload. Otherwise, drop the existing table and re-trigger the Model upload process.

An error can appear for any database object being created or maintained as part of Data Model Management. In such cases, ensure that the database (atomic schema) is consistent with the data model. Therefore, perform the necessary manipulations such as drop/alter/create at the database end to assure consistency and proceed with the Model Upload process.

Object Registration

Error while executing the query Failed Executing Batch: error occurred during batching: ORA-00001: unique constraint(PK_REV_TABLES_B) violated

1.     Verify the data model and delete the duplicate tables from ERwin.

2.     Re-generate the repository XML file from ERwin.

3.     Trigger Object Registration using the RegisterObjects.sh utility.

For more details, see Object Registration.

Model Upload

ORA-01758: table must be empty to add a mandatory (NOT NULL) column

When you modify an existing column from NULL to NOT NULL, ensure that there is no data in the table.

Model Upload

ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found

Ensure there is no duplicate record for the columns that are created as part of the Unique Index.

Model Upload

ORA-02437: cannot validate - primary key violated

When you try to enable a primary key constraint, ensure that the columns in the primary key do not contain NULL values or duplicates.