Upgrade Guide for DB2 UDB for z/OS > Database and UI Upgrade Planning > Planning Your Upgrade >

Considering Code Page Support

Siebel Systems supports both ASCII- and EBCDIC-based coded character set IDs (CCSIDs) on DB2 for z/OS. Development databases, however, require ASCII code pages, because databases with EBCDIC code pages do not support two critical procedures in a development environment upgrade:

• Merging prior configuration changes into a new custom configuration repository
• Compiling a new Siebel repository file (.srf file) from the new repository

Additional limitations on databases with EBCDIC code pages include the following:

• Siebel Web Client migration is not supported
• Siebel Dun & Bradstreet server components are not supported

Before you conduct an upgrade, carefully read Siebel Release Notes on My Oracle Support for information about known restrictions. For guidelines about choosing the code page for your subsystem, see Implementing Siebel Business Applications on DB2 UDB for z/OS.

About Code Page Conversion

Siebel Systems supports the ASCII 5348 and EBCDIC 1140 code pages on DB2 for z/OS (see Siebel System Requirements and Supported Platforms on Oracle Technology Network for further information). If your current Siebel release runs on a different code page, you must migrate to one of the supported code pages before upgrading to Siebel 7.8.

Siebel applications that are upgraded to Siebel v7.7.x or later, and that run on unsupported code pages, do not support all the characters that were supported before the upgrade, for example, the euro symbol.

Ensure you schedule sufficient time to perform and test the code page conversion before beginning the upgrade. For advice and assistance on converting DB2 code pages, contact IBM.