Running the Calyx RIM 5.1 Database Migration Scripts
Preparing to Run the Scripts
Before you run the
Calyx RIM 5.1 database migration scripts, please note the following:
- Calyx does not currently support character columns that use char semantics. Calyx supports only byte semantics. If you changed your database or specific columns in it to use char semantics, and if the data length in bytes exceeds what a column that uses byte semantics can hold, the migration might fail. To ensure that the migration succeeds, shorten the data or customize the migration.
- Delete all adhoc tables that you do not need. If they are part of Calyx RIM, they generate many significant migration errors.
Running the Scripts
Error from Using Char Semantics
Warning: If you encounter the error shown below when you run a script, your database or specific columns in it are using char semantics. To prevent this error, shorten the data or customize the migration. If you encounter this error, inform
Calyx Technical Support about it.
ORA-01450: maximum key length (6398) exceeded
Error from an Oracle Index or Constraint Creation Failure
Warning: If you encounter an error indicating an Oracle index or constraint creation failure when you run a script, contact
Calyx Technical Support for help. Do not try to resolve the problem yourself.
The following are examples of such an error:
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
ORA-02298: cannot validate (.R_<constraint number>) - parent keys not found
ORA-02296: cannot enable (constraint name>) - null values found
ORA-02299: cannot validate (<index_name>) - duplicate keys found
Error from an Adhoc Table
If you encounter an error caused by an adhoc table:
- If the table is not part of Calyx RIM, ignore the error or delete the table and rerun the migration script.
- If the table is part of Calyx RIM, contact Calyx Technical Support for help.