Bookshelf Home | Contents | Index | PDF     

Implementing Siebel Business Applications on DB2 UDB for z/OS > Installing the Siebel Database on the DB2 Host > Preparing the Storage Control File >

Validating the Extracted Storage Control File

You must validate a storage control file after you extract it or after you modify it to ensure it has been correctly generated and will work with the Siebel Schema as defined in the schema.ddl file.

To validate the storage control file

  1. Launch the Database Configuration Wizard and follow the steps in Performing a Standard Installation until the Siebel Database Operation screen is displayed (Step 7).
  2. On the Siebel Database Operation screen, select Run Database Utilities, and click Next.
  3. Choose the Configure Database option, and click Next.
  4. On the Database Configuration Options screen, select the Validate Storage File option, and click Next. This option validates that a specified storage control file and a specified schema will work on the DB2 host.
  5. Select one of the following options:
    • Batch - Generate Unload/Load. Select this option to validate the storage control file that you are going to use when upgrading to a new release of Siebel Business Applications.
    • Foreground - Generate Insert/Select. Select this option to validate the storage control file that you are going to use when migrating repositories or synchronizing Siebel repository definitions with the Siebel Schema.
  6. Identify the appropriate database encoding method, either Unicode or non-Unicode, and click Next.

    CAUTION:  Choose the correct option for your database to prevent installing the wrong data types. The database cannot create Unicode data types on a non-Unicode page setting, so check this setting carefully before choosing the option.

    If you selected the UNICODE Database option, proceed to Step 8.

  7. If you indicated that your database uses a non-Unicode encoding scheme, specify the code page encoding scheme for your Siebel Database, either ASCII or EBCDIC.

    For more information on choosing the database code page, see Considerations in Choosing the Database CCSID.

  8. If you have installed more than one language pack onto the Siebel Server, the Base Language screen is displayed. Specify which language is the primary (base) language for the Siebel database, and click Next.
  9. On the ODBC Data Source screen, accept the default name of the ODBC data source, or enter a different data source name.

    NOTE:  The Siebel Server installation process automatically creates the data source, using the format EnterpriseName_DSN.

    To continue, click Next.

  10. On the Database User Name screen, indicate the source database user name and password. The Database User Name is an ID authorized to log in to the Siebel database. This user ID must have authorization to set CURRENT SQLID.

    To continue, click Next.

  11. On the Siebel Database Schema Qualifier screen, enter the following information:
    1. Siebel Schema Qualifier. Type the identifier that designates the Siebel Schema for your database. This is also an authorization ID. The schema qualifier must start with a letter, can be up to 8 characters in length, and cannot contain special characters.
    2. Security Group ID/Grantee. Type the group ID to which schema access is being granted, for example, SSEROLE.

      To continue, click Next.

  12. On the Schema File screen, specify the names and directory paths of the following files:
    • Schema file. Specify the directory path and filename of the schema file against which the extracted storage control file is to be validated. If your Siebel Schema has been modified, use schema.ddl. For the Siebel preconfigured Schema, use ddl.ctl.
    • Storage control file. Enter the directory path and filename of the file you extracted and which you want to validate (for example, my_storage_file.ctl).

      To continue, click Next.

  13. On the Log Output Directory screen, indicate the directory where you want the log files to be generated. The default directory is SIEBSRVR_ROOT\log\dbconfig_validate_mf\output (Windows) or SIEBSRVR_ROOT/log/dbconfig_validate_mf/output (UNIX).
  14. Save the configuration information you have entered and launch the Siebel Upgrade wizard as described in the following topics:
  15. Click OK to start the validation process.
  16. When the validation process completes successfully, click OK.

    If the validation process fails, errors are noted in the log files in the directory you specified in Step 13. Correct the errors noted and run the validation process again.

    If you chose the Batch - Generate Unload/Load validate option, the validation process generates the following additional files in the log output directory. Review these files to determine the cause of validation errors:

    • load.ldc
    • schema.db.sql
    • schema.grt.sql
    • schema.nuind.sql
    • schema.oind.sql
    • schema.sql
    • schema.tbl.sql
    • schema.tbsp.sql
    • schema.uind.sql
    • unload.ldc
    
Implementing Siebel Business Applications on DB2 UDB for z/OS Copyright © 2008, Oracle. All rights reserved.