|
Problem IC92291
|
Status: Closed |
RE-CREATING A PREVIOUSLY DROPPED DATABASE WITH DIFFERENT PATH MAY FAIL WITH SQL1031N |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* purescale *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2_v101fp *
**************************************************************** |
| Local Fix: |
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. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
will be fixed in v101fp |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.05.2013
02.06.2014
02.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
