DB2 - Problembeschreibung
Problem IC78050 | Status: Geschlossen |
DEBUG DIAGNOSTICS CODE for LOAD TERMINATE OPERATION ON TABLES WITH LOBS | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
This APAR is being used to improve problem diagnostics for a potential DB2 issue that is still at problem determination stage. AFTER LOAD LOB/LF DATA FAILURE, FOLLOWED BY LOAD TERMINATE, SUBSEQUENT LOAD MAY FAIL WITH SQLDXE_BADPAGE 1) Pre-requisites: - Recoverable database - Table with LOB/LF column - Failed LOAD command (INSERT/REPLACE) - Successful LOAD TERMINATE After LOAD FAILURE, followed by LOAD TERMINATE is done, some LOB pages may not have been completely cleaned up. Please note that table is fully accessible after TERMINATE. However, a subsequent LOAD against this table may fail with a bad LOB page error. You can identify that LOAD TERMINATE was run in the scenario with below example: (Failed LOAD): 2011-07-12-12.03.47.037585+540 I64449596A539 LEVEL: Error PID : 29032720 TID : 118291 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-31282 APPID: *LOCAL.db2inst1.110803015837 AUTHID : DB2INST1 EDUID : 118291 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 DATA #1 : String, 113 bytes LOADID: 118291.2011-07-12-11.40.31.681591.0 (10;100) sqluv_rollback , 0, 93, Detected in file:sqluvutl.C, Line:937 2011-07-12-12.03.47.037731+540 I64450136A462 LEVEL: Severe PID : 29032720 TID : 118291 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-31282 APPID: *LOCAL.db2inst1.110803015837 AUTHID : DB2INST1 EDUID : 118291 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, database utilities, sqlu_register_table_load, probe:1132 MESSAGE : Load Error: Error loading partition. (LOAD TERMINATE): 2011-07-12-13.27.26.417998+540 I64672391A619 LEVEL: Warning PID : 29032720 TID : 113667 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-5149 APPID: *LOCAL.db2inst1.110803123533 AUTHID : DB2INST1 EDUID : 113667 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, database utilities, sqluCreateLoadListElement, probe:20 DATA #1 : LOADID, PD_TYPE_LOADID, 51 bytes LOADID: 113667.2011-07-12-13.26.26.186104.0 (10;100) MESSAGE : The Load synchronization element is now being reused. No user intervention is required. 2011-07-12-13.27.53.818982+540 I64673011A470 LEVEL: Warning PID : 29032720 TID : 113667 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-5149 APPID: *LOCAL.db2inst1.110803123533 AUTHID : DB2INST1 EDUID : 113667 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, database utilities, sqluvtld_route_in, probe:839 DATA #1 : <preformatted> Starting LOAD operation (S) (1) (T). | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All platforms * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * * Upgrade V9.7 FP5 * **************************************************************** | |
Local-Fix: | |
To avoid the bad page errors, avoid doing LOAD TERMINATE on tables identified in the Pre-requisites above. Instead, you must run RESTART. Affected tables can be cleaned up by running a REORG TABLE ... LONGLOBDATA against them. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows | |
Lösung | |
Enhanced diagnostics will be included in V9.7 FP5 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 10.08.2011 20.10.2012 02.08.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP5 | |
Problem behoben lt. FixList in der Version | |
9.7.0.7 |