PM94607: HIGH CPU AND ELAPSED TIMES DURING HIGH SPEED MODE RUN

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• High CPU and elapsed times can occur during a high speed run in
  the general report phase, which may even appear to be a loop.
  The reported problem may occur if SAVEPOINT rollbacks are part
  of a very large unit of work (generally noticeable on a UOW in
  excess of 500,000 DML).
  These rollbacks cause the product to invoke both an indexed and
  fullscan per DML activity record causing the long CPU/elapsed
  times. The fix allows the index scan, but prevents a subsequent
  full scan.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Log Analysis.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: If a LOAD LOG YES action is present     *
  *                      and both the relevant tablespace        *
  *                      (i.e. image copy) is very large and     *
  *                      the LOAD itself is large, performance   *
  *                      may become unacceptably slow during     *
  *                      image copy processing.  This APAR       *
  *                      improves the performance under those    *
  *                      conditions, though it may still be a    *
  *                      very time consuming operation. If a     *
  *                      LOAD LOG YES action is not required     *
  *                      to be materialized into individual      *
  *                      INSERTs, it is highly recommended that  *
  *                      the 'Show INSERTs=X' setting be used    *
  *                      when possible, which bypasses these     *
  *                      log records. It is not always           *
  *                      possible to use that setting in a       *
  *                      log-forward mode of operation because   *
  *                      the inserts from the LOAD may be needed *
  *                      if subsequent DML affects those         *
  *                      inserted records. In that case, a       *
  *                      log-backward operation may be           *
  *                      performed, again, only if possible      *
  *                      for the particular run.                 *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Apply the PTF.
  

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:

  UK98075

Modules/Macros

• ALAETV   ALALF1
  

Fix information

• Fixed component name

  DB2 LOG ANALYSI

• Fixed component ID

  5655E6601

Applicable component levels

• R330 PSY UK98075

     UP13/10/05 P F310

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.