IC88947: UPGRADE COMMAND CAN FAIL DURING HISTORY-FILE UPGRADE PHASE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • The UPGRADE database command can fail during history-file
    upgrade phase.
    
    (suppose the Upgrade occurs from downlevel v91 to uplevel v97)
    If an entry is added to the history-file (for example, a log
    file is archived) during an UPGRADE operation *prior* to the
    history-file upgrade phase, then this new entry will reflect the
    uplevel format.  When the history-file upgrade phase begins it
    will process each history-file entry expecting a downlevel
    format (in order to convert each to an uplevel format), and will
    fail when it encounters this new history-file entry (because
    it's already uplevel format).
    
    This problem does *not* exist when Upgrading to v10.1 or later.
    
    In the db2diag.log, one would typically see a log file archive
    message appear before the history-file upgrade message:
    
    2012-11-25-15.21.57.272553-300 I325583E262         LEVEL:
    Warning
    PID     : 5156                 TID  : 46912566640496PROC : db2bp
    INSTANCE: nirspi16             NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:10
    MESSAGE : Begin engn migration
    ...
    2012-11-25-20.52.00.180998-300 E520601E443         LEVEL: Info
    PID     : 5210                 TID  : 46912912746816PROC :
    db2sysc 0
    INSTANCE: nirspi16             NODE : 000
    EDUID   : 54                   EDUNAME: db2logmgr (NIRSPI26) 0
    FUNCTION: DB2 UDB, data protection services,
    sqlpgArchiveLogFile, probe:3180
    DATA #1 : <preformatted>
    Completed archive for log file S0237783.LOG to USEREXIT from
    /UDB/nirspi16/p000/log/nirspi26/NODE0000/.
    ...
    
    And then you would see the hisotory-file upgrade phase start
    message, followed by the "Error parsing history entry: invalid
    number of fields found" message:
    
    2012-11-26-03.18.40.281628-300 I761730E557         LEVEL:
    Warning
    PID     : 1361                 TID  : 46912937912640PROC :
    db2sysc 0
    INSTANCE: nirspi16             NODE : 000          DB   :
    NIRSPI26
    APPHDL  : 0-7                  APPID:
    *LOCAL.nirspi16.121126015219
    AUTHID  : NIRSPI16
    EDUID   : 16                   EDUNAME: db2agent (NIRSPI26) 0
    FUNCTION: DB2 UDB, database utilities, sqlumigr, probe:100
    DATA #1 : String, 0 bytes
    Object not dumped: Address: 0x0000000000000000 Size: 0 Reason:
    Address is NULL
    MESSAGE : Starting history file migration.
    
    2012-11-26-03.18.40.558329-300 E762288E913         LEVEL: Error
    PID     : 1361                 TID  : 46912937912640PROC :
    db2sysc 0
    INSTANCE: nirspi16             NODE : 000          DB   :
    NIRSPI26
    APPHDL  : 0-7                  APPID:
    *LOCAL.nirspi16.121126015219
    AUTHID  : NIRSPI16
    EDUID   : 16                   EDUNAME: db2agent (NIRSPI26) 0
    FUNCTION: DB2 UDB, database utilities, sqluhReadEntry, probe:768
    MESSAGE : SQL2161N  A damaged recovery history file could not be
    fixed.  The
              specified action failed.
    DATA #1 : String, 60 bytes
    Error parsing history entry: invalid number of fields found.
    DATA #2 : String, 23 bytes
    Number of fields read:
    DATA #3 : signed integer, 4 bytes
    5
    DATA #4 : String, 32 bytes
    Expected number of fields read:
    DATA #5 : signed integer, 4 bytes
    24
    DATA #6 : Dumped object of size 512 bytes at offset 0, 50 bytes
    /home/nirspi16/sqllib/db2dump/1361.16.000.dump.bin
    

Local fix

  • To work-around the problem, truncate the history file (by
    renamed the db2rhist.asc and db2rhist.back to db2rhist.asc.save
    and db2rhist.bak.save), and perform the Upgrade operation again.
    Take a full Backup after successfully completion of the Upgrade.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to inclusive fixpack.                                *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IC88947

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-12-07

  • Closed date

    2013-05-21

  • Last modified date

    2013-05-21

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

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

Fix information

Applicable component levels

  • R970 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

9.7

Reference #:

IC88947

Modified date:

2013-05-21

Translate my page

Machine Translation

Content navigation