Results 1 to 10 of 10
  1. #1
    Join Date
    May 2006
    Posts
    19

    Unanswered: Upgrade database stops db2

    Hi all,

    I'm running a DB2 Express-C version 9.7 installation on WinXP SP3. A database has been cataloged that has been created by an DB2 version 8.2.

    If I try to connect to that database, a SQL5035 message is shown telling me that I must upgrade the database.
    Invoking the db2 upgrade database command for that database, results in an abnormal termination of the database instance (the systray symbol changes to "stopped" state) and the message SQL1224 (no more connections).

    Looking into the db2diag.log, the last 2 not-Info-Level messages are "Begin migrating catalog table: SYSTABLES" and "End engn migration: with rc = -1224, sqlcode = -1224".
    In the diagpath the files 780.3916.trap.bin and 780.3916.dump.bin has been created.

    Any ideas what I can to to upgrade/migrate that database?

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    You may want to follow the steps outlined in the manual: Upgrading databases - IBM DB2 9.7 for Linux, UNIX, and Windows

  3. #3
    Join Date
    May 2006
    Posts
    19
    I had used exactly that part of the db2 manual to do the database upgrade. Step 3 describes the UPGRADE DATABASE command to be executed. The remaining steps are for special execution warnings and errors. In my case, the database instance (or one of its processes) crashes while executing the UPGRADE DATABASE command. So, there is no result message to analyse.

    The DB2 command shell then prints out a sql1224. In the description of sql1224, a possible reason for that result is an abnormal termination of the database agent or database manager. Due to the existance of a new dump file I assume that this is the reason for the failing UPGRADE command.

    I've allready tried to perform an update with automatic migration of the database, but the result is the same.

    Any more hints?

  4. #4
    Join Date
    Dec 2008
    Location
    Toronto, Canada
    Posts
    399
    one of the options you have is to drop the database and than restore on new db2 version (you should have taken a backup before migration). it will be migrated automatically by db2.
    DB2 9.5/9.7 on Unix/AIX 6.1/Linux

  5. #5
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    I think restore will also fail during catalog migration. What other errors do you see in the db2diag.log? Do you see ADM0501C?

  6. #6
    Join Date
    May 2006
    Posts
    19
    Trying to restore the backup into the db2 v9.7 results in the message SQL2519N (database restored but migration failed) with an error code "-1224" and token containing "SEMAPHORE WAIT". Thus, it effectively results in the same error I got trying to upgrade the database manually using UPGRADE DATABASE command.

    I've deleted the old db2diag.log file before executing the restore command. The new db2diag.log file contains some warnings, mostly "DB2 UDB, catalog migration, sqlrlm_catalog_migrate, probe:4754" with "migration status: 2".

    The last 3 entries in the db2diag.log file are:
    2010-07-07-08.21.58.643000+120 I177119H485 LEVEL: Warning
    PID : 1188 TID : 3420 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000 DB : PB
    APPHDL : 0-150 APPID: *LOCAL.DB2.100707062151
    AUTHID : SYSTEM
    EDUID : 3420 EDUNAME: db2agent (PB )
    FUNCTION: DB2 UDB, catalog migration, sqlrlm_catalog_migrate, probe:4945
    DATA #1 : <preformatted>
    Begin migrating catalog table: SYSTABLES

    2010-07-07-08.23.49.005000+120 I177606H316 LEVEL: Warning
    PID : 2216 TID : 2724 PROC : db2bp.exe
    INSTANCE: DB2 NODE : 000
    EDUID : 2724
    FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:20
    MESSAGE : End engn migration: with rc = -1224, sqlcode = -1224

    2010-07-07-08.23.49.036000+120 I177924H309 LEVEL: Error
    PID : 1496 TID : 3080 PROC : db2dasstm.exe
    INSTANCE: DB2 NODE : 000
    EDUID : 3080
    FUNCTION: DB2 Tools, DB2 administration server, handleRunCmd, probe:85
    DATA #1 : signed integer, 4 bytes
    -2519

    Additionally, a file "1188.3420.trap.bin" has been created during that process.
    Last edited by holgerschlegel; 07-07-10 at 03:40.

  7. #7
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    Your best bet seems to be to open a PMR with IBM support.
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

  8. #8
    Join Date
    Jan 2009
    Location
    Zoetermeer, Holland
    Posts
    746
    Quote Originally Posted by stolze View Post
    Your best bet seems to be to open a PMR with IBM support.
    PMR? Express-C? Since when?

  9. #9
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Few things to try:
    - run db2ckupgrade and verify there's absolutely nothing in the log
    - run DB2DART on the 8.2 database (provided you still have 8.2 installed)
    - change DIAGLEVEL to 4 before the database upgrade and see if there are more details in db2diag.log

  10. #10
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Quote Originally Posted by holgerschlegel View Post
    Additionally, a file "1188.3420.trap.bin" has been created during that process.

    Format this file using db2xprt:
    IBM DB2 9.7 for Linux, UNIX and Windows Information Center


    For example,
    db2xprt 1188.3420.trap.bin 1188.3420.trap.txt


    Open 1188.3420.trap.txt and look for a line that says "failing instruction". This will have the function name where db2 trapped. Try searching for any known APARs using this function name here:
    IBM Support Portal - DB2 for Linux, UNIX and Windows


    You can also try installing the latest fixpack if it's available for this product.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •