Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC74927 Status: Closed

DB2 "CONNECT TO DBNAME ..." MAY GETS SQL1013N AT A HEAVY WORKLOAD
SYSTEM

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
You may fail to connect and get SQL1013N via CLP even specifying 
correct parameters such as: 
db2 "connect to dbname ..." 
Here is a complete returning message: 
SQL1013N The database alias name or database name " " could not 
be found. 
 
db2diag.log may have below message: 
... 
2011-02-22-23.16.52.725569+540 I2060657A670       LEVEL: Warning 
PID     : 6193250              TID  : 1           PROC : db2bp 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 1 
FUNCTION: DB2 UDB, Connection Manager, sqleUCgetDirInfo, 
probe:1012 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1013   sqlerrml: 1 
 sqlerrmc: 
 sqlerrp : SQLEUCCM 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
... 
 
This problem is caused by a DB2 coding, unexpects this type of 
heavy workload situation. 
We will modify source code as DB2 can handle properly.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.5                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.5 FixPack 8.                            * 
****************************************************************
Local Fix:
set DB2RQTIME=60 and DB2IQTIME=60 may mitigate the problem.
available fix packs:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 9.5 FixPack 8.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC75523 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.03.2011
30.06.2011
30.06.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.