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

DB2LOGMGR EDU CRASH IN SPRINTF CALLED FROM SQLPGRETRIEVELOGDISK ON HADR
STANDBY REINTEGRATION

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
When both LOGARCHMETH1 and/or LOGARCHMETH2/FAILARCHPATH are set, 
 
a standby server will attempt to search each location for a 
later version of the log file after seeing this message in the 
db2diag.log : 
 
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMOpenLog, probe:600 
MESSAGE : Extent 203822 in log path may be stale. Trying 
archive. 
 
It's possible that after searching the 1st location ( pointed to 
by LOGARCHMETH1 ), the retrieve request used by the db2logmgr 
gets freed. This then can potentially lead to a crash in the 
db2logmgr edu upon trying the 2nd location ( e.g. pointed to by 
FAILARCHPATH ). 
 
A trap file may show the following list of functions : 
 
strlen 
_doprnt 
sprintf 
sqlpgRetrieveLogDisk 
sqlpgRetrieveLogFile 
sqlpgHandleLogMgrPost 
...
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Environment using HADR                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* A standby database server may abend in the db2logmgr         * 
* eduunder specific circumstances, detailed in the             * 
* apardescription.                                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the database server to V9.5 Fixpak 7                 * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
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

Lösung
This problem was first fixed in V9.5 Fixpak 7
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC70590 IC70591 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
07.06.2010
15.11.2010
15.11.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.
Problem behoben lt. FixList in der Version
9.1.0.7 FixList
9.5.0.7 FixList