JR34310: THIS APAR COMBINES PATCHES FOR THE FOLLOWING APARS: JR31114, JR30560, AND JR30106.

APAR status

• Closed as program error.

Error description

• This APAR combines the the patches for the following APARS:
  JR31114, JR30560, and JR30106.
  
  Please refer to each of the above APARs for details.
  

Local fix

• This fix is included in 8.0.1 fix pack 3
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  - INTERMITTENT LOCKING ISSUES (JR30106)
    - Diagnosis of DB2 "non-atomic batch errors"
      Detection of DB2 deadlock and full tablespace conditions
      Deadlocks causing operations to fail (JR30560)
    - Slow performance when deleting large object graphs (e.g.
  DataStage
      jobs) from the Information Server repository (JR31114)
  ****************************************************************
  PROBLEM DESCRIPTION:
   - DB2 locking issues encountered intermittently.
  
    - Information Server client applications sometimes fail to
  save
      objects to the Information Server repository, due to a DB2
      "Non-atomic batch error".  No other information is being
  logged
      about any errors that are chained to this error, so it is
  difficult
      to diagnosis the cause.
  
      Information Server client applications sometimes fail to
  save or
      retrieve objects from the Information Server repository due
  to
      a DB2 deadlock condition that is reported by DB2 using error
  codes
      SQLSTATE 40506, error code -1476, SQLERRMC -911.
      This combination of error codes is not detected as a
  deadlock by the
      Information Server repository, and the error is reported to
  the Information
      Server client application as a fatal error rather than a
  deadlock condition.
  
      Failures that occur due to a full DB2 tablespace are not
  specifically
      detected and logged.
  
      Information Server client applications sometimes fail to
  perform operations
      on the Information Server repository due to database
  deadlocks.  These
      deadlocks occur due to contention on database resources in
  multi-user
      sceanrios.
  
    - Deleting large object graphs from the Information Server
  repository
      has been shown to be a performance issue.  The primary use
  case for
      exposing this problem is the deletion of a large DataStage
  job.
  
  ****************************************************************
  RECOMMENDATION:
  INSTALL PATCH: JR34310 ( This APAR combines the the patches for
  the following APARS:
  JR31114, JR30560, and JR30106) .
  ****************************************************************
  

Problem conclusion

• - Change default isolation level of transactions. Add
  application support for
      the new isolation level.
  
    - Details about all chained errors that are thrown by DB2
      are logged to the WebSphere SystemOut.log to assist in
  diagnosing
      the cause of non-atomic batch errors and other errors.
  
      DB2 deadlock condition is detected for SQLSTATE 40506,
  error code
      -1476, SQLERRMC -911, and reported to the client
  application as a
      deadlock condition rather than a fatal error.
  
      DB2 failures due to a full tablespace are detected,
  logged, and an
      InsufficientDatabaseStorageException is reported to the
  client application.
  
      The likelihood of database deadlocks during certain
  repository operations
      has been reduced.
  
    - The IS repository delete operation has been redesigned,
  yielding
      a significant performance improvement for this operation.
  

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:

Modules/Macros

• SERVER
  

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R801 PSN

     UP