Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT02439 Status: Closed

BACKUP WILL FAIL WITH FILE SIZE TOO BIG IF LOB FILE IN A SMS TABLESPACE
REACHES OVER 2TB IN SIZE.ONLY

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
2013-11-12-22.05.13.169689-300 E2598462E1214       LEVEL: 
Warning 
PID     : 37121                TID  : 140724754441984PROC : 
db2sysc 0 
INSTANCE: db2inst2             NODE : 000          DB   : SAMPLE 
APPHDL  : 0-34107              APPID: 
*LOCAL.db2inst2.131113030221 
AUTHID  : DB2INST2 
EDUID   : 1620                 EDUNAME: db2bm.649.0 (SAMPLE) 0 
FUNCTION: DB2 UDB, oper system services, sqloFileStats, probe:20 
MESSAGE : ZRC=0x870F014C=-2029059764=SQLO_FSIZE_BIG "file size 
too big." 
DATA #1 : String, 17 bytes 
File size too big 
DATA #2 : File size, 8 bytes 
2201767641088 
CALLSTCK: 
  [0] 0x00007FFFF3AA4C9F pdLog + 0xD7 
  [1] 0x00007FFFF3E97E2A sqloFileStats + 0x352 
  [2] 0x00007FFFF43DD75C 
_Z14sqlbGetObjSizeP16SQLB_OBJECT_DESCP12SQLB_GLOBALSiPm + 0x234 
  [3] 0x00007FFFF48072B9 
_Z12sqlubReadLOBP14SQLU_BUFMAN_CBP8SQLD_TCB + 0x121 
  [4] 0x00007FFFF48058CF _Z12sqlubReadSMSP14SQLU_BUFMAN_CB + 
0x949 
  [5] 0x00007FFFF48029B9 _Z11sqlubBMContP14SQLU_BUFMAN_CB + 
0x5EF 
  [6] 0x00007FFFF48020B1 _Z8sqlubbufP8sqeAgent + 0x5B5 
  [7] 0x00007FFFF460B782 
_Z26sqleSubCoordProcessRequestP8sqeAgent + 0xAA 
  [8] 0x00007FFFF3BA0096 _ZN8sqeAgent6RunEDUEv + 0x63E 
  [9] 0x00007FFFF40C2B8D _ZN9sqzEDUObj9EDUDriverEv + 0x6D 
 
2013-11-12-22.05.13.220911-300 I2599677E517        LEVEL: Severe 
PID     : 37121                TID  : 140724754441984PROC : 
db2sysc 0 
INSTANCE: db2inst2             NODE : 000          DB   : SAMPLE 
APPHDL  : 0-34107              APPID: 
*LOCAL.db2inst2.131113030221 
AUTHID  : DB2INST2 
EDUID   : 1620                 EDUNAME: db2bm.649.0 (SAMPLE) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlbGetObjSizeInPages, 
probe:510 
MESSAGE : ZRC=0x8002003C=-2147352516=SQLB_BAD_CONTAINER_PATH 
          "Bad container path" 
 
2013-11-12-22.05.13.223389-300 E2600195E564        LEVEL: Severe 
PID     : 37121                TID  : 140724754441984PROC : 
db2sysc 0 
INSTANCE: db2inst2             NODE : 000          DB   : SAMPLE 
APPHDL  : 0-34107              APPID: 
*LOCAL.db2inst2.131113030221 
AUTHID  : DB2INST2 
EDUID   : 1620                 EDUNAME: db2bm.649.0 (SAMPLE) 0 
FUNCTION: DB2 UDB, database utilities, sqlubReadLOB, probe:1847 
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes 
-298 
DATA #2 : Hexdump, 8 bytes 
0x00007FFC96451718 : 3C00 0280 3C00 0000 
<...<... 
 
2013-11-12-22.05.13.227589-300 E2600760E875        LEVEL: Severe 
PID     : 37121                TID  : 140724754441984PROC : 
db2sysc 0 
INSTANCE: db2inst2             NODE : 000          DB   : SAMPLE 
APPHDL  : 0-34107              APPID: 
*LOCAL.db2inst2.131113030221 
AUTHID  : DB2INST2 
EDUID   : 1620                 EDUNAME: db2bm.649.0 (SAMPLE) 0 
FUNCTION: DB2 UDB, database utilities, sqlubReadLOB, probe:1847 
MESSAGE : SQL0298N  Bad container path. 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -298   sqlerrml: 2 
 sqlerrmc: 60 
 sqlerrp : sqlubRea 
 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: 
 
2013-11-12-22.05.23.699425-300 E2601636E436        LEVEL: Severe 
PID     : 37121                TID  : 140727564625664PROC : 
db2sysc 0 
INSTANCE: db2inst2             NODE : 000          DB   : SAMPLE 
APPHDL  : 0-34107              APPID: 
*LOCAL.db2inst2.131113030221 
AUTHID  : DB2INST2 
EDUID   : 649                  EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:865 
MESSAGE : Backup terminated.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 V10.1 users                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 Fix Pack 5 or higher.                   * 
****************************************************************
Local Fix:


Solution


Fixed in DB2 V10.1 Fix Pack 5.


Workaround


not known / see Local fix


Timestamps


Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

11.06.2014
17.07.2015
17.07.2015


Problem solved at the following versions (IBM BugInfos)




Problem solved according to the fixlist(s) of the following version(s)


10.1.0.5

FixList