Details of the reorganization progress are output to a log file. Any errors that occur during the reorganization are logged to this file.
If a reorganization fails, you should examine the appropriate log file to identify the cause of any errors that must be addressed before restarting the reorganization. Schema instantiation can fail for various reasons; for example:
The server could crash at any stage
The inter-object phase could encounter a No duplicates violation
A lock exception could be encountered in the commit phase
In all failure scenarios, committed transactions are not lost; that is, transaction durability is preserved. In other words, when you choose to perform part of an application deployment online and the deployment fails for any reason, user transactions that were successfully committed during the deployment can be recovered even if the effects of the failed deployment are removed.
In most cases, you can restart an interrupted schema instantiation, but this may entail redoing steps that have already been done.
Reorganization errors are output to the jomreorg.log file in the JADE log file directory. This directory is specified by the