DB2 FOR LUW / DB2FORLUW / 970 - DB2

When running db2ckupgrade against a database with version level 
v8.2 Fix Pack 1 (equivalent to v8.1 Fix Pack 8) or earlier, 
db2ckupgrade fails with SQL0444N due to the non-existence of the 
SYSPROC.ADMIN_CMD stored procedure. The SYSPROC.ADMIN_CMD stored 
procedure was first introduced in v8.2 Fix Pack 2 (equivalent to 
v8.1 Fix Pack 9). 
 
If you are running db2ckupgrade manually, you will see the 
following output: 
 
db2ckupgrade sample -l db2ckupgrade.log -u adminuser -p password 
 
  db2ckupgrade was unsuccessful. Please look at logfile for more 
details. 
 
 
Check the log file to see the actual errors: 
 
Database: 'SAMPLE' 
 
  ** ERROR ** 
 
[IBM][CLI Driver][DB2/AIX64] SQL0444N  Routine "ADMIN_CMD" 
(specific name "SQL110125110006970") is implemented with code in 
library or path ".../SYSPROC.ADMIN_CMD", function 
"SYSPROC.ADMIN_CMD" which cannot be accessed.  Reason code: "4". 
 SQLSTATE=42724 
 
  ** ERROR ** 
 
  REORG INDEXES command on catalog table 'SYSIBM.SYSTABLESPACES' 
failed. Run the REORG command "REORG INDEXES ALL FOR TABLE 
SYSIBM.SYSTABLESPACES" manually and resolve any reported errors 
prior to upgrading.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Running the db2ckupgrade utility from DB2 Version 9.7 Fix    * 
* Pack 1 through Fix Pack 3a against DB2 UDB Version 8.1 GA    * 
* through Version 8.2 Fix Pack 1 servers.                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The db2ckupgrade tool utilizes the SYSPROC.ADMIN_CMD stored  * 
* procedure, however, it was not introduced until later in     * 
* v8.2 Fix Pack 2. Thus, when running db2ckupgrade against     * 
* database with version level that is v8.2 Fix Pack 1 or       * 
* earlier will cause it to fail.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Refer to Local Fix or apply DB2 Version 9.7 Fix Pack 4 and   * 
* re-issue the command.                                        * 
****************************************************************

If you are upgrading to v9.7 via backup and restore, and you see 
only the above two errors recorded in the log file, then you can 
ignore the error messages and continue to upgrade your database. 
 
If instance upgrade (via db2iupgrade) is failing because of 
db2ckupgrade, then you need to contact IBM support to get a new 
version of the db2ckupgrade utility.

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
 

Problem is first fixed in DB2 Version 9.7 Fix Pack 4 and all 
subsequent Fix Packs.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

25.01.2011
28.04.2011
28.04.2011

9.7.FP4