LI73245: SWITCHING A HADR PRIMARY TO STANDBY AND BACK TO PRIMARY MIGHT STOP ARCHIVING NEWLY GENERATED LOGFILES

DB2 Version 9.1 Fix Pack 7  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6   for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

APAR status

• Closed as program error.

Error description

• Converting a HADR Standby database to a Standard database and
  using this database, will generate new logfiles. These
  logfiles will get archived normally. When this database gets
  restored later on, to set it up again as HADR Standby,
  FirstArchNum will not be reset in the SQLOGCTL.LFH file during
  the restore.
  If the Primary database has not produced as many logfiles as the
  Standby database before and the HADR Primary is switched to
  Standby and back to Primary, the wrong value for FirstArchNum
  will make it to the Primary. This stops the Primary from
  archiving logfiles afterwards.
  

Local fix

• Drop the database on the HADR Standby before the restore.
  

Problem summary

• Converting a HADR Standby database to a Standard database and
  using this database, will generate new logfiles. These
  logfiles will get archived normally. When this database gets
  restored later on, to set it up again as HADR Standby,
  FirstArchNum will not be reset in the SQLOGCTL.LFH file during
  the restore.
  If the Primary database has not produced as many logfiles as the
  Standby database before and the HADR Primary is switched to
  Standby and back to Primary, the wrong value for FirstArchNum
  will make it to the Primary. This stops the Primary from
  archiving logfiles afterwards.
  

Problem conclusion

• First fixed in DB2 UDB Version 9.1, FixPak 6
  

Temporary fix

• See LOCAL FIX.
  

Comments

APAR Information

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

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

  LI73255

Fix information

• Fixed component name

  DB2 UDE ESE LIN

• Fixed component ID

  5765F4104

Applicable component levels

• R810 PSN

     UP

• R820 PSN

     UP

• R910 PSN

     UP

• R950 PSN

     UP