|
Problem IC63104
|
Status: Closed |
POSSIBLE DATA LOSS WHEN CALLING ADMIN_MOVE_TABLE AND TRIGGERS ARE MISSING PRIOR TO THE SWAP PHASE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
During the INIT phase of ADMIN_MOVE_TABLE a number of triggers
are created to capture any data changes made to the source
table. If any of these triggers are dropped prior to the SWAP
phase, it is possible to miss some changes that happened to the
source table during the move, and have data loss after the move
completes. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of the ADMIN_MOVE_TABLE stored procedure *
****************************************************************
* PROBLEM DESCRIPTION: *
* During the INIT phase of ADMIN_MOVE_TABLE a number of *
* triggers are created to capture any data changes made to the *
* source table. If any of these triggers are dropped prior to *
* the SWAP phase, it is possible to miss some changes that *
* happened to the source table during the move, and have data *
* loss after the move completes. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to FP1 for v97 for the fix. *
**************************************************************** |
| Local Fix: |
Before the SWAP phase, make sure the triggers still exist. This
can be done by checking SYSCAT.TRIGGERS. For the table being
moved, there should exist 4 triggers, with a name similar to
'T1AAAAVxi', where T1 is the name of the table being moved. If
these 4 triggers don't exist, cancel the move operation and
start it again. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
If the triggers are missing prior to the SWAP phase,
ADMIN_MOVE_TABLE will return an error. Upgrade to FP1 for v97
for the fix. |
| Workaround |
Before the SWAP phase, make sure the triggers still exist. This
can be done by checking SYSCAT.TRIGGERS. For the table being
moved, there should exist 4 triggers, with a name similar to
'T1AAAAVxi', where T1 is the name of the table being moved. If
these 4 triggers don't exist, cancel the move operation and
start it again. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.09.2009
16.02.2010
16.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
