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

THE DB2START COMMAND WITH RESTART OPTION MAY TAKE LONG TIME.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The db2start command with restart option may take long time. 
 
The node recovery by db2start with restart option may take long 
time. 
 
The following stack can be observed for db2start in this 
situation. 
 
nrecvfrom(??, ??, ??, ??, ??, ??) at 0x9000000001037c4 
.readloop()() at 0x900000015264c00 
.sqleIsHostAlive(char*)(??) at 0x9000000152647b8 
sqleIsHostAlive(char*)(??) at 0x900000015264598 
sqleIssueStartStop.fdpr.chunk.8(int,void*,char*,char*,sqlf_kcfd* 
,int,SQLE_INTERNAL_ARGS*,unsigned 
int,unsigned int,sqlca*)(0x900000018d82cbc, 0xfffffffffffab10, 
0x0, 0x0, 0x3000000000000000, 0xc310, 0x0, 0x0) at 
0x9000000151f7f90 
sqleProcessStartStop.fdpr.chunk.3(int,void*,SQLE_INTERNAL_ARGS*, 
sqlf_kcfd*,char*,int,unsigned 
int,unsigned int,sqlca*)(??, ??, ??, ??, ??, ??, ??, ??) at 
0x900000018d84134 
main(??, ??) at 0x100001558
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using db2start with restart option.                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The db2start command with restart option may take long time. * 
*                                                              * 
* The node recovery by db2start with restart option may take   * 
* long                                                         * 
* time.                                                        * 
*                                                              * 
* The following stack can be observed for db2start in this     * 
* situation.                                                   * 
*                                                              * 
* nrecvfrom(??, ??, ??, ??, ??, ??) at 0x9000000001037c4       * 
* .readloop()() at 0x900000015264c00                           * 
* .sqleIsHostAlive(char*)(??) at 0x9000000152647b8             * 
* sqleIsHostAlive(char*)(??) at 0x900000015264598              * 
* sqleIssueStartStop.fdpr.chunk.8(int,void*,char*,char*,sqlf_k * 
* cfd*                                                         * 
* ,int,SQLE_INTERNAL_ARGS*,unsigned                            * 
* int,unsigned int,sqlca*)(0x900000018d82cbc,                  * 
* 0xfffffffffffab10,                                           * 
* 0x0, 0x0, 0x3000000000000000, 0xc310, 0x0, 0x0) at           * 
* 0x9000000151f7f90                                            * 
* sqleProcessStartStop.fdpr.chunk.3(int,void*,SQLE_INTERNAL_AR * 
* GS*,                                                         * 
* sqlf_kcfd*,char*,int,unsigned                                * 
* int,unsigned int,sqlca*)(??, ??, ??, ??, ??, ??, ??, ??) at  * 
* 0x900000018d84134                                            * 
* main(??, ??) at 0x100001558                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.7 Fix Pack 5.                                  * 
****************************************************************
Local-Fix:
Not available
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
The issue was fixed in V9.7 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC78120 IC78121 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
10.08.2011
08.12.2011
08.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList