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

Extracting a Storage Control File from the DB2 Catalog


You can create a storage control file to use during a custom installation using the Siebel extract utility. This utility extracts the storage layout of your source database from the DB2 catalog and creates a new storage control file that you can use during the custom installation process. You can use the extract utility at any time.

NOTE:  You must validate the storage control file after you extract it and after you modify it. For information on how to validate a storage control file, see Validating the Extracted Storage Control File.

Follow the instructions in the following procedure to extract a storage control file under Windows and UNIX.

To extract 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.
  2. On the Siebel Database Operation screen, select Run Database Utilities, and click Next.
  3. On the Database Utility Selection screen, select Configure Database, and click Next.
  4. The following options are available on the Database Configuration Options screen:
    • Extract Storage File. Extracts a storage control file based on the existing Siebel Schema layout.
    • Validate Storage File. Validates that a specified template and a specified schema will work on the DB2 host.

      Select the Extract Storage File option, and click Next.

  5. The following Extract options are available:
    • Extract from catalog. This option extracts the storage layout of your source database from the DB2 catalog. The output is a new storage layout.
    • Extract from catalog and Merge with Template. Extracts the storage layout of your source database and merges it with a Siebel template storage control file. This preserves your schema layout. If a database object is specified in both the existing database and the template, the layout of the existing database is extracted as the default. If there are conflicts that cannot be resolved, the extract process fails. You must correct any errors and run the Extract process again.

      Select the appropriate Extract option, and click Next.

  6. 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.
  7. On the ODBC Data Source Name screen, you can either select the default name of the ODBC data source or specify a different data source name.

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

  8. On the Database User Name screen, type your source database username and password, confirm the password by typing it again, and then click Next.
  9. On the Siebel Schema Qualifier screen, type the schema qualifier for your existing database, and then click Next.

    The schema qualifier is also an authorization ID. The schema qualifier must start with a letter and cannot contain special characters.

  10. Identify the database encoding scheme; either Unicode or Non-Unicode.

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

    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.

  11. If you indicated that your database uses a non-Unicode encoding scheme, specify the code page encoding scheme you use, either ASCII or EBCDIC, and click Next.

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

  12. On the Default Database Name screen, enter the default names for Siebel databases (for example, SIDB) and table spaces (for example, SIEBTS), and click Next.
  13. On the Default Storage Group screen, enter default storage group names for Siebel table spaces and indexes, for example, SYSDEFLT. Click Next.
  14. On the Default Buffer Pool Name screen, specify the default buffer pool names for your table spaces and indexes. Your DBA must have previously activated the buffer pools and granted access to them.
  15. In the Storage Control File screen, type the name you want to assign to the new storage control file generated, for example DBSRVR_ROOT\db2390\my_storage_file.ctl (Windows) or DBSRVR_ROOT/db2390/my_storage_file.ctl (UNIX). Click Next.
  16. 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_extract_catalog_mf (Windows) or SIEBSRVR_ROOT/log/dbconfig_extract_catalog_mf (UNIX).
  17. Save the configuration information you have entered and launch the Siebel Upgrade wizard as described in the following topics:
  18. Click OK.

    The Upgrade Wizard connects to the z/OS host, extracts the storage control file from the DB2 catalog, and copies it to the file you specified.

  19. Click OK to complete the storage control file Extract process.

    You must now validate the extracted storage control file, as described in Validating the Extracted Storage Control File.

Implementing Siebel Business Applications on DB2 UDB for z/OS Copyright © 2008, Oracle. All rights reserved.