DUMPCNT configuration parameter (UNIX)

Use the DUMPCNT configuration parameter to specify the number of assertion failures in a thread for which a database server dumps shared memory or generates a core file by calling the gcore utility.

onconfig.std value: DUMPCNT 1
values: Positive integers or a number of comma-separated fields as described in the Usage section.
units: Number of shared memory dumps or core files that can be generated by each thread.
takes effect: After you edit your onconfig file and restart the database server.; When you reset the value dynamically in your onconfig file by running the onmode -wf command.; When you reset the value in memory by running the onmode -wm command.

Usage

An assertion failure occurs when the database server cannot continue normal processing.

Assertion failures can generate as many core files or shared memory dumps as permitted by the DUMPCNT configuration parameter. Further assertion failures generate errors in the message log and perhaps to the application, but no further diagnostic information is saved.

>>-DUMPCNT--+----thread_count-----------------------+-----><
            |                                       |
            |  '----------------------------,----'  |
            |  |                                 |  |
            '--+-+-thrdlimit-=-thread_count----+-+--'
                 |                             |
                 +-instlimit-=-instance_count--+
                 |                             |
                 +-insttime-=-time_period------+
                 |                             |
                 '-interval-=-time_interval----'

Table 1. Options for the DUMPCNT configuration parameter value
Field	Values
thrdlimit	The thread_count value is a positive integer that represents the maximum number of shared memory dumps to be created by each thread. It also represents the maximum number of core files to be created by each thread if the DUMPGCORE onconfig parameter is enabled. The default is `1`.
instlimit	The instance_count value is a positive integer that represents the maximum number of shared memory dumps to be created by all threads in the database server instance in the time period specified by the insttime field. The default is `0` which implies no limit.
insttime	The time_period value is a positive integer to represent the period of time in seconds to be applied to the instlimit field. When the count of shared memory dumps reaches the limit set by instlimit then no further dumps will be created until the expiry of the time period. The start of the time period is the completion of the first shared memory dump. The default value is `0` which means that there is no time period and in this case, the instlimit field becomes an absolute count on the number of shared memory dumps to be created which remains in effect until the database server is restarted.
interval	The time_interval value is a positive integer representing the minimum time interval in seconds between the completion of one shared memory dump before another is permitted. The default value is `300 seconds`.

Note: When used, the fields instlimit, insttime, and interval are valid only for determination of creating a shared memory dump, not a core file. They are effective only when managed shared memory dumps are enabled by the DUMPSHMEM onconfig parameter. Furthermore, in order to prevent the loss of useful diagnostic information, they are not applied for an AFCRASH event.