DB2 - Problem description
| Problem IC64064 | Status: Closed |
A TABLE IN UNAVAILABLE STATE IS ABLE TO BE REDISTRIBUTED. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
A table in unavailable state is able to be redistributed. This
can cause a situation in which the table is not able to be
redistributed or dropped. The table is essentially in drop
pending and redistribute pending state.
The following messages will be seen in the db2diag.log when
doing the redistribution:
2008-12-19-16.10.51.029166-360 E30101G685 LEVEL: Info
PID : 24284 TID : 3058690960 PROC : db2sysc
0
INSTANCE: dpfv95b NODE : 000 DB : SAMPLE
APPHDL : 0-57 APPID: *N0.DB2.081219221049
AUTHID : DPFV95B
EDUID : 94 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, database utilities - Redistribute,
sqlurRedistributeTableByID, probe:8035
MESSAGE : REDISTRIBUTE TABLE
DATA #1 : String, 17 bytes
<schema> <tbname>
DATA #2 : String, 8 bytes
DPFV95
DATA #3 : String, 7 bytes
EMPTEST
DATA #4 : String, 18 bytes
<pool ID> <obj ID>
DATA #5 : signed integer, 2 bytes
3
DATA #6 : signed integer, 2 bytes
5
2008-12-19-16.10.51.104282-360 E30787G742 LEVEL: Warning
PID : 24284 TID : 3057642384 PROC : db2sysc
0
INSTANCE: dpfv95b NODE : 000 DB : SAMPLE
APPHDL : 0-57 APPID: *N0.DB2.081219221049
AUTHID : DPFV95B
EDUID : 95 EDUNAME: db2rinit 0
FUNCTION: DB2 UDB, data management, sqldSetupSQLCA, probe:3
MESSAGE : ADM5570W Access was attempted on an unavailable
object with id "5"
in tablespace "3" for table "DPFV95.EMPTEST". If the
object is a
table it will have to be dropped. If the object is a
partition it
will have to be detached. If the object is a
non-partitioned index
the index will have to be dropped.
When trying to drop the table, the below message will be seen:
$ db2 drop table dpfv95.emptest
DB21034E The command was processed as an SQL statement because
it was not a
valid Command Line Processor command. During SQL processing it
returned:
SQL0668N Operation not allowed for reason code "9" on table
"DPFV95.EMPTEST".
SQLSTATE=57016 | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of REDISTRIBUTE * **************************************************************** * PROBLEM DESCRIPTION: * * A table in an unavailable state is able to be redistributed, * * which results in the table being in drop pending and * * redistribute pending. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.7 FP1 * **************************************************************** | |
| Local Fix: | |
The workaround is to verify all the tables in the nodegroup prior to the redistribute are all in a good state. Any state (ie, load in progress, set integrity pending, unavailable) will result in a failure when redistribute eventually processes that table. One technique to detemine the tables are accessible prior to redistribute using the following query: db2 "select distinct tabschema, tabname from sysibmadm.admintabinfo where available='N'" | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
| Solution | |
Problem fixed in DB2 V9.7 FP1 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.10.2009 22.02.2010 22.02.2010 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP1 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.1 |
|