DB2 - Problembeschreibung
Problem IC81923 | Status: Geschlossen |
WHEN USEREXIT RETURNS ERROR, DB2 MAY REPORT AN INCORRECT LOGFILE NAME IN ERROR MESSAGE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
If the USEREXIT script encounters an error while retrieving a log file, DB2 may generate db2diag.log entries and an SQL return code that contains and incorrect error message (specifically, the previous log-file number) For example, if the userexit encounters an error while retrieving log-file S0003553.LOG, it may generate db2diag.log entries that show error messages containing both logs 3553 and 3552, like so: 2012-02-08-00.54.14.079971-300 E43736E609 LEVEL: Error PID : 4433 TID : 46995750250816PROC : db2sysc 0 INSTANCE: ngrcdi51 NODE : 000 EDUID : 845 EDUNAME: db2logmgr (IBMSTG1) 0 FUNCTION: DB2 UDB, data protection services, sqlpgUserexitLogAdminMsg, probe:1180 MESSAGE : ADM1835E The user exit program returned an error when retrieving log file "S0003553.LOG" to "/home/ngrcdi51/daraja/tbspace/logs/" for database "IBMSTG1". The error code that was returned by the user exit program to the database manager was: "1". 2012-02-08-00.54.14.313009-300 E49165E692 LEVEL: Error PID : 23874 TID : 46912565804912PROC : db2bp INSTANCE: ngrcdi51 NODE : 000 FUNCTION: DB2 UDB, database utilities, sqludTransportRollforward, probe:693 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1268 sqlerrml: 25 sqlerrmc: 1 S0003552.LOG IBMSTG1 0 sqlerrp : SQLUFROL sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0x00000000 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: However, the final sqlcode returned back to the caller may simply contain the incorrect log-file (3552 in this example): SQL1268N Roll-forward recovery stopped due to error "1" while retrieving log file "S0003552.LOG" for database "IBMSTG1" on node "0". | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * If the USEREXIT script encounters an error while retrieving * * a * * log file, DB2 may generate db2diag.log entries and an SQL * * return * * code that contains and incorrect error message * * (specifically, * * the previous log-file number) * **************************************************************** * RECOMMENDATION: * * Upgrade to v9.7 fixpak 7 * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 08.03.2012 30.10.2012 30.10.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7. | |
Problem behoben lt. FixList in der Version | |
9.7.0.7 |