IBM 000-8697 User Manual
Data Consistency, Recovery, and Migration
4-9
Setting Consistency-Checking Variables
The problem text briefly describes the type of consistency error. The process#
identifies the OnLine database server process identification number (pid) that
encountered the error. The user# is the user identification number as defined
in the
identifies the OnLine database server process identification number (pid) that
encountered the error. The user# is the user identification number as defined
in the
UNIX
/etc/passwd
file. The address is the address of the database server
process in shared memory. Locate the user login and try to discover the
operation being performed at the time of the error. This information might be
valuable for diagnostic purposes.
operation being performed at the time of the error. This information might be
valuable for diagnostic purposes.
Most of the general consistency-checking messages are followed by
additional information that usually includes the tblspace where the error was
detected. If this information is available, run tbcheck -cD on the 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.
additional information that usually includes the tblspace where the error was
detected. If this information is available, run tbcheck -cD on the 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 is also sent to the application process. The content of the message
depends on the operation in progress. However in all cases the following
depends on the operation in progress. However in all cases the following
ISAM
error is returned:
-105 ISAM error: bad isam file format
Tip:
, 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.
tency-checking messages.
Setting Consistency-Checking Variables
OnLine recognizes four variables in the user’s environment, which, when set,
direct OnLine to preserve diagnostic information whenever an inconsistency
is detected or whenever OnLine enters into an abort sequence. To take effect,
the variables must be set at the time that the user’s OnLine database server
process is started.
direct OnLine to preserve diagnostic information whenever an inconsistency
is detected or whenever OnLine enters into an abort sequence. 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
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.
database server process.