Page Comparison

...

1. Dump the corrupted database to a file using the Universal Database Dump utility.
2. Reload the database from the dump file using the Universal Database Load utility.

Database corruption can occur if the system or address space that is managing the databases ends abnormally. A Universal Agent program that utilizes databases should not be terminated abnormally.

...

For the first recovery attempt, execute the Universal Database Dump utility with the -r (lowercase) command line option. This option instructs the utility to recover as much data as possible. Depending on the extent of database corruption, this may result in a recovered database with some incomplete key/data pairs.

Reload the database using the Universal Database Load utility, and specify the -o option. This option instructs the utility to remove the underlying database file, which results in a clean reload from the dump file.

Anchor
1067298 1067298

If the database passes validation when you restart the application, it is likely that all data was successfully recovered and no additional recovery attempts are necessary.

Anchor
106730010676001067300 1067600

If the database fails validation, rerun the Universal Database Dump utility and omit the -r option. This results in a dump of only the most complete data. While this improves the chances for successful recovery, some data loss is likely. Rerun the Universal Database Load utility and restart the application.

Anchor
106730210676021067302 1067602

If both recovery attempts fail, you may delete the corrupted database and restart the application. This results in a total loss of data, but will allow the application to execute. The application will create the missing database during startup.

...