DB2 - Problem description
Problem IC71791 | Status: Closed |
DB2AGENT TRAP SIG#11 IN SQLOCRASHONCRITICALMEMORYVALIDATIONFAILU RE WITH SQLR_GET_STATS_COMMAND IN THE CALLSTACK | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
During statistics collection, the db2agent might trap with sig#11 in sqloCrashOnCriticalMemoryValidationFailure with sqlr_get_stats_command in the callstack. The statistics collection might be a collection that was initiated by the user via a RUNSTATS command, or might be a collection that was initiated by automatic statistics collection if this feature is enabled for the database. For the problem to occur, the application heap usage must have been constrained. A sample callstack that might be observed is: ossDumpStackTrace OSSTrapFile6dumpExEmi OSSTrapFile4dumpEmi sqlo_trce sqloEDUCodeTrapHandler sqloCrashOnCriticalMemoryValidationFailure sqlofmblkEx sqlofmblkPv sqlr_get_stats_command sqlrrsta sqlrr_runstats_DA Prior to the trap, the db2diag log might have application heap messages, for example: 2010-10-07-01.34.33.373569-240 I68291A582 LEVEL: Error PID : 757924 TID : 3600 PROC : db2sysc 0 INSTANCE: svtdbm5 NODE : 000 DB : SVTLNX2 APPHDL : 0-65 APPID: *N0.svtdbm5.101007052723 AUTHID : SVTDBM5 EDUID : 3600 EDUNAME: db2agent (SVTLNX2) 0 FUNCTION: DB2 UDB, relation data serv, sqlr_get_stats_command, probe:200 RETCODE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH "No memory available in 'Application Heap'" DIA8301C No memory available in the application heap. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * During statistics collection, the db2agent might trap with * * sig#11 in sqloCrashOnCriticalMemoryValidationFailure with * * sqlr_get_stats_command in the callstack. The statistics * * collection might be a collection that was initiated by the * * user via a RUNSTATS command, or might be a collection that * * was initiated by automatic statistics collection if this * * feature is enabled for the database. For the problem to * * occur, the application heap usage must have been * * constrained. * * * * A sample callstack that might be observed is: * * * * ossDumpStackTrace * * OSSTrapFile6dumpExEmi * * OSSTrapFile4dumpEmi * * sqlo_trce * * sqloEDUCodeTrapHandler * * sqloCrashOnCriticalMemoryValidationFailure * * sqlofmblkEx * * sqlofmblkPv * * sqlr_get_stats_command * * sqlrrsta * * sqlrr_runstats_DA * * * * Prior to the trap, the db2diag log might have application * * heap messages, for example: * * * * 2010-10-07-01.34.33.373569-240 I68291A582 LEVEL: * * Error * * PID : 757924 TID : 3600 PROC : * * db2sysc 0 * * INSTANCE: svtdbm5 NODE : 000 DB : * * SVTLNX2 * * APPHDL : 0-65 APPID: * * *N0.svtdbm5.101007052723 * * AUTHID : SVTDBM5 * * EDUID : 3600 EDUNAME: db2agent (SVTLNX2) 0 * * FUNCTION: DB2 UDB, relation data serv, * * sqlr_get_stats_command, probe:200 * * RETCODE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH * * "No memory available in 'Application Heap'" * * DIA8301C No memory available in the application * * heap. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.5 fix pack 7. * **************************************************************** | |
Local Fix: | |
Increasing application heap might reduce the likelihood of experiencing this problem. | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows | |
Solution | |
This problem was first fixed in DB2 version 9.5 fix pack 7. | |
Workaround | |
see LOCAL FIX | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.10.2010 15.11.2010 15.11.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP7 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.7 | |
9.5.0.7 |