ASAP 2.8 Server Manual

ASAP Conversational Interface Commands
HP NonStop ASAP Server Manual—522303-007
6-108
SET Command
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 creating the
CPU database. Partition description 4 is ignored, even though it is valid,
because description 3 is invalid.
•
If partitioning is enabled for an entity, the Valid column of the SET PARTITION
output indicates the status of each configured partition with one of these
values:
Value Indicates That the Partition Definition Is...
Used by
Collector
to Create
Database?
Yes Valid. Yes
No-Vol Invalid because no volume was specified. No
No-Sys/Key Invalid because no KEY or SYSNO was specified. No
No-Vol,Sys/Key Invalid because no VOLUME and no KEY or
SYSNO was specified
No
No-Prior Inv Invalid because a prior partition definition was
invalid. The definition itself is correct, but a
previous partition definition for the entity is
incomplete.
No
??-Key Seq Questionable because the partitioning key (a
combination of the SYSNO and KEY values) is
less than the partitioning key of a prior partition
definition. Fix the key sequencing.
Yes, with
errors
??-Dup Vol Questionable because a prior partition definition
uses the same volume. Each partition must be on
a separate volume.
Yes, with
errors
??-Vol Unknown Questionable because the specified volume does
not exist on the system on which ASAP is running.
Either you gave a remote name for a partition
volume or a configuration is being prepared on
one system for another. Specify an existing
volume.
Yes, with
errors