|
Problem IC81753
|
Status: Closed |
ALTER TABLESPACE SIZE TO A LARGE VALUE ON RAW DEVICE MAY CAUSE DB2 TRAP |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
In some cases, altering tablespace size to a large value on raw
device will cause the integer overflow error. Sometimes, when
doing resize tablespace container operation, if the total size
of the extended tablespace in KB is larger than 4294967295(4TB)
which is the max value of 32bit integer, db2 may trap during the
undo phase.
Some similar entries could be wriiten in db2diag.log. A record
with totalPages less than contSize, e.g (totalPages = 512000000)
< (contSize = 1342242816) may indicate the overflow occurs.
2012-02-27-15.40.17.930364+480 I30756777E570 LEVEL: Error
PID : 14453 TID : 47246594795840PROC :
db2sysc 0
INSTANCE: db2inst NODE : 000 DB : SAMPLE
APPHDL : 0-25844 APPID:
*LOCAL.db2inst2.121025001347
AUTHID : DB2INST2
EDUID : 62566 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbResizeDMSContainer,
probe:30
MESSAGE : ZRC=0x80020046=-2147352506=SQLB_BAD_CONT_SZ "bad
container size"
DATA #1 : String, 45 bytes
totalPages = 512000000, contSize = 1342242816
2012-02-27-15.40.17.930502+480 I30757348E482 LEVEL: Error
PID : 14453 TID : 47246594795840PROC :
db2sysc 0
INSTANCE: db2inst NODE : 000 DB : SAMPLE
APPHDL : 0-25844 APPID:
*LOCAL.db2inst2.121025001347
AUTHID : DB2INST
EDUID : 62566 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbUndo, probe:0
MESSAGE : ZRC=0x80020046=-2147352506=SQLB_BAD_CONT_SZ "bad
container size"
2012-02-27-15.40.17.930587+480 I30757831E480 LEVEL: Severe
PID : 14453 TID : 47246594795840PROC :
db2sysc 0
INSTANCE: db2inst NODE : 000 DB : SAMPLE
APPHDL : 0-25844 APPID:
*LOCAL.db2inst2.121025001347
AUTHID : DB2INST
EDUID : 62566 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, data management, sqldmund, probe:764
RETCODE : ZRC=0x80020046=-2147352506=SQLB_BAD_CONT_SZ "bad
container size"
2012-02-27-15.40.17.947179+480 I30759963E502 LEVEL: Severe
PID : 14453 TID : 47246594795840PROC :
db2sysc 0
INSTANCE: db2inst NODE : 000 DB : SAMPLE
APPHDL : 0-25844 APPID:
*LOCAL.db2inst2.121025001347
AUTHID : DB2INST
EDUID : 62566 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, DRDA Application Server, sqljsSignalHandler,
probe:10
MESSAGE : DIA0505I Execution of a component signal handling
function has begun. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL Platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2 v97 fp6 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
In some cases, altering tablespace size to a large value on raw
device will cause the integer overflow error. Sometimes, when
doing resize tablespace container operation, if the total size
of the extended tablespace in KB is larger than 4294967295(4TB)
which is the max value of 32bit integer, db2 may trap during the
undo phase.
Some similar entries could be wriiten in db2diag.log. A record
with totalPages less than contSize, e.g (totalPages = 512000000)
< (contSize = 1342242816) may indicate the overflow occurs.
2012-02-27-15.40.17.930364+480 I30756777E570 LEVEL: Error
PID : 14453 TID : 47246594795840PROC :
db2sysc 0
INSTANCE: db2inst NODE : 000 DB : SAMPLE
APPHDL : 0-25844 APPID:
*LOCAL.db2inst2.121025001347
AUTHID : DB2INST2
EDUID : 62566 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbResizeDMSContainer,
probe:30
MESSAGE : ZRC=0x80020046=-2147352506=SQLB_BAD_CONT_SZ "bad
container size"
DATA #1 : String, 45 bytes
totalPages = 512000000, contSize = 1342242816
2012-02-27-15.40.17.930502+480 I30757348E482 LEVEL: Error
PID : 14453 TID : 47246594795840PROC :
db2sysc 0
INSTANCE: db2inst NODE : 000 DB : SAMPLE
APPHDL : 0-25844 APPID:
*LOCAL.db2inst2.121025001347
AUTHID : DB2INST
EDUID : 62566 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbUndo, probe:0
MESSAGE : ZRC=0x80020046=-2147352506=SQLB_BAD_CONT_SZ "bad
container size"
2012-02-27-15.40.17.930587+480 I30757831E480 LEVEL: Severe
PID : 14453 TID : 47246594795840PROC :
db2sysc 0
INSTANCE: db2inst NODE : 000 DB : SAMPLE
APPHDL : 0-25844 APPID:
*LOCAL.db2inst2.121025001347
AUTHID : DB2INST
EDUID : 62566 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, data management, sqldmund, probe:764
RETCODE : ZRC=0x80020046=-2147352506=SQLB_BAD_CONT_SZ "bad
container size"
2012-02-27-15.40.17.947179+480 I30759963E502 LEVEL: Severe
PID : 14453 TID : 47246594795840PROC :
db2sysc 0
INSTANCE: db2inst NODE : 000 DB : SAMPLE
APPHDL : 0-25844 APPID:
*LOCAL.db2inst2.121025001347
AUTHID : DB2INST
EDUID : 62566 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, DRDA Application Server, sqljsSignalHandler,
probe:10
MESSAGE : DIA0505I Execution of a component signal handling
function has begun. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC84452
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.03.2012
18.05.2012
18.05.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
