IBM Support

IC76426: CONCURRENCY ISSUE WHEN FLUSHING TWO OPTIMIZATION PROFILES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When two different optimization profiles are flushed
    concurrently, the latter one will need to wait for the first one
    to release the lock, although that they are for two different
    optimization profiles.
    
    This can happen with two different connections issuing FLUSH
    OPTIMIZATION PROFILE on different optimization profiles if they
    are not already in the cache.
    

Local fix

  • Issue the FLUSH OPTIMIZATION PROFILE commands sequentially.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All DB2 Version 9.7 Fix Pack 4 and earlier servers on Linux, *
    * Unix, and Windows platforms issuing the FLUSH OPTIMIZATION   *
    * PROFILE command.                                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When two different optimization profiles are flushed, the    *
    * latter                                                       *
    * one will need to wait for the first one to release the lock, *
    *                                                              *
    * although that they are in two different optimization         *
    * profiles.                                                    *
    * This can happen with two different connections issuing DB2   *
    * FLUSH                                                        *
    * OPTIMIZATION PROFILE on different optimization profiles if   *
    * they                                                         *
    * are not already in the cache.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 9.7 Fix Pack 5 or refer to Local Fix. *
    ****************************************************************
    

Problem conclusion

  • The problem is first fixed in DB2 Version 9.7 Fix Pack 5 and all
    subsequent Fix Packs.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC76426

  • 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-05-16

  • Closed date

    2011-05-24

  • Last modified date

    2011-05-24

  • 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

  • R820 PSN

       UP

  • R910 PSN

       UP

  • R950 PSN

       UP

  • R970 PSN

       UP

  • R980 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
24 May 2011