DB2 - Problembeschreibung
| Problem IC80632 | Status: Geschlossen |
IF ADMIN_MOVE_TABLE WITH CANCEL OPTION IS INTERRUPTED SUBSEQUENT CANCEL WILL FAIL WITH SQL2104N RC=8 | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problembeschreibung: | |
If a call to sysproc.admin_move_table with an action to CANCEL
is interrupted via CTRL C, and the command is re-issued again,
it would fail with SQL2104N Rc=8. This fix would make sure
that a subsequent admin_move_table does not fail with this
error and proceeds.
.
for example:
.
db2 "call sysproc.admin_move_table('schema1','tab1',tab1_new',
'keep,copy_with_indexes,'CANCEL')"
.
And you interrupt this action and re-issue again the table
would be stuck in this phase and no reorg/loads etc. would
be possible against the original table. | |
| Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 6. * **************************************************************** | |
| Local-Fix: | |
Do not cancel the cancel phase and let it complete. It may take a bit of time for it to complete depending on how large the table is in this case. . If this happens and the state of the table is stuck in this phase, no subsequent loads/reorgs would be possible on the origi nal table and you would need to recreate the original table again. | |
| verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
| Lösung | |
First fixed in Version 9.7 Fix Pack 6. | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC84412 Nachfolger : | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 03.01.2012 19.06.2012 19.06.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP6 | |
| Problem behoben lt. FixList in der Version | |
| 9.7.0.6 |
|