
Data Consistency, Recovery, and Migration 4-9
Setting Consistency-Checking Variables
The problem text briefly describes the type of consistency error. The process#
identifiestheOnLinedatabaseserverprocessidentificationnumber(pid)that
encountered the error. The user# is the user identification number as defined
in the UNIX/etc/passwd file. The addressis the addressof the database server
process in shared memory. Locate the user login and try to discover the
operationbeingperformedat thetimeoftheerror.Thisinformationmightbe
valuable for diagnostic purposes.
Most of the general consistency-checking messages are followed by
additionalinformationthatusuallyincludesthetblspacewheretheerrorwas
detected. If this information isavailable, run tbcheck -cD onthe database or
table. If this check verifies the inconsistency, unload the data from the table,
drop the table, re-create the table, and reload the data. Otherwise, no other
action is needed.
A message isalso sent tothe applicationprocess.The content ofthe message
depends on the operation in progress. However in all cases the following
ISAM error is returned:
-105 ISAM error: bad isam file format
Tip: Chapter 8, which describes the messages that might appear in the OnLine
message log, provides additional details about the objectives and contents of consis-
tency-checking messages.
Setting Consistency-Checking Variables
OnLinerecognizesfourvariablesintheuser’senvironment,which,whenset,
directOnLinetopreservediagnosticinformationwheneveraninconsistency
is detected orwheneverOnLine enters into anabortsequence. To take effect,
the variables must be set at the time that the user’s OnLine database server
process is started.
You decide whether your users set these variables. Diagnostic output can
consume a large amount of disk space. (The exact content depends on the
environment variables set and your UNIX system.) The elements of the
output could include a copy of shared memory and/or a core dump of the
database server process.
Comentarios a estos manuales