PM96311: PERFORMANCE MAY BE SLOW WITH LOAD LOG YES PRESENT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error 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.
  

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:

Modules/Macros

• ALAETV
  

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.