IC88120: DATABASE UPGRADE TO DB2 VERSION 10.1 MAY FAIL WITH SQL2072N IF LOGARCHMETH1/LOGARCHMETH2 IS SET TO VENDOR OR TSM.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • When issuing an upgrade database in DB2 for Linux, Unix and
    Windows version 10.1, an error
    similar to the following may be encountered:
    
    db2 upgrade database MYDB
    SQL2072N  Unable to bind the shared library
    "/usr/openv/netbackup/bin/nbdb2.sl64/". Reason code: "1".
    
    
    This is due to the database config parameter LOGARCHMETH1 being
    set in a similar fashion:
    
    First log archive method                 (LOGARCHMETH1)     =
    VENDOR:/usr/openv/netbackup/bin/nbdb2.sl64
    
    
    Likewise, having LOGARCHMETH1 set to TSM can potentially cause a
    similar upgrade failure.
    

Local fix

  • Ideally, if the potential for this issue exists, then, prior to
    upgrade, the log archiving method can be updated to something
    other then TSM (if a management class is specified) or VENDOR.
    After the upgrade completes this can be reverted back.
    
    In the event of encountering the error however the only possible
    workaround is as follows:
    
    db2 upgrade database SAMPLE    //this will fail
    db2 deactivate db SAMPLE
    db2 update db cfg for SAMPLE using logarchmeth1 off immediate
    db2stop
    mv
    <the_dbpath>/<the_instance_name>/NODE0000/SQLxxxxx_dir_for_this_
    database/MEMBER0000/SQLDBCONF
    <the_dbpath>/<the_instance_name>/NODE0000/SQLxxxxx_dir_for_this_
    database/MEMBER0000/SQLDBCONF.orig
    cp
    <the_dbpath>/<the_instance_name>/NODE0000/SQLxxxxx_dir_for_this_
    database/SQLDBCONF
    <the_dbpath>/<the_instance_name>/NODE0000/SQLxxxxx_dir_for_this_
    database/MEMBER0000/SQLDBCONF
    db2start
    db2 upgrade database SAMPLE
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 version v10.01 fix pack 2.                    *
    ****************************************************************
    

Problem conclusion

  • First fixed in version 10.01 fix pack 2.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC88120

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-09

  • Closed date

    2013-04-16

  • Last modified date

    2013-04-16

  • 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

  • RA10 PSN

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

10.1

Reference #:

IC88120

Modified date:

2013-04-16

Translate my page

Machine Translation

Content navigation