ASAP 3.1 Server Manual

HP NonStop ASAP Server Manual Page 262 of 360
 You must define partitioning keys (made up of a combination of the SYSNO
and KEY values) in ascending order for each partition. That is, the
partitioning key for partition 2 must be greater than the partitioning key for
partition 1, the key for partition 3 must be greater than the key for partition
2, and so on.
 If Format 2 is on, you cannot specify MAXEXTENTS for a secondary
partition. The collector ignores any such values, and the secondary
partitions are created with the MAXEXTENTS value specified for the base
partition.
 The PRIEXT, SECEXT, and MAXEXTENTS values specified for partitions
of the DEFAULT entity are used when creating partitions for all other
entities, unless you supply specific values when you define the new
partitions. For example, partition 1 of the DEFAULT entity is defined with
PRIEXT = 100. This value is used when creating partition 1 of the CPU
entity unless the definition of partition 1 of the CPU entity overrides the
DEFAULT setting.
 The Collector automatically adjusts the length of the partitioning keys
specified for the partitions of a given entity to ensure that all partition key
lengths are the same for that entity. This is accomplished by null-filling
partition keys for the maximum partition key length specified.
For example, if the KEY for partition 1 of the APP entity is defined as FT,
the KEY for partition 2 is SWIFT, and the key for partition 3 is TXN, the
maximum partitioning key length is 5 bytes (from partition 2, for SWIFT).
Therefore, the Collector appends null bytes to the partitioning keys for
partitions 1 and 3, so their lengths are also 5 bytes. The partitioning key for
partition 1 becomes [FT, 0, 0, 0], and the partitioning key for partition 3
becomes [TXN, 0, 0]. This occurs in the Collector when the database is
created, so the keys are not shown in this adjusted form in the ASAP CI.
The SYSNO value is considered to be part of the key and, if specified, is
factored into the key length.
 Issuing a SET DB command resets all partitioning attributes.
 The Collector uses only valid partition descriptions (those listed as Valid in
the SET PARTITION command output) when creating the database. For
any entity, the Collector uses all valid partition descriptions found,
beginning at partition 0, until it encounters an invalid description. All further
partition descriptions for that entity are ignored.
For example, if partitions 0, 1, 2, and 4 are valid for the CPU entity, but
partition 3 is invalid, only partition descriptions 0, 1, and 2 are used when