ASAP 2.8 Messages Manual

HP NonStop ASAP Messages Manual—429917-004
1-91
Cause. The Collector encountered an error parsing partitioning settings read from the
partition control file due to illegal data in the file. The file might be corrupt or invalid.
Effect. The Collector logs the error and continues to process the control file. If the
entire file is corrupt or invalid, the database is created using default settings. If some
entries in the file are good, they are used to create the database.
Recovery. Shut down and restart the Collector to re-create the partition control file.
2037
error
file-system error number. If greater than 0, indicates the encountered file-system
error. If less than 0, indicates an internal ASAP error.
Cause. The Collector could not write status information to the partition control file after
reading the file. Most likely a security violation occurred.
Effect. The Collector logs the error and continues to run normally. Status information
is not written to the control file, but this does not otherwise affect Collector operations.
Recovery. Depends on error. If an internal ASAP error occurred, contact your
support representative.
2038
entity-suffix
suffix for an ASAP entity.
Cause. The Collector encountered an unknown ASAP database entity suffix. The
cause is an internal Collector error, possibly due to a versioning inconsistency.
Effect. The Collector does not create a database for the specified entity.
Recovery. Contact your support representative.
2039
filename
database file that cannot be created.
Collector could not write partition ctl file error
Unknown suffix entity-suffix
CreatePart filename file-error partition-index