home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC63699 Status: Geschlossen

SQL0952N AND OTHER ERRORS MAY RESULT FROM
QUERYTIMEOUTINTERVAL=0 SETTING NOT TAKING EFFECT ON WINDOWS CLNT

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
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)
verfügbare FixPacks:
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

Lösung
Scheduled for fp2
Workaround
Specify DB2CLIINIPATH to point to db2cli.ini file
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.10.2009
13.05.2010
13.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
9.7.0.2 FixList