During recovery, one of the following indications might be notified to you:
Database or Audit file problem exists.
Audit files are unreadable or out of sequence.
Another similar condition exists.
In such situations, you might need to use the backup copy of your database for recovery.
Note: The application will not automatically recover with a backup copy. You must decide if the backup copy is needed for recovery.
Recovery with a backup copy is required when data in the Database files is destroyed or corrupted by system software malfunction, a hardware fault, or human error. If the system software or hardware caused the problem, contact your Unisys support representative.
Never remove or copy over Audit files in a recovery situation. They are the only means of restoring your database to the state it was in before the problem occurred. It is safe to remove them only when you have taken a current backup copy through the COPYAUDIT program. |
CautionTo recover with a backup copy, use SYSTEM/DMUTILITY with RECOVERY or REBUILD, as appropriate. Refer to the Enterprise Database Server for ClearPath MCP Utilities Operations Guide for more information on recovery.
Note: It might be possible to reload only a portion of your database if the problem is localized. To do this, use the DMUTILITY program and the RECOVER statement. Refer to the Enterprise Database Server for ClearPath MCP Utilities Operations Guide for more information.
Post Recovery Procedures
The application completes the loading of the database formats and advise you when recovery and initialization is complete. Your application is then ready for data entry again.
Inhibiting COMS TTRAIL Recovery
If your database has been restored to an earlier point in time by a database rollback or by loading a backup copy, COMS tries to recover your application from its TTRAIL. You should inhibit this recovery by modifying the COMS database definition, setting the RDS pointer to End.
This is because COMS discards all outputs produced during the replaying of transactions committed to the TTRAIL. This includes TP-TP outputs (program to program), which Agile Business Suite uses to initiate external activities. As a consequence, any results of the following logic commands are not recovered: Run command, Start command, and commands for external Automatic Entry.
If COMS recovery is inhibited, then the database remains in its rolled-back state, and COMS will not resubmit transactions to the application for reprocessing.