JR48964: LOB COLUMNS IN IBM BPM ARE SET TO NOT LOGGED, WHICH RESULT IN DISASTER RECOVERY FAILURE FOR IBM DB2

7.5.1.2-WS-BPM-IFJR48964
Version 8.5 Refresh Pack 5 for the IBM Business Process Manager products
Download Version 8.0.1 Fix Pack 3 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• Disaster recovery fails on DB2 because all LOB columns in IBM
  Business Process Manager (BPM) are set to not be logged.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM BPM Advanced                            *
  *                  IBM Standard                                *
  *                  IBM Express                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: You cannot use the point-in-time        *
  *                      recovery feature of DB2 when the LOB    *
  *                      columns in the IBM Process Server       *
  *                      database and Performance Data           *
  *                      Warehouse database on DB2 do not use    *
  *                      the LOGGED option.                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  To use the point-in-time recovery feature of DB2, the LOGGED
  option must be set for LOB columns.
  

Problem conclusion

• A fix is available for IBM BPM to provide the SQL scripts that
  changes the logging option of the LOB columns of the Process
  Server database and the Performance Data Warehouse database.
  
  On Fix Central (http://www.ibm.com/support/fixcentral), search
  for JR48964:
  
   1. Select IBM Business Process Manager with your edition from
  the product selector, the installed version to the fix pack
  level, and your platform, and then click Continue.
   2. Select APAR or SPR, enter JR48964, and click Continue.
   3. Download and install all prerequisite fixes for JR48964.
  
  When you download fix packages, ensure that you also download
  the readme file for each fix. Review each readme file for
  additional installation instructions and information about the
  fix.
  
  After you install the interim fixes, update the LOB columns:
  
   1. Stop all Process Server and the Performance Database
  Warehouse servers, node agents, and deployment manager.
    2. Make sure that the DB2 server is started.
    3. Run the following command:
  
  AppServer\BPM\Lombardi\tools\upgrade\upgrade_7x>.\LOBLoggingEnab
  lement.bat|sh -profileName Dmgr01 -nodeName   bxv9v357Node01
  -serverName de1.AppTarget.bxv9v357Node01.0
  
     The arguments are similar to the upgrade_7x command; point
  the command to one of the app cluster targets. If the
  Performance   Database Warehouse server is on the Support
  cluster, use the following command:
  
  
    AppServer\BPM\Lombardi\tools\upgrade\upgrade_7x>.\LOBLoggingEn
  ablement.bat|sh -profileName AdvPCDmgr01 -nodeName
    bxv9v357Node01 -serverName de1.AppTarget.bxv9v357Node01.0
  -perfNodeName bxv9v357Node01 -perfServerName
    de1.Support.bxv9v357Node01.0
  
    The updateBPMDB.sql and updatePDWDB.sq files are generated
  under the same folder.
  
    4. Complete the following tasks on a backup database first
  to avoid errors:
     a) Run updateBPMDB.sql against the Process Server database
  to changethe LOB logging option.
        b) Run updatePDWDB.sql against the Performance Database
  Warehouse database to change the LOB logging option.
  
   5.  If no issues occur, run updateBPMDB.sql and
  updatePDWDB.sql against the production database.
  

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

  BPM STANDARD

• Fixed component ID

  5725C9500

Applicable component levels

• R750 PSY

     UP