What Is the Verify Database Utility?
The Lawson repository contains descriptions of all Lawson tables, indexes, and spaces for tables, indexes, and lobs. When these objects are stored in Oracle, the database driver translates the Lawson description for storage in the database. For Lawson applications to work properly with Lawson tables stored in the Oracle database, Lawson dictionary descriptions must match the expected translations in Oracle. Mismatches in these definitions can lead to performance problems or even program failure (column definition mismatches).
The dbverify utility checks for several kinds of differences when it compares the Lawson dictionary with the Oracle definitions:
-
Missing columns or indexes
The utility checks to make sure that each column and index defined in the Lawson dictionary has a matching column and index in the Oracle database.
-
Extra columns or indexes
The utility checks to make sure that all objects defined in the Oracle database have counterparts in the Lawson dictionary.
-
Mismatched column or indexes
When the columns defined in a Lawson table or index are not matched by the Oracle database definitions of those columns, the utility returns a mismatched file or index definition message. Mismatches include differences in data types, lengths, and so on. All fields are assumed to not allow nulls―only those that do allow nulls have output noting this fact.
-
Mismatched table, index, and lob spaces
The utility checks to make sure that definition of each space in the Lawson dictionary matches the Oracle database definitions for table spaces.
While the utility finds the differences between the Lawson dictionary and the Oracle database definitions, it does not fix the mismatches or alter the definitions in any way.
If you run dbverify without options, it prints out a line that notifies you as it checks each table and index in the specified product line, system code, or file. If you run the utility in quiet mode, it prints out only the messages that identify the differences between the definitions, followed by a summary.