The database upgrade to v10.5 misses to upgrade the packed
descriptor of MQT dependant views.
A MQT can be based on a view like in the following simple
example:
1.) db2 "create table t1 (c1 int, c2 int)"
2.) db2 "insert into t1 values (1,2),(2,3),(3,4)"
3.) db2 "create view v1 as select * from t1"
4.) db2 "create table mqt as (select * from v1) data initially
deferred refresh deferred"
If the database was upgraded then the DROP of such an MQT may
fail:
db2 "drop table mqt"
DB21034E The command was processed as an SQL statement because
it was not a
valid Command Line Processor command. During SQL processing it
returned:
SQL1224N The database manager is not able to accept new
requests, has
terminated all requests in progress, or has terminated the
specified request
because of an error or a forced interrupt. SQLSTATE=55032
It may cause various crashes of the DB2 database server as the
stack got corrupted.
On Windows OS we have seen a SQL0901N error logged with message
"Invalid isolation":
2013-12-05-08.52.41.757000+060 I1247675F902 LEVEL:
Severe
PID : 4992 TID : 6600 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : MIDB
APPHDL : 0-107 APPID:
127.0.0.1.49515.131205074913
AUTHID : DB2ADMIN HOSTNAME: localhost
EDUID : 6600 EDUNAME: db2agent (DB) 0
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,
probe:300
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 17
sqlerrmc: Invalid isolation
sqlerrp : SQLRC06C
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0xFFFFFFEC (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: |
