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

Table Objects in Storage Control Files


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

[Object 8005]
Type = Table
Name = S_ORG_EXT
Database = SIDB1465
Tablespace = H1465000
Clobs = No

The Table object illustrated in this topic translates into the following DDL output:

CREATE TABLE SIEBTO.S_ORG_EXT (
ROW_ID VARCHAR(15) NOT NULL,
CREATED TIMESTAMP DEFAULT NOT NULL,
CREATED_BY VARCHAR(15) NOT NULL,
...

VAT_REGN_NUM VARCHAR(30),
DIRECTIONS LONG VARCHAR) IN SIEBTO.H1465000 /

Siebel Business Applications include one template for each encoding scheme when partitioning is used and one template for each encoding scheme for nonpartitioning.

Most tables use page-level locking by default, but a few use row-level locking. Table 8 lists tables that use row-level locking.

NOTE:  LockSize is not defined on the table level, but in the corresponding table space.

Table 8. Tables with Row-Level Locking
Row-Level Locking

S_ESCL_ACTN_REQ

S_ESCL_LOG

S_ESCL_REQ

S_DOCK_TXN_LOG

S_DOCK_TXN_LOGT

S_DOCK_TXN_SET

S_DOCK_TXN_SETT

Table 9 lists tables that use table-level locking.

Table 9. Tables with Table-Level Locking
Table-Level Locking

S_DOCK_INIT_ITEM

S_DOCK_INITM_XX

Implementing Siebel Business Applications on DB2 UDB for z/OS Copyright © 2008, Oracle. All rights reserved.