JR31472: DB2 .NET CONFIGURATION IS NOT UPDATED AFTER A DB2 V9.1 FIXPAK INSTALL ON A (non-GA) LOWER FIXPAK LEVEL

DB2 Version 9.1 Fix Pack 7  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

• This problem happens in the following DB2 v9.1 Fixpak upgrade
  scenario:
    1). The DB2 copy to be upgraded is the default copy on the
  system,
    2). The base DB2 level is not the V9.1 GA, and
    3). The fixpak install is a GUI install, instead of a response
  file based silent install
  
  The problem is: The DB2 .NET configuration is not updated by the
  fixpak install. The DB2 .NET Data Provider of the lower fixpak
  level is still configured with the system.
  
  The reason for this problem is some configuration tasks are
  skipped during the fixpak upgrade install.
  

Local fix

• A simple workaround is to reset the default copy on the system
  after the installation.  You can take one of the following
  options:
  1). Use the default copy selection wizard:
      Start > Programs > IBM DB2 > [CopyName] > Set-up Tools >
  Default DB2 and Database Client Interface Selection wizard
  2). Use the DB2 copy switch command line:
       Open a DB2 command windows, and execute the following
  command:    db2swtch -d [copyName]
  
  This problem does not happen in a response file based silent
  fixpak upgrade install.
  

Problem summary

• Users affected :
  Users installing DB2 V9.1 FIXPAK.
  
  Problem descirption :
  DB2 .NET CONFIGURATION IS NOT UPDATED AFTER A DB2 V9.1 FIXPAK
  INSTALL ON A (non-GA) LOWER FIXPAK LEVEL
  
  Problem Summary :
  This problem happens in the following DB2 v9.1 Fixpak upgrade
  scenario:
  1). The DB2 copy to be upgraded is the default copy on the
  system,
  2). The base DB2 level is not the V9.1 GA, and
  3). The fixpak install is a GUI install, instead of a
  responsefile based silent install
  
  The problem is: The DB2 .NET configuration is not updated by
  thefixpak install.
  The DB2 .NET Data Provider of the lower fixpak  level is still
  configured with the system.
  The reason for this problem is some configuration tasks are
  skipped during the fixpak upgrade install.
  

Problem conclusion

• Problem was first fixed in Version 9.1 Fix Pack 7
  

Temporary fix

• A simple workaround is to reset the default copy on the system
  after the installation.
  You can take one of the following options:
    1). Use the default copy selection wizard :
  Start > Programs > IBM DB2 > [CopyName] > Set-up Tools >
  Default DB2 and Database Client Interface Selection wizard
    2). Use the DB2 copy switch command line:
  Open a DB2 command windows, and execute the following command :
  db2swtch -d [copyName]
  This problem does not happen in a response file based silent
  fixpak upgrade install.
  

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