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

Object Naming Conventions


When you work with Siebel objects you must understand Siebel object naming conventions. An understanding of object naming conventions allows you to keep track of existing Siebel objects and to successfully create and maintain your own objects.

If you understand Siebel naming conventions, you can more easily identify underlying datasets (VSAM files); for example, the name of the underlying datasets for H0401000 table space might look like Q10E.DSNDBC.SIEBTO.H0401000.I0001.A001 where the fourth node represents the table space name.

NOTE:  Siebel utilities are able to recognize and use custom objects only if they follow Siebel naming conventions; therefore, it is strongly recommended that you use the Siebel naming conventions for objects that you create.

Table Space Names

The table space naming convention applies to all Siebel tables, whether you created the tables or the tables were shipped as part of your Siebel eBusiness Application.

Tables are named with eight characters (for example, H0401000) that consist of three elements (in the following order):

  1. A leading letter (H, V, F, or S) designates the product group that the table belongs to.
  2. The four-digit number that was assigned to the base table when you created it, for example, 0401. (This number cascades down to table spaces, auxiliary tables, and auxiliary indexes.)
  3. NOTE:  For custom tables, use a four-digit number greater than 6000.

  4. The ending three-digit number depends on the database storage layout and size of the buffer pool. Use the following matrix to determine which prefix to use.
  5.  
    One table per table space
    Multiple tables per table space
    Partitioned
    000
    000
    Nonpartitioned


    000
    004
    016
    032

CAUTION:  When you create new custom tables and auxiliary indexes, use the prefix S, follow it with a unique four-digit number greater than 6000, then end with the three-zero suffix (000), for example, S6001000. This maintains object naming conventions, and prevents custom objects from being created with random names.

Table names are stored in the repository table S_TABLE, and the table number is stored in the Group Code column (GROUP_CD) in S_TABLE. Table names can be viewed in Siebel Tools under Table > Object.

Auxiliary Object Names

Names for auxiliary objects such as character large objects (CLOBs) must follow a naming convention that provides space for the auxiliary table, table space, and index for each partition of a partitioned CLOB.

Auxiliary objects are named with eight characters (for example, A0401000) that consist of three elements (in the following order):

  1. A leading letter designates the product group that the table belongs to. Use the following matrix to determine which prefix to use.
  2.  

    Tables
    Table Spaces
    Table Indexes
    Horizontal
    X
    A
    I
    SIA and Custom ("S")
    Y
    B
    J
    Default Group Names Assigned
    to Objects with No Leading "S"
    Z
    C
    K

  3. A four-digit number that uniquely identifies the table space, for example, 0401.
  4. NOTE:  Default numbering of auxiliary objects starts from 0001.

  5. The ending three-digit number must be all zeros: 000. (Every name ends in 000.)

Triggers

Partitioning Triggers are named with eight characters (for example, PTH0401) that consist of three elements (in the following order):

  1. The leading two letters must be PT to designate that this is a partitioning trigger.
  2. The third letter (H, V, F, or S) designates the product group or component that the trigger belongs to.
  3. The ending four-digit number uniquely identifies the trigger based on the table number, for example, 0401.
  4. The trigger name is normally related to a corresponding table space name; for example, the trigger name PTH0401 relates to the table space name H0401000.


 Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS 
 Published: 18 April 2003