DB2 - Problem description
Problem IC75373 | Status: Closed |
SQL8002N FROM 32 BIT CLI DRIVER TO HOST ON SUN64 MACHINE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
Attempting to connect to a host system using the 32 bit IBM Data Server Driver on a 64 bit Sun Solaris system will result in the following error message: [IBM][CLI Driver] SQL8002N An attempt to connect to a host failed due to a missing DB2 Connect product or invalid license. SQLSTATE=42968 This will occur even if a suitable license is placed in the /license subdirectory of the Driver installation path. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Customers using 32 bit Data Server Driver for Sun SPARC * **************************************************************** * PROBLEM DESCRIPTION: * * Attempting to connect to a host system using the 32 bit IBM * * Data * * Server Driver on a 64 bit Sun Solaris system will result in * * the * * following error message: * * * * * * * * [IBM][CLI Driver] SQL8002N An attempt to connect to a host * * * * failed due to a missing DB2 Connect product or invalid * * license. * * SQLSTATE=42968 * * * * * * * * This will occur even if a suitable license is placed in the * * * * /license subdirectory of the Driver installation path. * * * * The key differentiator for this APAR is that the "nodelock" * * file * * found in the "license" subdirectory will be write-only. * **************************************************************** * RECOMMENDATION: * * Upgrade to v9.5 FP8. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
Fixed in v9.5 FP8. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.03.2011 30.06.2011 30.06.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.8 |