Hierarchy
⤷ BC-DB-DB2 (Application Component) DB2 for z/OS
⤷ STU2 (Package) CCMS for DB2 for OS/390
Basic Data
Data Element | DB2BASEPARTNR |
Short Description | Partition number of the base table (0 for non-partitioned) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DB2PARTNO | |
Data Type | INT2 | 2-byte integer, only for length field before LCHR or LRAW |
Length | 5 | |
Decimal Places | 0 | |
Output Length | 5 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Base Part |
Medium | 15 | Base Partition |
Long | 34 | Partition number of the base table |
Heading | 34 | Partition number of the base table |
Documentation
Definition
LOB table spaces hold large object data such as graphics, video, or very large text strings. A LOB table space is always associated with the table space that contains the logical LOB column values. The table space that contains the table with the LOB columns is called the base table space.
This relationship is organized in such a way, that each column containing a LOB value needs an auxiliary table (and corresponding auxiliary LOB table space) created for the LOB column. A base table space that is partitioned must have one auxiliary table for each partition of each LOB column.
The actual LOB data is stored in these auxiliary tables. The base table only contains a row identifier for each row and an indicator column for each of its LOB columns.
Since for each column and partition of the base table a separate auxiliary table has to be created, the partition number of the base table space for which the LOB TS has been created is stored in this column.
History
Last changed by/on | SAP | 20070813 |
SAP Release Created in | 700 |