PI50513: IN A CLUSTERED ENVIRONMENT THE JOB TABLES "XJCLREPOSITORY" AND "GLOBALJOBIDASSIGNMENT" WILL NOT BE PURGED CORRECTLY

8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• On a clustered environment, when purging jobs, some entries are
  still remaining in the "XJCLREPOSITORY" and
  "GLOBALJOBIDASSIGNMENT"  tables. This may lead to hanging
  threads after some time, because the entries have never been
  deleted and the tables increase from time to time.
  
  With this iFix the entries will be deleted correctly from the
  job-tables as soon as the jobs will be purged.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Purge operation leaves entries in       *
  *                      XJCLREPOSITORY and                      *
  *                      GLOBALJOBIDASSIGNMENT table.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Occassionally, the purge operation does not remove all related
  entries of a job. Obsolete entries are seen from
  XJCLREPOSITORY and/or GLOBALJOBIDASSIGMENT table.
  

Problem conclusion

• The purge job operation's ability to remove all related
  database entries for a job is depended on the availability of
  the job scheduler that submitted the job. A best effort is
  attempted if owning scheduler is not active, and can lead to
  inconsistency in the batch database.  This is often not an
  issue in low volume batch environment.  However, if this is
  not adequate, the batch job scheduler can be configured to
  perform purge operation on a job only when the job owning
  scheduler is active.  To achieve this, set job scheduler
  custom property
  "only.purge.when.owning.scheduler.active" to true.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.9.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP