Implementing Siebel Business Applications on DB2 for z/OS > Migrating a Siebel Database to Unicode Format > Requirements for Migrating the Siebel Database to Unicode >

Converting the Storage Control File to Unicode

As part of the process of migrating your ASCII or EBCDIC database to a Unicode format, you must convert the physical layout of your source database so that it supports Unicode. This involves expanding the size of the columns in the schema tables; the extent to which a column must be expanded is determined by the column type and length.

Once you have converted the storage control file to Unicode, you must validate the converted file. This topic outlines both tasks.

To convert the source storage control file to Unicode and validate it

1. Open the Siebel Database Storage Configurator as described in About Modifying Storage Control Files.
2. Click the Import tab, navigate to the directory containing your existing Siebel schema storage control file (the file you extracted in Step 4), and double-click this file to import it.
3. When the import process is completed, a message appears stating that you have imported the storage control file successfully. Click OK.
4. When the message, Please enter default values for your system appears, accept the default values and click Set.
5. You are prompted to indicate whether you want to import row lengths. Click Yes.
6. Navigate to the directory containing the renamed schema.ddl file for your schema (for example, ddl_ascii.ctl or ddl_ebcdic.ctl) and double-click this file to import it (this is the file you extracted and renamed in Step 5).

   The Siebel Database Storage Configurator reads the ddl_codepage.ctl file to determine the type and length of each table column in the schema.

7. When the ddl_codepage.ctl file is imported successfully, click OK.
8. When the message Would you like to import row counts is displayed, select No.
9. Click the Structures tab, then the Database tab.
10. (Optional) Change the database name prefix of all the databases listed (for example, SIDB) to the database name prefix you want to use in your Unicode schema (for example, SIEB). The database name prefix must be the same for all database objects in the Siebel schema.
11. Click Functions, and then Convert to Unicode.
12. Click the Convert button.

    If a message is displayed stating that the spreadsheet has already been converted to Unicode, click the Structures tab and change entries in the CCSID column from Unicode to ASCII, then select the Convert to Unicode tab again.

13. When the storage control file has been converted, click the Home tab and then click the Export button.
14. Rename your converted storage control file, for example, storage_uni.ctl, and save it. The Siebel Database Storage Configurator validates the file.
15. Click OK and a storage control file is created for your Siebel database with an expanded Unicode schema.
16. If errors occur while the Unicode storage control file is being exported, a message is displayed and the values that need to be reviewed are highlighted.

    Make any corrections that are required before exporting the file again. For further information on this task, see Modifying a Storage Control File Using the Database Storage Configurator.

17. Validate the converted Unicode storage control file using the Database Configuration Utility Validate Storage File option.

    For information on validating a storage control file using the Database Configuration Utility, see Validating an Extracted or Modified Storage Control File.

    Ensure that you specify the following values:

    • Configure Database option. Select the Validate Storage File option
    • Batch or Foreground Mode. Choose the Batch - Generate Unload/Load option
    • Database values. Specify database parameter values for your existing Siebel ASCII or EBCDIC database
    • Schema File. Specify the ddl_codepage.ctl file you extracted in Step 5
    • Storage Control File. Specify the storage control file you have just converted to Unicode, for example, storage_uni.ctl
18. Depending on the outcome of the validation process, do one of the following:
    • If the validation process completes successfully, proceed to Generating the Unicode Migration Files.
    • If the validation process fails because of buffer pool errors, follow the procedure in Recovering from Buffer Pool Errors, then run the validation process again.

      Errors generated during the validation process are written to a log file in the SIEBSRVR_ROOT\log\dbconfig_validate_mf\output directory (Windows) or the SIEBSRVR_ROOT/log/dbconfig_validate_mf/output directory (UNIX).