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 IC96255 Status: Geschlossen

CONNECTION HANGS ON ACR AFTER COMMUNICATION ERROR. ALTERNATE SERVER
INFORMATION from the database catalog IS NOT USED.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
ACR is not started after hitting communication error. ACR does 
not look at alternate server information in directory. The 
defect was introduced in v9.7.5. 
 
The problem can happen for connections established 
from non-JDBC clients (including CLP) and from 
non-JDBC drivers.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.1 fp3                                         * 
****************************************************************
Local-Fix:
To work-around the issue explicitly enable ACR ( enableACR) in 
db2dsdriver.cfg, set keepAliveTimeout and tcpipConnectTimeout. 
See the example appended below. 
 
Example to enableACR in db2dsdriver.cfg 
<configuration> 
   <DSN_Collection> 
      <dsn alias="sample" name="sample" host="samplehost" 
port="xxxxxx"/> 
      </dsn> 
   </DSN_Collection> 
   <databases> 
      <database name="sample" host="samplehost" port="xxxxxx"> 
         <ACR> 
            <parameter name="enableACR" value="true"/> 
         </ACR> 
         <parameter name="keepAliveTimeout" value="15"/> 
         <parameter name="TcpipConnectTimeout" value="2"/> 
      </database> 
  </databases> 
</configuration>
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
First fixed in v10.1 fp3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
25.09.2013
18.10.2013
18.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList