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

Extracting the Storage Control File


To extract the storage control file from the source database, follow the procedure outlined in this topic.

To extract the storage control file

  1. Run the Database Server Configuration Wizard.

    For information on running the Database Server Configuration Wizard, see Running the Database Server Configuration Utility Under Windows or Running the Database Server Configuration Utility Under UNIX.

  2. Enter the information shown in Table 15 when prompted by the Database Server Configuration utility. Collect this information and verify it before running the utility.
Table 15. Information Required for the Database Server Configuration Utility—Extract and Merge Option
Screen Name
Required Information

Siebel Gateway Name Server Address

Windows only. The Siebel Gateway Name Server machine name and the Enterprise Server name.

Siebel Server Directory

The absolute path of the directory where the Siebel Server is installed—for example D:\sea_7x\siebsrvr. For UNIX, do not enter the string $SIEBEL_ROOT.

Siebel Database Server Directory

The absolute path of the directory where the Siebel Database Server is installed—for example D:\sea_7x\dbsrvr.

RDBMS Platform

Choose IBM DB2 UDB for z/OS.

Siebel Database Operation

Choose Run Database Utilities.

Database Utilities Options

Choose Configure Database

Database Configuration Options

Choose Extract Storage File to extract a storage control file.

Extract Options

Extract from Catalog. This option extracts the storage layout of your source database from the DB2 catalog as-is. The output is a new storage layout.

Extract from Catalog and Merge with Template. This option preserves your existing layout. This option merges storage layout information from your source database with information that you already entered into a storage control file, only taking objects from the template that do not already exist in the catalog.

NOTE:  The first time that you run an upgrade, you must use the Extract from Catalog and Merge with Template option, thereby preserving your existing layout.

Source Database ODBC Data Source Name

Verify the ODBC name for connecting to the source Siebel Database for your upgrade. If it is not correct, enter the correct ODBC name.

The ODBC data source must have the same name as the subsystem. When you set up the ODBC connection in DB2 Connect, use the actual subsystem name for the database alias.

Windows: To find the name of your ODBC data source, navigate to Start > Settings > Control Panel > Administrative Tools > Data Source (ODBC). Click the System DNS tab to find the name of your ODBC data source.

UNIX: To find the name of your ODBC data source, type:
vi $ODBCINI.

Source Database User Name

Enter the source user name and password for the Siebel administrator of the source database for your upgrade.

NOTE:  The source database user name (user ID) needs to have authorization to set CURRENT SQLID.

Source Siebel Schema Qualifier and Security Group ID.

Source Schema Qualifier. Enter the eight-character identifier that designates the Siebel Schema for your source database. This is also an authorization ID. The schema qualifier must start with a letter, cannot contain special characters, and must be entered in uppercase.

Source Security Group ID. Enter the user ID of the group to whom schema access is granted, for example, SSEROLE.

Code Page Encoding Scheme

Indicate whether your DB2 subystem is ASCII or EBCDIC.

Siebel Schema Layout

Choose Siebel Schema without Partitioning if you want all tables only in segmented tablespaces.

Choose Siebel Schema with Partitioning if you want a layout that includes a set of tables that is recommended for partitioning. The remaining nonpartitioned tables are in segmented tablespaces.

Default Tablespace

Enter the name of the default tablespace.

Storage Group for Tablespaces

Storage Group for Indexes

Indicate the values for the following parameters:

Storage Group for Tablespaces. Enter the name of the table storage group.

Storage Group for Indexes. Enter the name of the index storage group.

4KB Buffer Pool Name

16KB Buffer Pool Name

Indicate the values for the following parameters:

4KB Buffer Pool Name. Enter the 4-KB buffer pool name for your tablespaces or accept the default name, BP1. This buffer pool should already be activated and have access to it granted by the DBA.

16KB Buffer Pool Name. Enter the 16-KB buffer pool name for your tablespaces or accept the default name, BP16K1. This buffer pool should already be activated and have access to it granted by the DBA.

32KB Buffer Pool Name

Index Buffer Pool Name

Indicate the values for the following parameters:

32KB Buffer Pool Name. Enter the 32-KB buffer pool name for your tablespaces or accept the default name, BP32K1. This buffer pool should already be activated and have access to it granted by the DBA.

Index Buffer Pool Name. Enter the buffer pool name for indexes or accept the default name, BP2. This buffer pool should already be activated and have access to it granted by the DBA.

Database Name Prefix

Enter the prefix for your target database name. The default prefix is SIDB.

This prefix consists of up to four of the first characters in the names of your logical Siebel Databases. This prefix must start with a letter and cannot contain any special characters. All database names end in numbers.

Storage Control File

Enter the directory path and name for the storage control file created by this process:

    • Windows: Accept the default value displayed in the Storage Control File field (this is the DBSRVR_ROOT\DB2390 directory, for example, D:\DBSRVR_ROOT\DB2390\storage.ctl) or use the Browse button to navigate to a different directory.
    • UNIX: Enter the path to your storage control file.

Log Output Directory

Accept the default or enter the directory name. If the directory does not exist, it will be created. Do not use special characters such as spaces, slashes, or symbols in the name of the log output.

CAUTION:  If you are restarting or recovering a previous incomplete upgrade, do not change the Log Output Directory that you previously selected.

  1. Save the configuration information you have entered and launch the Siebel Upgrade Wizard as described in the following topics:
  2. When the Siebel Upgrade Wizard appears, click OK. The Upgrade Wizard connects to the z/OS host, extracts the storage control file and copies it to the file that you specified (see Table 15).

    If you selected the Extract from Catalog and merge with Template option, this process reads the database catalog and merges your prior custom database layout with one of the 7.8 Siebel Database layout templates (located in the DBSRVR_ROOT\db2390 directory). New objects take a layout from one of the layout templates.

    NOTE:  If you choose a Siebel storage control file template that includes partitioning, and the existing database schema does not include partitioning, by default, the existing database objects are not partitioned in the storage control file generated (that is, the database catalog overrides the templates) unless you specify the table names in the override input file (override.inp).

    By default, new tables are created as one-table-per-database to prevent concurrency and locking errors.

Once the merged storage control file is created, you must verify it against either the source or target database. See Validating the Extracted Storage Control File for information on this task.

Upgrade Guide for DB2 UDB for z/OS