Implementing Siebel Business Applications on DB2 UDB for z/OS > Configuring the Database Layout > Siebel Objects >

Database Objects in Storage Control Files

In the Siebel database storage layout, each table resides in its own table space, and each table space resides in its own database. The number of databases you receive depends on which modules your organization purchases. You can regroup table spaces in databases, as required for your enterprise.

NOTE:  The maximum number of databases is 64,000 per one DB2 subsystem.

The following example illustrates what a Database object looks like in the storage control file:

[Object 4]
Type = Database
Name = SIDB2532
LockSize = Page

The Database object illustrated in this section translates into the following DDL output:

CREATE DATABASE SIDB2532 CCSID ASCII BUFFERPOOL BP1 /

In Siebel Business Applications, CCSID is defined on the database level only. CCSID is always taken from the Defaults object.

LockSize is not used in the CREATE DATABASE statement, because LockSize is a default value for all table spaces that belong to a given database.

The names of databases in storage control files are comprised of two parts. The first part of the name is a variable, $DbnamePrefix. The second part of the name is a four-digit number. This four-digit number in the database name is the same four-digit number used in the table space name that resides in this database. You can substitute the database name prefix with a literal value up to four characters long (for example, SIDB) that conforms to your organization's naming convention. You can change the value of the database name prefix either during the installation process or by changing it in the storage control file. For more information on the table space name structure, see Table Space Naming Conventions.