DB2 FOR LUW / DB2FORLUW / A10 - DB2

For PureData Systems for Transactions, a DEPLOY database may 
fail with an error if the database being deployed has the same 
name as a DELETED database. 
 
After deleting the database, the system database directory in 
the pureScale instance may still contain cached entries for the 
deleted database. 
 
In both PureData System for Transactions and in DB2 pureScale, 
this error will appear as an SQL1031 after the first connection 
to the database.

**************************************************************** 
* USERS AFFECTED:                                              * 
* purescale                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v101fp                                        * 
****************************************************************

For pureScale, connect to the database a second time, and 
re-issue the failed command. 
 
For PureData Systems for Transactions, a STOP and a START of the 
instance is required between the DELETE and DEPLOY of the 
database in order to flush out the invalid cached entries.

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

will be fixed in v101fp

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

14.05.2013
02.06.2014
02.06.2014