|
Problem IC74032
|
Status: Closed |
BIND FILE FOR AUTOMATICALLY BINDING NULLID.AOTMH00 IS INCORRECT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If the NULLID.AOTMH00 package is dropped, there is auto-bind
functionality to bind the package when you call the
SYSPROC.ADMIN_MOVE_TABLE procedure. The problem is that the
bind file name used was incorrect. Here are the symptoms:
1.) The package for SYSPROC.ADMIN_MOVE_TABLE is dropped, ie.
NULLID.AOTMH00
2.) You call SYSPROC.ADMIN_MOVE_TABLE and get the following:
call
sysproc.admin_move_table('MYSCHEMA','TDF','TS2','TS2','TS2','','
','','','','MOVE')
SQL0805N Package "NULLID.AOTMH00 0X4141414141634858" was not
found.
SQLSTATE=51002 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users who have dropped NULLID.AOTMH00 *
****************************************************************
* PROBLEM DESCRIPTION: *
* If the NULLID.AOTMH00 package is dropped, there is auto-bind *
* *
* functionality to bind the package when you call the *
* *
* SYSPROC.ADMIN_MOVE_TABLE procedure. The problem is that the *
* *
* bind file name used was incorrect. Here are the symptoms: *
* *
* 1.) The package for SYSPROC.ADMIN_MOVE_TABLE is dropped, *
* ie. *
* NULLID.AOTMH00 *
* 2.) You call SYSPROC.ADMIN_MOVE_TABLE and get the *
* following: *
* *
* call *
* sysproc.admin_move_table('MYSCHEMA','TDF','TS2','TS2','TS2', *
* '',' *
* ','','','','MOVE') *
* *
* SQL0805N Package "NULLID.AOTMH00 0X4141414141634858" was *
* not *
* found. *
* *
* SQLSTATE=51002 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v9.7 FP5 or newer *
**************************************************************** |
| Local Fix: |
The workaround is to bind db2_adminotm.bnd package manually. To
do this please do the following:
1.) Navigate to .../sqllib/bnd
2.) Connect to the database in question
3.) Run: db2 bind db2_adminotm.bnd |
| available fix packs: |
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 |
Upgrade to DB2 v9.7 FP5 or newer |
| Workaround |
The workaround is to bind db2_adminotm.bnd package manually. To
do this please do the following:
1.) Navigate to .../sqllib/bnd
2.) Connect to the database in question
3.) Run: db2 bind db2_adminotm.bnd |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.01.2011
20.12.2011
20.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
