DB2 - Problembeschreibung
Problem IC82244 | Status: Geschlossen |
ENOMEM ERROR ON DB2ACD PROCESS COULD LEAD TO NON-FATAL ASSERTION FAILED | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problembeschreibung: | |
If db2acd process hit a ENOMEM issue, NON-FATAL ASSERTION FAILED messages might be dumped in db2diag.log, for example: 2012-03-09-01.30.03.287000+540 I1224328F464 LEVEL: Severe PID : 2764 TID : 3052 PROC : db2fmp64.exe INSTANCE: DB2INST1 NODE : 000 APPID : *LOCAL.DB2.120308170015 FUNCTION: DB2 UDB, global services, sqlzAssertFailed, probe:10 DATA #1 : String, 157 bytes NON-FATAL ASSERTION FAILED!!! ASSERTION EXPRESSION: Invalid block eye-catcher (0xDEAD055E) found at: SOURCE FILENAME: ../include/atmStats.h LINE NUMBER: 210 There can be multiple reasons for the underlying out of memory condition. One common reason is that the db2acd memory requirement exceeds the data ulimit of the userid which performed the db2start operation. In the example above, the ossErrorMemoryAnalysis probe indicates the db2acd process was running with a data ulimit of 128MB. It is likely that the out of memory condition experienced by db2acd will not occur if the instance is restarted by an userid with sufficient data ulimit. Depending on the operating system involved, the diaglog messages above might differ, and the facilities to control resource limits might also differ. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade DB2 UDB version 9.1 fix pack 12. * **************************************************************** | |
Local-Fix: | |
On operating systems which support user resource limits, restart the DB2 instance from a user account whose data ulimit is sufficient, such as unlimited. | |
Lösung | |
Problem was first fixed in DB2 UDB Version 9.1 Fix Pack 12. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 25.03.2012 02.08.2012 02.08.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.1.FP12 | |
Problem behoben lt. FixList in der Version | |
9.1.0.12 |