IBM Support

IC74096: DB2CKUPGRADE FAILS WITH SQL0444N WHEN RUN AGAINST DATABASES ON V8.2 FIX PACK 1 (A.K.A. V8.1 FIX PACK 8) OR EARLIER

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • 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.
    

Local fix

  • 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.
    

Problem summary

  • ****************************************************************
    * 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.                                        *
    ****************************************************************
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IC74096

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-01-25

  • Closed date

    2011-04-28

  • Last modified date

    2011-04-28

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSY

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC74096

Modified date: 28 April 2011