DB2 FOR LUW / DB2FORLUW / 970 - DB2

In DB2 V9.7 Fixpack 1 , an online backup may incorrectly 
 
fail with error code SQL2048 and reason code rc = 5. 
 
 
The db2diag.log will report a message similar to this : 
 
2009-12-24-10.19.01.354587+060 E1437271A646       LEVEL: Severe 
PID     : 1266018              TID  : 29836       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE 
APPHDL  : 0-227                APPID: 
*LOCAL.db2inst1.091224091838 
AUTHID  : DB2INST1 
EDUID   : 29836                EDUNAME: db2bm.10539.3 (SAMPLE) 0 
FUNCTION: DB2 UDB, database utilities, sqlubResizeBufSpace, 
probe:472 
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes 
-2048 
DATA #2 : Hexdump, 28 bytes 
0x0000000111A80998 : FFFF F800 444D 532E 5441 424C 4553 5041 
....DMS.TABLESPA 
0x0000000111A809A8 : 4345 2E44 4154 4100 0000 0005 
CE.DATA..... 
 
 
an alternative symptom is that the backup may hang and stop 
progressing. 
This is not detectably by external symptoms, but running db2pd 
-utilities will confirm that there is no progress being made. 
DB2 support can identify this issue when call stacks are 
collected and the db2bm edu  stacks repeatedly has this 
signature : 
 
  sqloCSemP 
  sqlbpfParallelDirectReadV 
  sqlbDirectReadBlock 
  sqlubReadDMS 
  sqlubBMCont 
  sqlubbuf 
  sqleSubCoordProcessRequest 
  ...

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* An online database backup may hang, or may return            * 
* errorSQL2048 RC = 5 in V9.7 Fix Pack 1                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the database server to V9.7 Fix Pack 2               * 
****************************************************************

Take an offline backup 
Increasing the buffersize ( -BUFFER--buffer-size-' option ) may 
avoid the error, whilst increasing the number of prefetch EDU's 
( NUM_IOSERVERS db cfg parameter ) may avoid the hang situation, 
however there are no guarantees that this will avoid the 
problem, it just reduces the likelihood of it happening.

DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

The problem has first been fixed in V9.7 Fix Pack 2

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC66809 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

25.12.2009
10.06.2010
18.02.2011

9.7.FP2