|
Problem IC63699
|
Status: Closed |
SQL0952N AND OTHER ERRORS MAY RESULT FROM QUERYTIMEOUTINTERVAL=0 SETTING NOT TAKING EFFECT ON WINDOWS CLNT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If DB2CLIINIPATH is not set, DB2 CLI might not read the correct
keyword value for some of the keywords like
QUERYTIMEOUTINTERVAL, even though "db2 get cli cfg " shows
correct value. This can happen only with keywords which are
metioned in Common section of the .ini file
This problem will be seen in v95 and v97 releases. and is
specific to windows environment. |
| Problem Summary: |
See prob description |
| Local Fix: |
Work Around is to set the DB2CLIINIPATH environment variable to
the db2cli.ini location (By default it points to the path
contained in the variable DB2INSTPROF) |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Scheduled for fp2 |
| Workaround |
Specify DB2CLIINIPATH to point to db2cli.ini file |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.10.2009
13.05.2010
13.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
