DB2 - Problembeschreibung
Problem IC97850 | Status: Geschlossen |
DB2DIAG.LOG IS FILLED WITH -443 WARNING MESSAGES | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
This scenario can occur when we are trying to call UTL_FILE.FREMOVE with Invalid Path. Applying this APAR will remove the extra info in db2diag.log Following warning message will be dumped in the db2diag.log 2013-09-09-10.07.15.303595-300 E1221656E857 LEVEL: Warning PID : 12060 TID : 47036938316096PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-36520 APPID: 140.95.202.156.56501.130917010024 AUTHID : TESTER EDUID : 31425 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, runtime interpreter, sqlriTrustedTruncateTokensUserSqlState, probe:100 DATA #1 : signed integer, 4 bytes -443 DATA #2 : String with size, 5 bytes 5UA06 DATA #3 : String with size, 30 bytes SYSIBMADM.UTL_FILE.IMP_FREMOVE DATA #4 : String with size, 20 bytes UTL_FILE_IMP_FREMOVE DATA #5 : String with size, 21 bytes UTL_FILE.INVALID_PATH DATA #6 : signed integer, 4 bytes 68 DATA #7 : signed integer, 4 bytes 20 DATA #8 : signed integer, 4 bytes 20 DATA #9 : signed integer, 4 bytes 21 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix Pack 3. * **************************************************************** | |
Local-Fix: | |
N/A | |
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 3. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 21.11.2013 25.08.2014 25.08.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.4 |