invispix 10x10
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 IT40806 Status: Closed

TRUNCATING TABLE SPACE FILES (SQLSPCS.1/2) LARGER THAN 4GB MAY FAIL

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
Certain Db2 operations will truncate tablespace files SQLSPCS.1
and SQLSPCS.2 under the cover. When the tablespace files are
larger than 4GB, i.e., containing more than 16,384 tablespaces,
the truncation may fail with an error
SQLO_FSIZE_BIG, and this error may in turn fail the Db2
operation.

In particular,
1. In non-pureScale, drop the tablespace with the highest
tablespace ID will fail with SQL1034C.

DB21034E  The command was processed as an SQL statement because
it was not a
valid Command Line Processor command.  During SQL processing it
returned:
SQL1034C  The database was damaged, so all applications
processing the
database were stopped.  SQLSTATE=58031

The associated db2diag.log message:

2022-05-01-15.00.33.774343+120 E109149E2175          LEVEL:
Warning
PID     : 153116               TID : 139955821078080 PROC :
db2sysc 0
INSTANCE: XXXXXXX              NODE : 000            DB   :
XXXXX
APPHDL  : 0-26                 APPID:
XXXXXXXXXXXXXX.220501125934
AUTHID  : XXXXXXX              HOSTNAME: XXXXXXXXXX
EDUID   : 19                   EDUNAME: db2agent (XXXXX) 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
5242355712
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
  [0] 0x00007F0B616EDE41 sqloFileStats + 0x711
  [1] 0x00007F0B63494011 _ZN12sqlzCtrlFile11GetFileSizeEPj +
0x111
  [2] 0x00007F0B5970F152 _Z16sqlbPoolTblTruncbP12SQLB_GLOBALS +
0x152
  [3] 0x00007F0B597119C3 _Z18sqlbPoolTblDelPooltjP12SQLB_GLOBALS
+ 0x433
  [4] 0x00007F0B5991A034 _Z15sqlbDropPoolActtiP12SQLB_GLOBALS +
0x464
  [5] 0x00007F0B59BDA13E
_Z8sqldmpndP8sqeAgentiPcP9SQLP_LSN8PmP15SQLD_RECOV_INFO + 0x18DE
  [6] 0x00007F0B6180CAA6 _Z8sqlptpplP8sqeAgentiPb + 0x8F6
  [7] 0x00007F0B617E4FD9
_Z8sqlpxcm1P8sqeAgentP15SQLXA_CALL_INFOi + 0x16F9
  [8] 0x00007F0B61EB8BB9
_Z12sqlrrcom_dpsP8sqlrr_cbiiP15SQLXA_CALL_INFO + 0x5C9
  [9] 0x00007F0B61EBBCEF _Z8sqlrrcomP8sqlrr_cbii + 0x5EF
  [10] 0x00007F0B61E7D278 _Z12sqlrr_commitP14db2UCinterface +
0x408
  [11] 0x00007F0B5F89883A
_Z16sqljs_ddm_rdbcmmP14db2UCinterfaceP13sqljDDMObject + 0x1AA
  [12] 0x00007F0B5F86E5F1
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U
Cinterface + 0x181
  [13] 0x00007F0B5F86FEEC
_Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb +
0x3EC
  [14] 0x00007F0B5F867731
/home/db2inst1/sqllib/lib64/libdb2e.so.1
+ 0x8DC1731
  [15] 0x00007F0B5F86B6A5
_Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 0xCF5
  [16] 0x00007F0B5F1B5C79 _ZN8sqeAgent6RunEDUEv + 0x639
  [17] 0x00007F0B6348EFF4 _ZN9sqzEDUObj9EDUDriverEv + 0x1A4
  [18] 0x00007F0B617122E9 sqloEDUEntry + 0x2A9
  [19] 0x00007F0B6844DEA5 /lib64/libpthread.so.0 + 0x7EA5
  [20] 0x00007F0B559D79FD clone + 0x6D

2. In pureScale, a Db2 operation that is performed with super
exclusive access may fail at starting pools time, for instance,
offline backup fails with the following error and stack:

SQL0902C  A system error occurred. Subsequent SQL statements
cannot be
processed. IBM software support reason code: "".  SQLSTATE=58005

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
4296015872
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
  [0] 0x00007F53CC3A3E41 sqloFileStats + 0x711
  [1] 0x00007F53CE14A011 _ZN12sqlzCtrlFile11GetFileSizeEPj +
0x111
  [2] 0x00007F53C43C5152 _Z16sqlbPoolTblTruncbP12SQLB_GLOBALS +
0x152
  [3] 0x00007F53C43C837C _Z14sqlbStartPoolsP12SQLB_GLOBALS +
0x78C
  [4] 0x00007F53C44E7A53 sqlbinit + 0x345A
  [5] 0x00007F53C9FDBB8E
_Z8sqledintP8sqeAgentP16sqeLocalDatabaseP5sqlcacPciPbm + 0x120E
  [6] 0x00007F53C9FFBD80
_ZN16sqeLocalDatabase12FirstConnectEP8SQLE_BWARcP8sqeAgentP8sqlo
_gmtiiPb + 0x7AB0
  [7] 0x00007F53C9FBEEC4
_ZN8sqeDBMgr23StartUsingLocalDatabaseEP8SQLE_BWAP8sqeAgentRccP8s
qlo_gmtPb + 0x1424
  [8] 0x00007F53C9E97A2D
_ZN14sqeApplication13AppStartUsingEP8SQLE_BWAP8sqeAgentccP5sqlca
Pc + 0x7FD
  [9] 0x00007F53C9E9E9EB
_Z22sqleProcessConnectTypeP14db2UCinterfaceP8SQLE_BWAP8sqeAgentP
5sqlcaP22SQLELOST_STATUS_VECTOR + 0x8B
  [10] 0x00007F53C9E9FFEB
_ZN14sqeApplication13AppLocalStartEP14db2UCinterface + 0x7BB
  [11] 0x00007F53CA2A7B11 _Z11sqlelostWrpP14db2UCinterface +
0x41
  [12] 0x00007F53CA2A6CE5 _Z14sqleUCengnInitP14db2UCinterfacet +
0x715
  [13] 0x00007F53CA2AB77F sqleUCagentConnect + 0x30F
  [14] 0x00007F53CA5C7933
_Z18sqljsConnectAttachP13sqljsDrdaAsCbP14db2UCinterface + 0x233
  [15] 0x00007F53CA537B3D
_Z16sqljs_ddm_accsecP14db2UCinterfaceP13sqljDDMObject + 0x6D
  [16] 0x00007F53CA523948
_Z17sqljsParseConnectP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UCint
erface + 0x208
  [17] 0x00007F53CA52633A
_Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb +
0x83A
  [18] 0x00007F53CA51D731
/home/db2inst1/sqllib/lib64/libdb2e.so.1
+ 0x8DC1731
  [19] 0x00007F53CA5216A5
_Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 0xCF5
  [20] 0x00007F53C9E6BC79 _ZN8sqeAgent6RunEDUEv + 0x639
  [21] 0x00007F53CE144FF4 _ZN9sqzEDUObj9EDUDriverEv + 0x1A4
  [22] 0x00007F53CC3C82E9 sqloEDUEntry + 0x2A9
  [23] 0x00007F53D3103EA5 /lib64/libpthread.so.0 + 0x7EA5
  [24] 0x00007F53C068D9FD clone + 0x6D
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Db2 Version 11.5                                             *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 Version 11.5.8.0                              *
****************************************************************
Local Fix:
If drop the tablespace with the highest tablespace ID fails and
brings down the database, run crash recovery, after it completes
successfully, the tablespace with the highest tablespace ID will
be dropped successfully.

There is no good workaround for the other case.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Db2 Version 11.5                                             *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 Version 11.5.8.0                              *
****************************************************************
Comment
Problem was first fixed in Db2 Version 11.5.8.0
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.05.2022
12.05.2022
12.05.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
invispix 10x10
invispix 10x10
Versions InfomailVersions Infomail

Versions Infomail

Product LifecycleProduct Lifecycle

Lifecycle

Current BugsCurrent Bugs

Current Bugs

Bug ResearchBug Research

Bug Research

Bug FixlistsBug Fixlists

Bug Fixlists

invispix 10x10