Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC92910 Status: Closed

DB2TS COMMAND RETURN ERROR MESSAGE CIE00756 CONNECT FAILED ON H NAMED
"LOCALHOST" AND PORT ..."

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The db2ts  "create index test_idx for text on 
 
test(name) connect to db1" 
 
 
 
returns the following error message even though the port is 
 
available and listening 
 
 
 
SQL20427N  An error occurred during a text search administration 
 
procedure or command. The error message is "CIE00756 Connect 
 
failed on host named "localhost" and port "5936". ". 
 
SQLSTATE=38H14
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fix Pack 3 or newer fix pack             * 
****************************************************************
Local Fix:
available fix packs:
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

Solution
Problem First Fixed in DB2 Version 10.1 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.06.2013
03.10.2013
03.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList