Default Objects in Storage Control Files

The first object in the storage control file is a Defaults object. If no actual value exists for a given object, but a value for that object is required by a DB2 statement, then the default value is either derived from the Defaults object or inherited from a higher-level object.

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

[Object 1]
Type            = Defaults
Name           = Defaults
Database         = $DbnamePrefix0000
Tablespace        = SIEBTS00
Stogroup         = $StogroupTables
IndexStogroup      = $StogroupIndexes
IndexBp          = $IndexBufferPool
Bufferpool         = $4KBufferPool
LockSize           = Page
SegSize          = 32
LockMax           = 0
PriQty             = 48
SecQty            = 1440
PctFree           = 17
FreePage        = 0
Compress          = Yes
Define     = No
Erase      = No
CCSID      = $DbType

You can override default values for any given object by explicitly defining the value in the object. For example, if the Tablespace object does not contain PriQty or SecQty values, then these values are inherited from the PriQty and SecQty values defined in the Defaults object. However, if the values are defined in the Tablespace object, then the explicitly provided value overrides the default and is used in the output DDL.

Note: If you create an extension table in Siebel Tools and use the apply process without creating new underlying objects for this table in the storage control file, then the necessary storage layout is derived from the default definitions. For information about the apply process, see Roadmap for Creating Custom Extensions to the Siebel Schema.