Bookshelf Home | Contents | Index | Search | PDF

Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS > Preparing for Implementation on the DB2 Host >

Setting Up the Subsystem

---

Set up a separate subsystem for Siebel eBusiness Applications, particularly for larger deployments, for the following reasons:

DSNZPARM optimization. The DSNZPARMs used with this release of Siebel eBusiness Applications are optimized for the Siebel application, but might not be optimal for use with non-Siebel applications. It is recommended, but not required, that you run the Siebel eBusiness Application on its own subsystem.
OLTP and OLAP characteristics. Siebel applications possess the characteristics of both an OLTP and OLAP application. However, most other vendors' applications have the characteristics of either one or the other.
Use of Dynamic SQL. Virtually all Siebel eBusiness Applications use dynamic SQL, whereas most other applications typically use static SQL and bound plans.
DB2 maintenance requirements. This release of Siebel eBusiness Applications requires the application of a number of maintenance activities that are documented in informational APAR ii13487.

CAUTION:  It is crucial that you apply everything in informational APAR ii13487 to the subsystem that you set up. Otherwise, operating anomalies and unpredictable behavior might occur.

System catalog locking during Siebel Database recovery. Recovery of the Siebel Schema might affect other applications on a shared DB2 subsystem if the system catalog becomes locked during the recovery process. Because recovery typically requires the restoration of all Siebel table spaces, locking could last many hours.

Bookshelf Home | Contents | Index | Search | PDF