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

A LOG FILE COULD BE ARCHIVED FROM STANDBY SERVER WHEN DEACTIVATE DATABASE
COMMAND IS ISSUED ON STANDBY SERVER

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
In a HADR setup, transaction log files should be archived only 
by the primary server. Due to an internal logic error, a log 
file could be archived by the standby server when a deactivate 
database command is issued. 
 
Here's an example of the db2diag.log entries from the primary 
HADR server i.e. 
 
<snip> 
 
2011-04-14-13.15.06.020862-240 E57184A373         LEVEL: Info 
PID     : 3109096              TID  : 2315        PROC : db2sysc 
INSTANCE: xxxxxxx              NODE : 000 
EDUID   : 2315                 EDUNAME: db2logmgr (xxxxxx) 
FUNCTION: DB2 UDB, data protection services, 
sqlpgArchiveLogFile, probe:3108 
DATA #1 : <preformatted> 
Started archive for log file S0028570.LOG. 
 
2011-04-14-13.15.06.030289-240 E57558A494         LEVEL: Info 
PID     : 3109096              TID  : 2315        PROC : db2sysc 
INSTANCE: xxxxxxx              NODE : 000 
EDUID   : 2315                 EDUNAME: db2logmgr (xxxxxx) 
FUNCTION: DB2 UDB, data protection services, 
sqlpgArchiveLogFile, probe:3180 
DATA #1 : <preformatted> 
Completed archive for log file S0028570.LOG to 
/xxxx/xxxx/archive/xxxxxxx/xxxxxx/NODE0000/C0000000/ from 
/xxxxx/xxxxxxx/xxxxxxx/NODE0000/SQL00001/SQLOGDIR/. 
... 
 
Here's an example of the db2diag.log entries from the standby 
server (Note: S00285709.LOG should not be archived on the 
standby) i.e. 
 
<snip> 
 
2011-04-14-13.15.19.997444-240 I66548A466         LEVEL: Warning 
PID     : 954478               TID  : 1801        PROC : db2sysc 
INSTANCE: xxxxxxx              NODE : 000         DB   : xxxxxx 
APPHDL  : 0-29                 APPID: 
*xxxxx.xxxxxxx.xxxxxxxxxxxx 
AUTHID  : xxxxxxx 
EDUID   : 1801                 EDUNAME: db2agent (xxxxxx) 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrEduShutdown, probe:29002 
MESSAGE : Info: HADR Shutdown has completed. 
 
2011-04-14-13.15.19.998278-240 E67015A373         LEVEL: Info 
PID     : 954478               TID  : 2368        PROC : db2sysc 
INSTANCE: xxxxxxx              NODE : 000 
EDUID   : 2368                 EDUNAME: db2logmgr (xxxxxx) 
FUNCTION: DB2 UDB, data protection services, 
sqlpgArchiveLogFile, probe:3108 
DATA #1 : <preformatted> 
Started archive for log file S0028570.LOG. 
 
2011-04-14-13.15.20.019806-240 E67389A494         LEVEL: Info 
PID     : 954478               TID  : 2368        PROC : db2sysc 
INSTANCE: xxxxxxx              NODE : 000 
EDUID   : 2368                 EDUNAME: db2logmgr (xxxxxx) 
FUNCTION: DB2 UDB, data protection services, 
sqlpgArchiveLogFile, probe:3180 
DATA #1 : <preformatted> 
Completed archive for log file S0028570.LOG to 
/xxxx/xxxx/archive/xxxxxxx/xxxxxx/NODE0000/C0000000/ 
from /xxxxx/xxxxxxx/xxxxxxx/NODE0000/SQL00001/SQLOGDIR/.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 HADR users on all platforms                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* log archive can happen on HADR standby. This usually does    * 
* not cause any trouble for customer, but may lead to some     * 
* unpredictable issues.                                        * 
* When hitting this, customer can see the symptoms described   * 
* in "Error Description"                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v97fp5                                        * 
****************************************************************
Local-Fix:
Avoid issue the DEACTIVATE DATABASE command on the standby HADR 
server.
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
after applying DB2 v97fp5, standby will not try archive log 
file.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.04.2011
22.12.2011
22.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList