Correcting Data if a Reorganization Fails
Reorganization maintains a backup copy of all databases files involved in the reorganization. If the reorganization encounters an error, these backup files are used to restore the database.
When something goes wrong during a schema instantiation, you can perform one of the following actions.
-
Restart the schema instantiation (by using the Restart Reorg command from the Schema menu Reorg command submenu or the JadeReorgApp application and specifying the restartReorg value in the
This action applies to situations in which the schema instantiation was interrupted (for example, the machine halted) and reprocessing can still be accomplished in the remaining system downtime window.
-
Abandon the schema instantiation (by using the Abort Reorg command from the Schema menu Reorg command submenu or the JadeReorgApp application and specifying the abortReorg value in the
This action may be necessary in failure situations when there is no degree of certainty the problem that caused the failure can be resolved and the instantiation completed within the remaining system downtime window.
If your reorganization fails because of a data error (for example, you have duplicate keys in a collection class that does not allow them or there is an invalid reference), the following error is most likely to be displayed.
3101 Unable to reorganize class - refer to jomreorg.log
Your reorganization log file contains the class in which the error occurred, to enable you to correct your data before actioning a successful reorganization, as follows.
-
Check your reorganization log file, to determine the class or classes that contains the error or errors.
-
Write some code to correct the data (for example, by using a method in the JadeScript class).
-
Initiate the reorganization of your schema again. (For details, see "
