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

Validating the Storage Control File

You must validate the storage control file after you extract it or after you modify it. This process validates that the tables are the right length for the target schema.

• For development environment upgrades, this process validates the storage control file for the source database, so you must use the source tableowner.
• For production environment upgrades, this 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 you did 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. On the Database Utility Selection screen, choose Validate Storage Control File.
4. On the Storage Control File Language screen, choose your Storage Control File language.
5. 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).
6. To validate that storage.ctl works, connect to the catalog, and run ddlimp.

   NOTE:  If your tablespace is not large enough to hold the merged schema, examine the DDLIMP.log. Look for the bufferpools for the offending tablespace, and increase as necessary. Bufferpools are likely to increase for some tables when you extract or validate the storage layout.

7. Review the log file (ddlimp.log) that is generated in the log subdirectory under SIEBSRVR_ROOT.

   SIEBSRVR_ROOT refers to the directory that you specified when you set up the validation job.