DB2 - Problembeschreibung
Problem IC74861 | Status: Geschlossen |
ADM4500W - PACKAGE CACHE OVERFLOW MESSAGE GETS LOGGED AS ERROR IN WINDOWS EVENT LOGS. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
Starting from DB2 V95, a package cache overflow warning message gets logged in as ERROR in Windows Event logs as follows. Event Type: Error Event Source: DB2-0 Event Category: None Event ID: 4 Date: 21.02.2011 Time: 08:00:02 User: N/A Computer: S-BDB02 Description: 2011-02-21-08.00.02.327007 Instance:DB2 Node:000 PID:5716(db2syscs.exe) TID:200 Appid:*LOCAL.DB2.110221072654 access plan manager sqlra_cache_mem_please Probe:100 Database:VUINDEX ADM4500W A package cache overflow condition has occurred. There is no error but this indicates that the package cache has exceeded the configured maximum size. If this condition persists, you should perform additional monitoring to determine if you need to change the PCKCACHESZ DB configuration parameter. You could also set it to AUTOMATIC. It should get logged in as WARNING in the Windows Event logs. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 * **************************************************************** * PROBLEM DESCRIPTION: * * ADM4500W - PACKAGE CACHE OVERFLOW MESSAGE GETS LOGGED AS * * ERROR * * IN WINDOWS EVENT LOGS. * **************************************************************** * RECOMMENDATION: * * Upgrade to v95fp8 * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows | |
Lösung | |
After fix: ADM4500W - PACKAGE CACHE OVERFLOW MESSAGE GETS LOGGED AS WARNING IN WINDOWS EVENT LOGS. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC74888 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 04.03.2011 05.07.2011 05.07.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP8 | |
Problem behoben lt. FixList in der Version | |
9.5.0.8 |