Siebel Database Upgrade Guide for DB2 for z/OS > Creating the Siebel Staging Database >

Creating the Staging Database Schema DDL Files


To create the staging database, you must generate schema DDL files from the target database. You then use these files and the storage control file you extracted from the target database to create the staging database. The following procedure describes how to generate the DDL files.

To generate the DDL files used to create the staging database

  1. Run the Database Configuration Wizard. See About Running the Database Configuration Wizard on Windows and About Running the Database Configuration Wizard Under UNIX.
  2. Specify the following options:
    1. Upgrade Options:
      • Development environment: Upgrade Siebel Database Schema (upgrep).
      • Production environment: Upgrade Siebel Database Schema (upgrep + upgphys).
    2. Upgrade Process: zSeries Staging of Files for Upgrade.
    3. Storage Control File: Specify the name of the storage control file you extracted in Step a.
    4. DB2 Subsystem Name:
      • The DB2 subsystem name you specify for the staging database must be different to the DB2 subsystem name of the database to be upgraded (target database).
      • It is recommended that the DB2 subsystem name you specify for the staging or target database is the same as the ODBC Data Source Name (DSN) you specify for the database. If the database ODBC DSN is not the same as the DB2 subsystem name, you can create a new ODBC DSN for the staging or target database or amend the existing ODBC DSN.

        See Information Required by the Database Configuration Wizard.

  3. Launch the Siebel Upgrade Wizard. See Starting the Siebel Upgrade Wizard.

    SQL commands are executed on your existing database to generate the staging database files. The Upgrade Wizard then stops (Pause #0). For a list of the files generated on the midtier by the Siebel Upgrade Wizard, see Upgrade Files for Siebel Business Applications.

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