|
Problem IC72869
|
Status: Closed |
SQL0301 may be returned if ADMIN_MOVE_TABLE was used to change a table's column from LONG VARCHAR FOR BIT DATA to BLOB. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If a table contains a column with the datatype "LONG VARCHAR FOR
BIT DATA",
and the ADMIN_MOVE_TABLE procedure is used to convert that
column to a BLOB while other applications are concurrently
accessing this table, then an sql0301 may be returned. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* LONG VARCHAR FOR BIT DATA TO BLOB migrations *
****************************************************************
* PROBLEM DESCRIPTION: *
* If you have "LONG VARCHAR FOR BIT DATA" COLUMNs and trying *
* to *
* move them to BLOB using ADMIN_MOVE_TABLE, while applications *
* are *
* running against these tables, then you could get SQL0301N. *
* *
* Please, apply this APAR. *
* *
* You can work around the issue, by making sure that *
* statements *
* are re-prepared after ADMIN_MOVE_TABLE is done. *
****************************************************************
* RECOMMENDATION: *
* Install this APAR or work around the issue, by making sure *
* that statements *
* are re-prepared after ADMIN_MOVE_TABLE is done. *
**************************************************************** |
| Local Fix: |
Application can re-prepare statements against the table after
ADMIN_MOVE_TABLE is done. |
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
If you have "LONG VARCHAR FOR BIT DATA" COLUMNs and trying to
move them to BLOB using ADMIN_MOVE_TABLE, while applications
are
running against these tables, then you could get SQL0301N.
Please, apply this APAR.
You can work around the issue, by making sure that statements
are re-prepared after ADMIN_MOVE_TABLE is done. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.11.2010
29.04.2011
29.04.2011 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
