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

IN PURESCALE DB2 LOG HEADER (XHDR) UPDATION INFO IS DUMPED AS WARNING
,WHICH SHOULD BE AT INFO LEVEL

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
In  Purescale  , 
 
We observe  the following messages continiously 
 
2014-09-01-02.22.11.722641+330 E40910681A2078       LEVEL: 
Warning 
PID     : 4587740              TID : 56163          PROC : 
db2sysc 1 
INSTANCE: db2ipist             NODE : 001           DB   : 
PRODIST 
HOSTNAME: pneftswdb0q2 
 
EDUID   : 56163                EDUNAME: db2hadrp.1.1 (PRODIST) 1 
 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEdu:: 
 
hdrEduP, probe:5234 
 
DATA #1 : String, 32 bytes 
 
Waiting for closed bit to be set 
 
DATA #2 : SQLPG_XHDR, PD_TYPE_SQLPG_XHDR, 2048 bytes 
 
Validity Check 1 = 155 
 
Format Version = 13 
 
alVersion = V:10 R:5 M:0 F:3 I:0 SB:0 
 
Log Extent State = 0x00010001 
 
                                   - SQLPG_State_Init 
 
                                   - 
SQLPG_State_FileEntryNum1_Valid 
Signature = IBMLOG 
 
Partition = 0 
 
Log Stream = 1 
 
Topology Life ID = 1396543046 
2014-04-03-16.37.26.000000 GMT 
Compression Mode = 0 (UNCOMPRESSED) 
 
Segment Size = 0 
 
Extent Number = 5464 
 
Extent Size = 32768 
 
Number of Pages = 32768 
 
Previous Extent ID = 1409457290 
2014-08-31-03.54.50.000000 GMT 
Database Log ID = 1396543046 
2014-04-03-16.37.26.000000 GMT 
Current Extent ID = 1409462868 
2014-08-31-05.27.48.000000 GMT 
Original Current Extent ID = 1409176967         2014-08-27- 
 
22.02.47.000000 GMT 
 
firstLso = 704554012673 maps to 000000A4D8C00010 
 
minTruncOffset = 0 
 
fileEntryNum1 = 16845 
 
fileEntryNum2 = 0 
 
logFileChainId = 4 
 
lsnBase = 00000000D96CDBB7 
 
logChainInfo[0] = 19551803 000000000E38186C 1398289089 3145 
 
logChainInfo[1] = 0 0000000000000000 1396543046 6239 
 
logChainInfo[2] = 19551803 000000000E38186C 1398289089 3145 
 
logChainInfo[3] = 18446744073709551615 FFFFFFFFFFFFFFFF 
4294967295 0 
gfaNumEntries = 0 
 
gfa(Global FRALA Array) : 
 
        idx   gfaLogStreamId  gfaExtNum 
 
        0 0 6552 
 
        1 1 5290 
 
      (All-zero GFA entries after gfaNumEntries entries are 
omitted) 
firstLFSInExtent = 491921636 
 
firstLFSInNextExtent = 0 
 
lastLfsInExtent = 18446744073709551615 
 
lastLsnInExtent = FFFFFFFFFFFFFFFF 
 
firstRecLso = 704554013724 
 
hbGroupNextLfsLsn = 0/0000000000000000 
 
hbStreamLastLfsLsn = 0/0000000000000000 
 
hbStreamDiskLso = 0 
 
xhdrCheckSum = 9B369809 expectedCheckSum 9B369809 
 
 
This is a normal condition, where the HADR primary needs to wait 
for some final updates to be made in the log file header (XHDR) 
before shipping it to standby. 
 
The condition is not supposed to last long, as these final 
updates are supposed to be made and the LFR will see them 
 
We  are  making  the message as  Info level.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 PureScale users                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* We  observe  db2 log header  info  dumped continiously as    * 
* Warning.                                                     * 
*                                                              * 
* We  will change  the message  level  to Info.                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Ignore the message.                                          * 
****************************************************************
Local-Fix:
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Kommentar
Problem is first fixed in db2 v10.5 fp7
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.09.2014
25.01.2016
25.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList