IBM Support

IC69489: SETTING A RELATIVE AGENT PRIORITY OF -1 HAS NO EFFECT - 'DB2PD -AGENTS' WILL INCORRECTLY REPORT -1 PRIORITIES

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When setting a relative agent priority of -1 (higher relative
    priority) in DB2 on a supported UNIX platform, there will be no
    actual change in the priority of the affected agents. This is
    due to a problem in DB2 (which the fix to this APAR addresses).
    Due to this problem, there is an additional side-effect when
    using 'db2pd -agents'.
    
    This side-effect is particularly apparent on platforms where
    certain capabilities must be bestowed upon the user in order to
    increase the relative agent priority, such as on AIX. For
    example, on AIX, the user must have CAP_NUMA_ATTACH and
    CAP_PROPAGATE capabilities in order to increase the relative
    agent priority. In the absence of these capabilities, if you try
    to set a relative agent priority of -1 for any agents and then
    examine the relevant agent priorities via 'db2pd -agents', the
    output will display -1 priorities, even though the actual agent
    priorities haven't changed.
    
    Example 'db2pd -agents' output (without CAP_NUMA_ATTACH and
    CAP_PROPAGATE capabilities enabled):
    
    Address            AppHandl [nod-index] AgentEDUID Priority
    Type     State       ClientPid  Userid   ClientNm Rowsread
    Rowswrtn   LkTmOt DBName   LastApplId
                               LastPooled
    0x0780000001255E80 45       [000-00045] 1544       0
    Coord    Inst-Active 1642592    db2inst1    db2bp    170
    0          NotSet MYDB     *LOCAL.db2inst1.100628151322
                                  Mon Jun 28 11:11:43
    0x0780000001270080 46       [000-00046] 1812       -1
    Coord    Inst-Active 1642592    db2inst1    db2stmm  0
    0          NotSet MYDB     *LOCAL.DB2.100628151332
                               Mon Jun 28 11:11:40
    0x07800000012F0080 47       [000-00047] 7245       -1
    Coord    Inst-Active 1642592    db2inst1    db2taskd 3
    0          NotSet MYDB     *LOCAL.DB2.100628151333
                               Mon Jun 28 11:11:39
    0x07800000012F5E80 48       [000-00048] 7758       -1
    Coord    Inst-Active 1642592    db2inst1    db2wlmd  0
    0          NotSet MYDB     *LOCAL.DB2.100628151334
                               Mon Jun 28 11:11:39
    0x0780000001275E80 49       [000-00049] 5211       -1
    Coord    Inst-Active 1642592    db2inst1    db2lused 0
    0          3      MYDB     *LOCAL.DB2.100628151335
                               n/a
    0x07800000012A0080 50       [000-00050] 5468       -1
    Coord    Inst-Active 1642592    db2inst1    db2fw0   0
    0          3      MYDB     *LOCAL.DB2.100628151336
                               n/a
    0x07800000012A5E80 51       [000-00051] 5725       -1
    Coord    Inst-Active 1642592    db2inst1    db2fw1   0
    0          3      MYDB     *LOCAL.DB2.100628151337
                               n/a
    0x0780000001360080 52       [000-00052] 5982       -1
    Coord    Inst-Active 1642592    db2inst1    db2fw2   0
    0          3      MYDB     *LOCAL.DB2.100628151338
                               n/a
    0x0780000001365E80 53       [000-00053] 6239       -1
    Coord    Inst-Active 1642592    db2inst1    db2fw3   0
    0          3      MYDB     *LOCAL.DB2.100628151339
                               n/a
    0x07800000013E0080 54       [000-00054] 6496       -1
    Coord    Inst-Active 1642592    db2inst1    db2evml_ 0
    0          3      MYDB     *LOCAL.DB2.100628151340
                               n/a
    
    This incorrect reporting is only applicable to the relative
    agent priority of -1. For other higher relative priority values,
    'db2pd -agents' will correctly report 0, since no changes will
    have actually occurred with respect to agent priorities without
    CAP_NUMA_ATTACH and CAP_PROPAGATE set.
    

Local fix

  • There is no workaround to the immediate problem of being unable
    to set a relative agent priority of -1. However, if feasible,
    you could always set a relative agent priority of -2.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 WLM users on a UNIX platform                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When setting a relative agent priority of -1 (higher         *
    * relative priority) in DB2 on a supported UNIX platform,      *
    * there will be no actual change in the priority of the        *
    * affected agents. This is due to a problem in DB2 (which the  *
    * fix to this APAR addresses). Due to this problem, there is   *
    * an additional side-effect when using 'db2pd -agents'.        *
    *                                                              *
    * This side-effect is particularly apparent on platforms where *
    * certain capabilities must be bestowed upon the user in order *
    * to increase the relative agent priority, such as on AIX. For *
    * example, on AIX, the user must have CAP_NUMA_ATTACH and      *
    * CAP_PROPAGATE capabilities in order to increase the relative *
    * agent priority. In the absence of these capabilities, if you *
    * try to set a relative agent priority of -1 for any agents    *
    * and then examine the relevant agent priorities via 'db2pd    *
    * -agents', the output will display -1 priorities, even though *
    * the actual agent priorities haven't changed (because of a    *
    * lack of the right capabilities being set).                   *
    *                                                              *
    * Example 'db2pd -agents' output (without CAP_NUMA_ATTACH and  *
    * CAP_PROPAGATE capabilities enabled):                         *
    *                                                              *
    * Address            AppHandl [nod-index] AgentEDUID Priority  *
    *   Type     State       ClientPid  Userid   ClientNm Rowsread *
    *   Rowswrtn   LkTmOt DBName   LastApplId                      *
    *                                  LastPooled                  *
    * 0x0780000001255E80 45       [000-00045] 1544       0         *
    *   Coord    Inst-Active 1642592    db2inst1    db2bp    170   *
    *      0          NotSet MYDB     *LOCAL.db2inst1.100628151322 *
    *                                        Mon Jun 28 11:11:43   *
    * 0x0780000001270080 46       [000-00046] 1812       -1        *
    *   Coord    Inst-Active 1642592    db2inst1    db2stmm  0     *
    *      0          NotSet MYDB     *LOCAL.DB2.100628151332      *
    *                                     Mon Jun 28 11:11:40      *
    * 0x07800000012F0080 47       [000-00047] 7245       -1        *
    *   Coord    Inst-Active 1642592    db2inst1    db2taskd 3     *
    *      0          NotSet MYDB     *LOCAL.DB2.100628151333      *
    *                                     Mon Jun 28 11:11:39      *
    * 0x07800000012F5E80 48       [000-00048] 7758       -1        *
    *   Coord    Inst-Active 1642592    db2inst1    db2wlmd  0     *
    *      0          NotSet MYDB     *LOCAL.DB2.100628151334      *
    *                                     Mon Jun 28 11:11:39      *
    * 0x0780000001275E80 49       [000-00049] 5211       -1        *
    *   Coord    Inst-Active 1642592    db2inst1    db2lused 0     *
    *      0          3      MYDB     *LOCAL.DB2.100628151335      *
    *                                     n/a                      *
    * 0x07800000012A0080 50       [000-00050] 5468       -1        *
    *   Coord    Inst-Active 1642592    db2inst1    db2fw0   0     *
    *      0          3      MYDB     *LOCAL.DB2.100628151336      *
    *                                     n/a                      *
    * 0x07800000012A5E80 51       [000-00051] 5725       -1        *
    *   Coord    Inst-Active 1642592    db2inst1    db2fw1   0     *
    *      0          3      MYDB     *LOCAL.DB2.100628151337      *
    *                                     n/a                      *
    * 0x0780000001360080 52       [000-00052] 5982       -1        *
    *   Coord    Inst-Active 1642592    db2inst1    db2fw2   0     *
    *      0          3      MYDB     *LOCAL.DB2.100628151338      *
    *                                     n/a                      *
    * 0x0780000001365E80 53       [000-00053] 6239       -1        *
    *   Coord    Inst-Active 1642592    db2inst1    db2fw3   0     *
    *      0          3      MYDB     *LOCAL.DB2.100628151339      *
    *                                     n/a                      *
    * 0x07800000013E0080 54       [000-00054] 6496       -1        *
    *   Coord    Inst-Active 1642592    db2inst1    db2evml_ 0     *
    *      0          3      MYDB     *LOCAL.DB2.100628151340      *
    *                                     n/a                      *
    *                                                              *
    * This incorrect reporting is only applicable to the relative  *
    * agent priority of -1. For other higher relative priority     *
    * values, 'db2pd -agents' will correctly report 0, since no    *
    * changes will have actually occurred with respect to agent    *
    * priorities without CAP_NUMA_ATTACH and CAP_PROPAGATE set.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 9.7 Fix Pack 3 or higher to address   *
    * the issues brought forth in this APAR.                       *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in DB2 Version 9.7 Fix Pack 3.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC69489

  • 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

    2010-06-28

  • Closed date

    2010-09-20

  • Last modified date

    2010-09-20

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

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

    IC69539

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC69489

Modified date: 20 September 2010