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

Extracting the Storage Control File


After you have created the staging database but before you begin to generate the upgrade files, you must extract the storage control file from the staging database and merge it with a Siebel CRM template. You do this using the Database Configuration Wizard Extract from Catalog and Merge with Template option. Depending on the type of upgrade you are performing, assign one of the following names to the extracted storage control file:

  • Development environment upgrade: storage_upg_dev.ctl
  • Production environment upgrade: storage_upg_prod.ctl.

This task is a step in Process of Preparing the Storage Layout of the Schema.

To extract the storage control file

  1. Run the Database Configuration Wizard.

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

  2. Enter the information shown in Table 9 when prompted by the Database Configuration Wizard. Collect this information and verify it before running the utility.
  3. Save the information you have entered and launch the Upgrade Wizard as described in Running the Database Configuration Wizard to Perform Upgrade Tasks.

    The database catalog is read and your prior custom database layout is merged with one of the Siebel database layout templates for the current release (located in the DBSRVR_ROOT\db2390 directory). New objects take a layout from one of the layout templates. By default, new tables are created as one-table-per-database to prevent concurrency and locking errors.

    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).

    Before using the merged storage control file, you must verify it against the staging database. For information on this task, see Validating the Extracted Storage Control File.

Information Required for the Database Configuration Wizard Extract Option

Table 9 lists the information you must enter to run the Database Configuration Wizard Extract and Merge option.

Table 9. Information Required for the Database Configuration Wizard Extract and Merge Option
Field Name or Menu
Required Information

Siebel Server Directory

The absolute path of the directory where the Siebel Server is installed, for example, C:\sba81\siebsrvr (Windows) or siebel/siebsrvr (UNIX). For UNIX, do not enter the string $SIEBEL_ROOT.

Siebel Database Server Directory

The absolute path of the directory where the Siebel Database Configuration Utilities are installed, for example C:\sba81\dbsrvr (Windows) or siebel/dbsrvr (UNIX).

RDBMS Platform

Choose IBM DB2 UDB for z/OS.

Siebel Database Operation

Choose Run Database Utilities.

Database Utilities Selection

Choose Configure Database

Database Configuration Options

Choose Extract Storage File to extract a storage control file.

Extract Options

Choose the Extract from Catalog and Merge with Template option.

This option preserves your existing layout. This option merges storage layout information from the database you specify 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.

Base Language

On the Base Language screen, specify which language serves as the primary language for the Siebel database.

If you installed a single Siebel language pack, the Base Language screen is not displayed.

ODBC Data Source Name

Verify the ODBC name for connecting to the staging Siebel database.

Windows: To find the name of your ODBC data source, navigate to the Start menu and select Settings, Control Panel, Administrative Tools, and then Data Sources (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.

Database User Name

Database Password

Enter the user name and password for the Siebel administrator of the staging database.

NOTE:  The staging database user name (user ID) must have authorization to set the CURRENT SQLID.

Siebel Schema Qualifier

Enter the eight-character identifier that designates the Siebel schema for your staging 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.

 

Database Encoding

Specify whether your database is UNICODE or Non-UNICODE.

If you select Non-UNICODE, click Next, then indicate whether your DB2 subsystem is ASCII or EBCDIC.

Environment Type

Indicate whether your database environment is production or development.

Select Siebel Schema Layout

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

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 table spaces.

Default Table Space

Enter the name of the default table space.

Storage Group for Table Spaces

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

8KB Buffer Pool Name

16KB Buffer Pool Name

32KB Buffer Pool Name

Index Buffer Pool Name

 

 

Indicate the values for the following parameters:

4KB Buffer Pool Name. Enter the 4-KB buffer pool name for your table spaces or accept the default name, BP1. The DBA must have activated this buffer pool and granted access to it.

8 KB Buffer Pool Name. Enter the 8-KB buffer pool name for your table spaces or accept the default name, BP8K1. The DBA must have activated this buffer pool and granted access to it.

16KB Buffer Pool Name. Enter the 16-KB buffer pool name for your table spaces or accept the default name, BP16K1. The DBA must have activated this buffer pool and granted access to it.

32KB Buffer Pool Name. Enter the 32-KB buffer pool name for your table spaces or accept the default name, BP32K1. The DBA must have activated this buffer pool and granted access to it.

Index Buffer Pool Name. Enter the buffer pool name for indexes or accept the default name, BP2. The DBA must have activated this buffer pool and granted access to it.

Database Name Prefix

Enter the prefix to assign to the names of logical Siebel databases on the target database. The default prefix is SIDB.

NOTE:  The prefix can consist of a maximum of four characters in length, it must start with a letter, and it cannot contain any special characters. The database name prefix must be the same for all database objects in the Siebel schema because the prefix identifies an object as belonging to the Siebel schema. Siebel utilities can recognize and use Siebel objects only if they follow Siebel naming conventions.

Storage Control File

Enter the directory path and name for the storage control file created by this process. You must accept the default value displayed in the Storage Control File field; this varies depending on the type of upgrade you are performing:

  • Development environment upgrade: storage_upg_dev.ctl
  • Production environment upgrade: storage_upg_prod.ctl.

Log Output Directory

Accept the default directory (dbconfig_extract_merge_mf) or enter a different 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.

Siebel Database Upgrade Guide for DB2 for z/OS Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.