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

ERROR SQL0843N WHEN CONNECTING TO AN INFORMIX DATABASE WITH A NAME LONGER
THAN 18 CHARACTERS

Produkt:
DB2 CONNECT / DB2CONNCT / A50 - DB2
Problembeschreibung:
Trying to connect to an Informix databases with a name longer 
than 18 character will fail with the following errors: 
 
  ERROR [08003] [IBM] SQL0843N  The server name does not specify 
an existing connection.  SQLSTATE=08003 
 
  ERROR [58004] [IBM] CLI0119E  Unexpected system failure. 
SQLSTATE=58004 
  ERROR [01002] [IBM] CLI0001W  Disconnect error. SQLSTATE=01002
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v10.5 Fixpack 4 or Higher                 * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
Fixed in DB2 LUW v10.5 Fixpack 4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.05.2014
08.09.2014
08.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList