Verifying the Repository After Upgrade

As noted in Step 15 of the table in Upgrading a Custom Database Schema, the repository is optionally verified after you complete the upgphys process. This step is executed if you selected the option Verify Repository After Upgrade during database configuration. The following are the verification steps executed:

1. dbchck. Provides a report of the schema differences between the physical database and the repository definition. Unacceptable errors can occur if data types are mismatched. Acceptable errors occur if a schema object (such as a table or an index) is intentionally external to the repository.

2. dictutl. Verifies that all dock objects and rule definitions are correct.

3. mlovupgd. Validates the repository for data inconsistencies. Errors are logged into the log file and upgrade wizard continues with the next steps.

4. SeedConflict. Generates the seed conflict report in HTML format. The report contains details of all the records with unique constraint violations.