DB2 - Problembeschreibung
Problem IC99405 | Status: Geschlossen |
SQLPGRETRIEVELOGFILE MAY REPORT WRONG CHAIN NUMBER IN DB2DIAG.LOG IN ERROR SCENARIO | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
In case there was an error while retrieving a log file then sqlpgRetrieveLogFile function may report a wrong (misleading) chain number in db2diag.log: 2014-02-05-16.25.38.502270+060 E228924A518 LEVEL: Warning PID : 43385156 TID : 30586 PROC : db2sysc 0 INSTANCE: db2inst3 NODE : 000 DB : SAMPLE HOSTNAME: localhost EDUID : 30586 EDUNAME: db2logmgr (HRS) 0 FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4165 MESSAGE : ADM1847W Failed to retrieve log file "S0459820.LOG" on chain "0" to "/export/db2inst3/overflow/NODE0000/LOGSTREAM0000/LOGSTREAM0000/ ". The reported chain "0" in the above example might not be the correct/current chain number. DB2 attempts to retrieve the correct log chain, it just fails to report it in case the sqlpgRetrieveLogFile() failed. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix Pack 4. * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 10.5 Fix Pack 4. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 17.02.2014 09.09.2014 09.09.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.4 |