Fixes are available
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
Running the db2swtch -l command or the "Set Default Tools" GUI to change the default copy of the v9 DB2 products causes db22013 and db22003 errors if the current default copy is a DB2 Runtime Client copy which was installed via Merge Module. This error is reported because the following set of registries is missing for the DB2 RunTime Client copy: HKEY_CLASSES_ROOT\IBMDADB2 HKEY_CLASSES_ROOT\IBMDADB2 Connection HKEY_CLASSES_ROOT\IBMDADB2 Advanced HKEY_CLASSES_ROOT\IBMDADB2 Enumerator HKEY_CLASSES_ROOT\IBMDADB2 Error Lookup
Local fix
As a workaround to switch the default copy, the customer can firstly promote the DB2 Runtime Client copy (which is the current default copy), demote it and then promote the other DB2 product. Ie, (1) From a DB2 windows of the default DB2 Runtime Client copy, run "db2lswtch -promote" (2) From the same DB2 windows, run "db2lswtch -demote" (3) From a DB2 windows of the DB2 copy (which will be set as the default copy), run "db2lswtch -promote"
Problem summary
ERROR DESCRIPTION: Running the db2swtch -l command or the "Set Default Tools" GUI to change the default copy of the v9 DB2 products causes db22013 and db22003 errors if the current default copy is a DB2 Runtime Client copy which was installed via Merge Module. This error is reported because the following set of registries is missing for the DB2 RunTime Client copy: HKEY_CLASSES_ROOT\IBMDADB2 HKEY_CLASSES_ROOT\IBMDADB2 Connection HKEY_CLASSES_ROOT\IBMDADB2 Advanced HKEY_CLASSES_ROOT\IBMDADB2 Enumerator HKEY_CLASSES_ROOT\IBMDADB2 Error Lookup LOCAL FIX: As a workaround to switch the default copy, the customer can firstly promote the DB2 Runtime Client copy (which is the current default copy), demote it and then promote the other DB2 product. Ie, (1) From a DB2 windows of the default DB2 Runtime Client copy, run "db2lswtch -promote" (2) From the same DB2 windows, run "db2lswtch -demote" (3) From a DB2 windows of the DB2 copy (which will be set as the default copy), run "db2lswtch -promote"
Problem conclusion
First fixed in DB2 UDB Version 9.1 Fixpak 7
Temporary fix
Comments
APAR Information
APAR number
JR30853
Reported component name
DB2 UDB ESE WIN
Reported component ID
5765F4101
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-10-21
Closed date
2009-05-22
Last modified date
2009-05-22
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
R810 PSN
UP
R820 PSN
UP
R950 PSN
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]
Document Information
Modified date:
06 October 2021