IC89171: MISSING ROWS AFTER PRIMARY ALONE AND CATCHUP

APAR status

• Closed as program error.

Error description

• In solidDB V6.3 with a HotStandby setup, transactions that were
  committed to the Primary in PRIMARY ALONE state are not
  replicated to the Secondary after the servers are reconnected.
  The catchup after the servers have been reconnected appears to
  finish successfully.
  
  March 26, 2013: The problem was fixed originally in IBM solidDB
  6.3
  Interim Fix 9 (06.30.0054). However, the fix was insufficient; a
  new fix available in V6.3 Interim
  Fix 10 (06.30.0055).
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All HSB users.                                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to IBM solidDB 6.3 Interim Fix 10.                   *
  ****************************************************************
  

Problem conclusion

• Fix is included in IBM solidDB 6.3 Interim Fix 10 (06.30.0055).
  

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

  SOLIDDB-DB2/IDS

• Fixed component ID

  5724V1700

Applicable component levels

• R630 PSY

     UP