PK75402: DB2 STATUS IS ALWAYS WAIT-REMREQ FOR DISTRIBUTED DATABASE ACCESS(DBAT) THREADS IN OMPE CLASSIC AND TEP SCREENS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DBAT thread has getpg, update activity, and wait for lock but
  the status always WAIT-REMREQ (see details below)
  
  ________________ ZTDTL    VTM     O2       V410./C SDF1 11/07/08
  20:36:43   2
  >                                THREAD DETAIL
   PLAN
  + Thread:  Plan=DISTSERV  Connid=SERVER   Corrid=db2bp.exe
  Authid=SUK
  + Dist  :  Type=DATABASE ACCESS,
  Luwid=G9414B5C.NA07.081107192507=25
  + Location  :  9.65.75.92
   act
  + Thread Activity                         User Defined Functions
  + -------------------------------------
  -------------------------------------
  + DB2 Status            =   WAIT-REMREQ   TCB Time (SQL)
  = 00:00:00.000
  + MVS Status            =                 Wait for TCB Time
  = 00:00:00.000
  + Total Elapsed Time    =  00:10:56.984   Elapsed Time
  = 00:00:00.000
  + CP CPU Utilization    =         00.0%   Elapsed Time (SQL)
  = 00:00:00.000
  + Total CP CPU Time     =  00:00:00.122   SQL Events
  =            0
  
  
  
  ================================================================
  ===============
  >                    Threads Summary Excluding Idle Threads
   THDA
  + *
  + Elapsed      Planname  CPU    Status       GetPg  Update
  Commit CORRID/JOBN
  + ----------   --------  -----  ------------ ------ ------
  ------ ------------
  + 22:33:49.5   KO2PLAN   00.0%  NOT-IN-DB2     2275     18
  7 SDF1DM4S
  + 22:33:34.7   KO2PLAN   00.0%  NOT-IN-DB2        0      0
  0 SDF1DM4S
  + 22:33:22.8   KO2PLAN   00.6%  IN-DB2            0      0
  0 SDF1DM4S
  + 03:01:59.9   KO2PLAN   00.0%  NOT-IN-DB2        0      0
  0 D832DM1S
  + 00:10:09.9   DSNESPCS  00.0%  NOT-IN-DB2       56      1
  0 SUK
  + 00:00:47.3   DISTSERV  00.0%  WAIT-REMREQ    1124     18
  0 db2bp.exe
  ================================================================
  ===============
  
  Lock Conflicts:
  
   ________________ ZLOCKC   VTM     O2       V410./C SDF1 S
  11/07/08 20:37:57
  >                             LOCKING CONFLICTS
  
   XLOK
  +Stat Plan     Corrid       Type Lvl Resource
  +---- -------- ------------ ---- ---
  ------------------------------------------
  + OWN DSNESPCS SUK          DPAG   X DB=SUKTEST  PS=SUKTAB
  PG=0000000C
  +WAIT DISTSERV db2bp.exe    DPAG   S DB=SUKTEST  PS=SUKTAB
  PG=0000000C
  ================================================================
  ===============
  
  
  
  Waiting for a lock:
  
   ________________ ZLOCKW   VTM     O2       V410./C SDF1
  11/07/08 20:37:13   2
  >                    LOCKS/CLAIMS CAUSING A THREAD TO WAIT
   PLAN
  + Thread:  Plan=DISTSERV  Connid=SERVER   Corrid=db2bp.exe
  Authid=SUK
  + Dist  :  Type=DATABASE ACCESS,
  Luwid=G9414B5C.NA07.081107192507=25
  + Location  :  9.65.75.92
   wait
  +      Thread Is Currently Suspended Waiting To Obtain The
  Following Lock
  +      Type=DPAG  Level=S   Resource = DB=SUKTEST  PS=SUKTAB
  PG=0000000C
  +
  +      Wait For Lock Time  =   36 Seconds     # to repeat lock
  timeout =  23K
  +      IRLM Time Out Value =   60 Seconds
  +
  +      The Lock Being Waited On Is Owned By The Following
  User(s)
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   Tivoli Enterprise Monitoring Agent       *
  *                 -   Classic Interface                        *
  *                 -   CUA Interface                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: Thread status may be incorrect          *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  ****************************************************************
  PROBLEM SUMMARY:
  The thread status was checked incorrectly.
  
  PROBLEM CONCLUSION:
  Fix the code to check the thread status correctly.
  

Problem conclusion

• Fix the code to check the thread status correctly.
  
  KEYWORDS : THREAD STATUS INCORRECT
  

Temporary fix

Comments

APAR Information

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

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

  UK46200

Modules/Macros

•    KO2CTH8A KO2CTH8S KO2CTH82
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R410 PSY UK46200

     UP09/05/06 P F905

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.