This topic includes the following sections:
If you’ve made changes to a system catalog, you may want to verify that the system catalog tables still match the definitions in the repository and the database.
Comparing the system catalog to repository definitions
You can create a verification log that lists table names, file names, the number of columns read and defined for each table, and the number of indexes read for each table. You can create this file from the DBA program or from the command line.
Using DBA to create a verification log
| 1. | Open the system catalog in DBA. Close any open lists or input windows. |
| 2. | Select Catalog > Verify. |
The Verify System Catalog window opens and prompts you for a name and location.
| 3. | Accept the default or enter a new location and name. Then select OK. |
A message displays telling you how many tables were verified and how many errors were found. (But be sure to read the log file for more complete information.)
| 4. | Select OK. |
Creating a verification log from the command line
To create a verification log from the command line, use the following syntax at a Windows or Unix prompt:
dbr SODBC_DBA:xfdba.dbr -c connect_string -v verify_file
or use the following syntax at an OpenVMS prompt:
$ XFDBA -C connect_string -V verify_file
where connect_string has the user_name/password/connect_filename format and verify_file is the full path and filename for the verification log.
The following examples generate a verification log named vrfy.log in a directory named data.
Windows:
dbr SODBC_DBA:xfdba.dbr -c DBADMIN/MANAGER/sodbc_sa -g c:\data\vrfy.log
Unix:
dbr SODBC_DBA:xfdba.dbr -c DBADMIN/MANAGER/sodbc_sa -g /usr/data/vrfy.log
OpenVMS:
$ XFDBA -C DBADMIN/MANAGER/SODBC_SA -G DKA600:[DATA]VRFY.LOG
For information on DBA command-line options, see Options .
Comparing the system catalog to a database
If your system catalog supports level-based users, you can use the DBA program or fcompare to compare the tables in the system catalog to the data definitions in a database. For information on comparing from the command line, see fcompare. (For information on level-based users, see Managing access with users, groups, and table settings.)
Using DBA to compare the system catalog to a database
| 1. | Open the system catalog in DBA. Close any open lists or input windows. |
| 2. | Select Catalog > Compare to Files. |
The Compare System Catalog to Files window opens.
| 3. | Fill in or select from the following: |
Connect file
Enter a connect file name or accept the default. The connect file determines which database and system catalog will be compared.
Option
Select All to compare all tables in the system catalog to the database. Select Specific to compare one system catalog table to the database.
Table name
If you selected the Specific option for the Option field, enter the name of the table you want compared to the database. This is available only if Specific is selected for the Option field.
Verify data
Select this option to verify data in the ISAM files. (Data definitions are compared regardless of this setting, but data is verified only if this option is selected.) This option is available only if Specific is selected for the Option field.
Log file
Enter the path and name for the log file. The log file will contain the results of the comparison.
Verbose logging
Select this option if you want to generate additional (verbose) output information.
| 4. | Click OK. |
