IBM Support

JR54670: "NOT LOGGED" OPTION PREVENTING DB RECOVERY IS USED FOR SOME LOB TABLESPACES ON DB2 FOR ZOS FOR BPM TABLES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • "NOT LOGGED" option is used for the creation of several BPM DB
    LOB tablespace when the DB type is DB2 for zOS. Having
    tablespaces set in this manner can prevent transaction recovery
    and impact the ability to restore from a DB backup.
    This impacts environment created prior to 8.5.5. Upgrading to
    8.5.5 does not correct existing environments.
    

Local fix

  • Change all tablespaces for your BPM environment DBs to
    "LOGGED".
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM Business Process Manager                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Already got agreement with the          *
    *                      database architect(Andreas              *
    *                      Fried1/Germany), L2 lead(Todd R         *
    *                      Deen/Durham/IBM), and Allen in the CC   *
    *                      list. We will not provide the ifix      *
    *                      for this issue, instead by providing    *
    *                      a technote.                             *
    *                      This is the technote:                   *
    *                      http://g01zciwas018.ahe.pok.ibm.com/sup *
    *                      port/dcf/preview.wss?host=g01zcidbs003. *
    *                      ahe.pok.ibm.com&db=support/swg/swgtech. *
    *                      nsf&unid=9E6F7F196CBB5C3A85257F07007CC7 *
    *                      81&taxOC=SSC8K7E&MD=2015/12/02%2010:12: *
    *                      52&sid=                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Already got agreement with the database architect(Andreas
    Fried1/Germany), L2 lead(Todd R Deen/Durham/IBM), and Allen in
    the CC list. We will not provide the ifix for this issue,
    instead by providing a technote.
    This is the technote:
    http://g01zciwas018.ahe.pok.ibm.com/support/dcf/preview.wss?host
    =g01zcidbs003.ahe.pok.ibm.com&db=support/swg/swgtech.nsf&unid=9E
    6F7F196CBB5C3A85257F07007CC781&taxOC=SSC8K7E&MD=2015/12/02%2010:
    12:52&sid=
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR54670

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    850

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-11-06

  • Closed date

    2016-01-17

  • Last modified date

    2016-01-17

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

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

Fix information

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 January 2016