IZ45208: Downlevel DB2 instance wont autostart after install higher level

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

• If you have 2 versions of DB2 on the same machine configured
  correctly for autostart (DB2AUTOSTART set to yes), only the
  latest version will autostart due to library incompatibility
  with the old version.  Even if the instance is migrated from a
  lower level, the newly migrated instance will autostart, but the
  older ones will not. The fix for APAR IZ45208 will resolve this.
  
  There should only be 1 entry (latest DB2 version) in
  /etc/inittab.  The db2fmcu is then expected to start all the
  other instances (same version AND older versions of DB2) on the
  same machine. However due to this APAR, the older versions of
  DB2 will not autostart.
  
  The solution is to upgrade the most current DB2 version
  (whichever one has is in the /etc/inittab) to the fixpack that
  contains the fix to resolve it.
  

Local fix

Problem summary

• Downlevel DB2 instance wont autostart after install higher level
  
  ERROR DESCRIPTION:
  
  If you have 2 versions of DB2 on the same machine configured
  correctly for autostart (DB2AUTOSTART set to yes), only the
  latest version will autostart due to library incompatibility
  with the old version.  Even if the instance is migrated from a
  lower level, the newly migrated instance will autostart, but the
  older ones will not. The fix for APAR IZ45208 will resolve this.
  
  There should only be 1 entry (latest DB2 version) in
  /etc/inittab.  The db2fmcu is then expected to start all the
  other instances (same version AND older versions of DB2) on the
  same machine. However due to this APAR, the older versions of
  DB2 will not autostart.
  
  The solution is to upgrade the most current DB2 version
  (whichever one has is in the /etc/inittab) to the fixpack that
  contains the fix to resolve it.
  

Problem conclusion

• Users Affected: ALL
  
  First fixed in v9.1 FP8
  

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:

  IZ45209 IC63992 IC69274

Fix information

• Fixed component name

  DB2 CUE AIX

• Fixed component ID

  5724B6200

Applicable component levels

• R910 PSY

     UP