DB2 - Problembeschreibung
Problem IT04669 | Status: Geschlossen |
RENAME TABLE AGAINST AN ALIAS CAUSES THE UNDERLYING TABLE TO TAKE ON THE ALIAS' SCHEMA | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to v10.1 Fix Pack 5. * **************************************************************** | |
Local-Fix: | |
N/A | |
Lösung | |
Fixed in v10.1 Fix Pack 5. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 30.09.2014 14.07.2015 14.07.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.5 |