DUMPGCORE

onconfig.std
value

0

range of values

0 = Do not dump gcore.
1 = Dump gcore.

takes effect

When shared memory is initialized

utilities

onutil

refer to

Collecting diagnostic information in the chapter on consistency checking in the IBM Informix: Administrator's Guide

DUMPGCORE is used with operating systems that support gcore. If you set DUMPGCORE, but your operating system does not support gcore, messages in the database server message log indicate that an attempt was made to dump a core image, but the database server cannot find the expected file. (If your operating system does not support gcore, you can set DUMPCORE instead, but do so with caution. See DUMPCORE for details.)

If DUMPGCORE is set, the database server calls gcore whenever a virtual processor encounters an assertion failure. The gcore utility directs the virtual processor to dump a core image to the directory that DUMPDIR specifies and continue processing.

The core dump output that gcore generates is saved to the file core.pid.cnt. The pid value is the process identification number of the virtual processor. The cnt value is incremented each time that this process encounters an assertion failure. The cnt value can range from 1 to the value of DUMPCNT. After that, no more core files are created. If the virtual processor continues to encounter assertion failures, errors are reported to the message log (and perhaps to the application), but no further diagnostic information is saved.

To modify the DUMPGCORE parameter dynamically, use the onutil SET command. Example:

% onutil
1> SET DUMPGCORE 1;