JR27947: DB2EXTSEC.EXE traps during SAP FP upgrade from FP3 to FP4

DB2 Version 9.1 Fix Pack 7  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 5   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

• During SAP fixpack install, it uses a response file with
  parameter NO_CONFIG=YES. After the successful install,
  db2extsec.exe is run manually. It traps because the code
  incorrectly expects the Registry has been set up with certain
  DB2 registry variables. With NO_CONFIG=YES, these variables
  were not set up. db2extsec.exe traps.
  

Local fix

• Run the command such that it provides the "old" db2 group names.
  
  For example:
  db2extsec -a DB2ADMNS -u DB2USERS -oldadmins DB2ADMNS -oldusers
  DB2USERS
  

Problem summary

• Users affected:
  All.
  
  Problem Description:
  See "ERROR DESCRIPTION" section for more details.
  
  Problem Summary:
  Without this APAR, customer is exposed to the issue
  as described in the "ERROR DESCRIPTION" section.
  

Problem conclusion

• First fixed in DB2 UDB Version V9.1, FixPak 5.
  

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

  DB2 UDB ESE WIN

• Fixed component ID

  5765F4101

Applicable component levels

• R910 PSY

     UP