DB2 - Problembeschreibung
Problem IC75523 | Status: Geschlossen |
DB2 "CONNECT TO DBNAME ..." MAY GETS SQL1013N AT A HEAVY WORKLOAD SYSTEM | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 UDB Version 9.7 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error description field for more information. * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.7 FixPack 5. * **************************************************************** | |
Local-Fix: | |
set DB2RQTIME=60 and DB2IQTIME=60 may mitigate the problem. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 5. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 03.04.2011 21.12.2011 21.12.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP5 | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |