|
Problem IT04739
|
Status: Closed |
RENAME TABLE AGAINST AN ALIAS CAUSES THE UNDERLYING TABLE TO TAKE ON THE ALIAS' SCHEMA |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
For example, suppose table S1.T1 has an alias in a different
schema, S2.T1_ALIAS. After
rename table S2.T1_ALIAS to T1_NEW
the underlying table is renamed to T1_NEW (this is expected),
but the table's schema is changed to the alias' schema. S1.T1 no
longer exists, as it's renamed to S2.T1_NEW, and the alias
refers to a non-existent table (S1.T1).
The underlying table's schema should remain unchanged. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to DB2 v9.7 Fix Pack 11 *
**************************************************************** |
| Local Fix: |
N/A |
| Solution |
Problem first fixed in DB2 v9.7 Fix Pack 11 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.10.2014
19.10.2015
19.10.2015 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP11
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.11
|
 |
