Siebel Database Upgrade Guide for DB2 UDB for z/OS > Basic Database Preparations for a Siebel Upgrade > 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 8.0 template in preparation for the 8.0 upgrade, you must validate the storage control file. (You must also validate the storage control file any time you modify it.) The validation process checks that the tables are the right length for the target schema. Do not proceed with the Siebel 8.0 upgrade until the validation process runs without error.

The following procedure describes how to validate the storage control file you extracted and merged with a Siebel 8.0 template as described in Extracting the Storage Control File.

To validate the storage control file

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

   NOTE:  The procedure to validate a storage control file using the Database Configuration Wizard is also described in Implementing Siebel Business Applications on DB2 for z/OS.

2. Specify the following values:
   1. On the Database Configuration Options screen, select the Validate Storage File option.
   2. On the Data Transport Method screen, select the Batch - Generate Unload/Load option.
   3. On the following screens, make sure you specify values for the staging database:
      • ODBC Data Source Name
      • Database User Name
      • Siebel Schema Qualifier screen
   4. 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: Specify the name of the storage control file you extracted and merged in Extracting the Storage Control File. For development environment upgrades, specify storage_upg_dev.ctl. For production environment upgrades, specify storage_upg_prod.ctl.
3. When you have entered all the required values and reviewed them, launch the Siebel Upgrade Wizard to start the validation process. SeeRunning the Database Configuration Wizard to Perform Upgrade Tasks.
4. When the validation is completed, review the log files, dbvalidate_report.log and dbvalidate_schema.log, that are generated in the SIEBEL_ROOT\LOG\dbconfig_validate_mf\output directory (Windows) or the SIEBEL_ROOT/LOG/dbconfig_validate_mf/output directory (UNIX).

   If any validation errors occurred, correct them, then run the validation process again.

About Validation Errors

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.

The most common reason that the validation process fails is because table spaces for the Siebel schema are not large enough to hold the new table definitions. If this error occurs, examine the dbvalidate_report.log file and identify the names of the buffer pools associated with the table spaces generating errors. Increase the bufferpool sizes as necessary in the storage.ctl file.

You can amend the storage control file using any of the methods described in Modifying the Storage Control File. To amend buffer pool sizes associated with table spaces generating errors using the Database Storage Configurator (dbconf.xls), perform the following procedure.

To amend bufferpool sizes using dbconf.xls

1. Open dbconf.xls and select Enable Macros when prompted.
2. Import the storage control file that generated the validation errors:
   1. With the Home tab active, click Import.
   2. Go to the directory where your storage control file is located and double-click the appropriate file.
   3. When the import process is completed, click OK.
3. The following message appears:

   Please enter default values for your system

   Either amend the values for the displayed parameters, or accept the default values. (This screen does not appear if you have already set the default values.)

4. Click Set.
5. You are prompted to indicate whether or not you want to import row lengths. Select No.
6. Select the Functions tab, then click the Tools tab.
7. Click the Repair BP Validation button.
8. Select the log file generated by the validation process by double-clicking on the file, or selecting the file and clicking Open. This file lists the names of the buffer pools associated with the table spaces generating errors.
9. The Database Storage Configurator updates the buffer pool sizes for the table spaces generating errors in the storage control file. When the process is completed, the following message is displayed.

   Bufferpools have been updated successfully!

10. Click OK.
11. Click the Home tab, and then click Export to save the amended storage control file. Save the file with the same filename. A message is displayed stating that the file will be validated (the syntax is validated).
12. Click OK. When the validation process is completed, a message is displayed if the file contains any values that you need to review.
13. Click OK. The values in the file that need to be reviewed are displayed, highlighted in red (errors) or yellow (warnings).
14. Make a note of the object that is generating the error or warning—the relevant object type tab and the object are highlighted. Click OK.
15. Navigate to the object that generated the validation warning or error by selecting Structures > object type. Amend the highlighted values if required, then export the file again.
16. When the validation process is completed successfully and you have exported the file, exit from the Database Storage Configurator.
17. Validate the storage control file against the target schema again using the Database Configuration Wizard.

For further information on using the Database Storage Configurator, see Implementing Siebel Business Applications on DB2 for z/OS.