Upgrade Guide for DB2 UDB for z/OS > Basic Database Preparations > Preparing the Storage Layout of the Schema >

Validating the Extracted Storage Control File

When you have extracted your existing database storage control file and merged it with a Siebel 7.8 template in preparation for the 7.8 upgrade, you must validate the storage control file. (You must also validate the storage control file any time you modify it.) The validation process validates that the tables are the right length for the target schema. Do not proceed with the Siebel 7.8 upgrade until the validation process runs without error.

Be aware of the following:

• For development environment, midtier-centric upgrades, the validation process validates the storage control file for the source database, so you must use the source tableowner.
• For production environment upgrades, the validation process validates the storage control file for the target database, so you must use the target tableowner.

The validation produces two output files in the log directory under SIEBSRVR_ROOT.

• db_config_siebel.log
• db_config_validation.log

NOTE:  When validating the extracted storage control file, the validation job calls for the schema.ddl file as an example. Make a copy of ddl.ctl and rename it schema.ddl, keeping the copy in the same location as ddl.ctl.

If you are validating a storage control file for an EBCDIC database, the validation process does not report all errors the first time it is run. You must rerun the validation process after fixing all reported errors. If new errors are reported on a subsequent validation, you must fix the errors and run the validation again. You may proceed after the validation reports no errors.

NOTE:  It is recommended that you enter all values in uppercase letters.

To validate the storage control file

1. Launch the Database Server Configuration Wizard as described in Extracting the Storage Control File.

   In the following steps, for Windows users, screen refers to a standard, application window. For UNIX users, the Siebel Upgrade Wizard displays in a shell. Screen refers to the pages of text that display in the shell.

2. Enter the information requested on each screen and click or press the appropriate button for your operating system to proceed:
   • Windows: Click Next.
   • UNIX: Press Enter.
3. Specify the following values:
   1. On the Database Configuration Options screen, select the Validate Storage Control File option.
   2. On the Schema File screen, specify the following values:
      • Schema File. Specify the directory path and filename of the file against which the extracted file is to be validated. For development environment upgrades, specify the ddl.ctl file. For production environment upgrades, specify the schema.ddl file.
      • Storage Control File. The name of the storage control file that you want to validate (this is the file that you extracted in Extracting the Storage Control File).
4. On the Configuration Parameter Review screen, review the configuration values you entered on the previous Configuration utility screens.

   NOTE:  Passwords are encrypted and do not appear in plain text either in the user interface or in the upgrade configuration files (UCF files). After a password is entered, it always appears in encrypted form. If you need to use another password, you must rerun the configuration utility.

   If you need to change any values, do the following:

   • Windows: Use the Previous and Next buttons to access the desired screens, then to return to this screen. When you are satisfied, click Finish to launch the Siebel Upgrade Wizard.
   • UNIX: Enter N, and rerun the Database Server Configuration Wizard by entering dbsrvr_config.ksh. This allows you to reconfigure with different values. When you are satisfied, enter Y to launch the Siebel Upgrade Wizard (srvrupgwiz).
5. When the Upgrade Wizard appears, click OK start the storage control file validation process.

   NOTE:  If the Validate Storage Control File process fails because tablespaces for your Siebel schema are not large enough to hold the new table definitions, examine the dbvalidate_report.log file for further information. Look for the bufferpools for any offending tablespace, and increase them as necessary in the storage.ctl file.

6. Review the log files, dbvalidate_report.log and dbvalidate_schema.log, which are generated in the SIEBEL_ROOT\LOG\dbconfig_validate_mf\output directory (Windows) or the $SIEBEL_ROOT/LOG/dbconfig_validate_mf/output directory (UNIX).