IBM 000-8697 Manuale Utente
4-10
IBM Informix OnLine Database Server Administrator’s Guide
Setting Consistency-Checking Variables
(A core dump is an image of the database server process in memory at the time
that the inconsistency was detected. Some core dumps include a copy of
shared memory. To determine the size of your OnLine shared memory, refer
to the kilobyte information listed in any tbstat header.)
that the inconsistency was detected. Some core dumps include a copy of
shared memory. To determine the size of your OnLine shared memory, refer
to the kilobyte information listed in any tbstat header.)
Administrators with disk space constraints might prefer to write a script that
detects the presence of diagnostic output in a specified directory and sends
the output to tape. This approach preserves the diagnostic information and
minimizes the amount of disk space used.
detects the presence of diagnostic output in a specified directory and sends
the output to tape. This approach preserves the diagnostic information and
minimizes the amount of disk space used.
GCORE
The
GCORE
environment variable is used with
UNIX
operating systems that
support the gcore utility. If
GCORE
is set, the OnLine database server process
calls gcore whenever the server process detects an inconsistency or initiates
an abort sequence. The gcore utility directs the server process to dump core
to the current directory (or the directory specified by
an abort sequence. The gcore utility directs the server process to dump core
to the current directory (or the directory specified by
DUMPDIR
) and continue
processing.
The core dump output generated by gcore is saved to the file core.pid.cnt.
The pid value is the OnLine database server process identification number.
The cnt value is incremented each time this process encounters an inconsis-
tency. The cnt value can range from 1 to 4. After 4, separate core dumps are
saved to files, and no more files are created. If the server process continues to
detect inconsistencies in this section of code, errors are reported to the
OnLine message log (and perhaps to the application), but no further
diagnostic information is saved.
The pid value is the OnLine database server process identification number.
The cnt value is incremented each time this process encounters an inconsis-
tency. The cnt value can range from 1 to 4. After 4, separate core dumps are
saved to files, and no more files are created. If the server process continues to
detect inconsistencies in this section of code, errors are reported to the
OnLine message log (and perhaps to the application), but no further
diagnostic information is saved.
If you set
GCORE
and your
UNIX
system does not support gcore, messages in
the OnLine message log indicate that an attempt was made to dump core, but
the expected file was not found. (If your
the expected file was not found. (If your
UNIX
system does not support gcore,
set
DUMPCORE
instead.)
Set the
GCORE
environment variable at the system prompt or in your .login
or .cshrc (C shell) or your .profile (Bourne shell) file as follows:
C shell:
setenv GCORE
Bourne shell:
GCORE =
export GCORE