Fixes are available
APAR status
Closed as fixed if next.
Error description
When a container is deleted / dropped from one tablespace and the same container is added to another tablespace, (as can be seen below): - db2 "alter tablespace tbsp1 drop(file '/home/nishansi/cont2')" - db2 "alter tablespace tbsp2 add(file '/home/nishansi/cont2' 2000)" and the same operation when replayed using logs during rollforward, results in the following error being displayed on the CLP: SQL1042C An unexpected system error occurred. SQLSTATE=58004 The following error gets logged in the db2diag.log: 2008-11-26-00.01.43.334641-300 I15350C2737 LEVEL: Severe PID : 942114 TID : 1 PROC : db2redom (TEST) INSTANCE: nishansi NODE : 000 DB : TEST APPHDL : 0-25 APPID: *LOCAL.nishansi.081126050144 FUNCTION: DB2 UDB, buffer pool services, sqlbContainerTagIsValid, probe:200 MESSAGE : iTag(CONTAINER_TAG) DATA #1 : Hexdump, 512 bytes 0x2FF1DCE8 : 4442 3243 4F4E 5400 0000 0213 7C7E EE46 DB2CONT.....|~.F 0x2FF1DCF8 : 0000 0004 0000 0001 0000 0001 0000 0001 ................ 0x2FF1DD08 : 0000 00BB 8C26 5445 5354 2020 2020 006E .....&TEST .n 0x2FF1DD18 : 6973 6861 6E73 6900 0000 0000 0000 00BB ishansi......... 0x2FF1DD28 : 8C26 2F68 6F6D 652F 6E69 7368 616E 7369 .&/home/nishansi 0x2FF1DD38 : 2F6E 6973 6861 6E73 692F 4E4F 4445 3030 /nishansi/NODE00 0x2FF1DD48 : 3030 2F53 514C 3030 3030 312F 0000 0000 00/SQL00001/.... 0x2FF1DD58 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DD68 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DD78 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DD88 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DE08 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DE18 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DE28 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DE38 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DE48 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DE58 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DE68 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DE78 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DE88 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DE98 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DEA8 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DEB8 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DEC8 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x2FF1DED8 : 0000 0000 0000 0000 0000 0000 5845 E20C ............XE.. 2008-11-26-00.01.43.335115-300 I18088C447 LEVEL: Error PID : 942114 TID : 1 PROC : db2redom (TEST) INSTANCE: nishansi NODE : 000 DB : TEST APPHDL : 0-25 APPID: *LOCAL.nishansi.081126050144 FUNCTION: DB2 UDB, buffer pool services, sqlbDMSAddContainerRequest, probe:869 RETCODE : ZRC=0x80020039=-2147352519=SQLB_CONTAINER_IN_USE "Container is already being used" 2008-11-26-00.01.43.335418-300 I18536C443 LEVEL: Error PID : 942114 TID : 1 PROC : db2redom (TEST) INSTANCE: nishansi NODE : 000 DB : TEST APPHDL : 0-25 APPID: *LOCAL.nishansi.081126050144 FUNCTION: DB2 UDB, buffer pool services, sqlbDMSAddContainerRequest, probe:869 MESSAGE : Error acquiring container 1 (/home/nishansi/cont2) for tbsp 4. Rc = 80020039 The error occurrs because the rebalancing is still being performed on the first tablespace and the container is still being used, and at the same time the container is tried to be added to second tablespace, and since the rollforward operation is not complete (forward and backward phases), the container continues to remain attached to the first tablespace and hence the error is encountered.
Local fix
Executing the rollforward command twice after some interval of time will solve this problem.
Problem summary
Fixed in V91fp8
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
IZ40574
Reported component name
DB2 UDB WSE AIX
Reported component ID
5765F3500
Reported release
910
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-12-22
Closed date
2009-10-09
Last modified date
2009-10-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R810 PSY
UP
R820 PSY
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]
Document Information
Modified date:
04 October 2021