If your database reorganization fails, you must correct the problem manually. The Generate WFL will not terminate, but is suspended, requiring you to correct the cause of the problem. The WFL waits for your input and for the reorganization to be restarted.
If you want to continue with the build after correcting the cause of the problem, and you can afford to lose the transactions that occurred during the failed reorganization, perform the following:
Reload the database from the backup taken immediately before the generate. You must reload only the files backed up by a standard DMS II backup; that is, the Control File and the data files.
Fix the cause of the reorganization problem. For example, if the reorganization failed due to duplicates being present on a Profile which you had changed to NO.DUPLICATES, you could run a Report to remove any duplicate entries.
Reply mix OK to the waiting Generate WFL. The Generate WFL then restarts from the beginning of the reorganization.
Builder does not fully support recovery of failed online reorganizations. Using the above method, database updating that has occurred during the failed reorganization is lost. If you cannot afford to lose these transactions, the following method can be used instead:
Take the application down normally and disable the window so that no users are able to sign on to the application until you have completed Step 5.
Fix the cause of the reorganization problem. For example, if the reorganization failed due to adding a Profile with NO DUPLICATES to a structure that has duplicates, use DMINQUIRY to remove the duplicates.
Reply AX mix OK to the waiting build job. The Reorganization program is restarted. It produces a program dump and the error message DATABASE ALREADY AT REORG UPDATE LEVEL, then go to End-of-Task. The Profile is locked at this stage.
Delete the new Profile that had the duplicates error and rebuild the application.
Add the Profile back and rebuild the application.
If you had performed any Report generates during this process, they need to be rebuilt.
If you are unable to correct the cause of the reorganization failure (or choose not to do so) and you want to resume using the original database, perform the following:
Reply mix DS to terminate the waiting Generate WFL.
Reload the database and Agile Business Suite programs from your backup.
Reload only the files backed up by a standard DMS II backup: that is, the Control File and the data files.
If you had performed any Report generates during the application generate, you might need to restore the original Report object code.