Prior to a migration or upgrade, you should validate the integrity of the database to insure against any loss of data that might result from errors in tables or a corrupted file system. Pre-existing problems on the source system can cause issues, such as the following:
- Failure of the entire migration or upgrade operation
- Failure to detect new problems introduced by the migration on the destination system
- Apparent migration or upgrade problems that are not real
- Database failures on the destination system
These utilities may take a long time to run, depending on the priority level at which they are run, the degree of checking they do, and how much data exists on the system. To speed the utilities and minimize the effect on currently logged on users, do the following:
- Run SCANDISK at a low priority level.
- Run CheckDisk at a medium priority doing Level 2 checking with the following command:
check dbc at level two with no error limit skiplocks priority=m error only;
CheckTable commands require a semicolon at the end. - If there are no users logged on to the system, use the IN PARALLEL option of the CheckTable command to speed the checking.