home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC97586 Status: Closed

SETTING HADR_SYNCMODE TO SUPERASYNC FLOODS DB2DIAG.LOG WITH "SAVING
PARTIAL PAGE" MESSAGES

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When setting HADR SYNCMODE to SUPERASYNC, the db2diag.log is 
getting flooded with the following Informational message: 
 
2013-10-18-06.11.36.191957-240 I511574532A361     LEVEL: Warning 
PID     : 38797556             TID  : 4385        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 4385                 EDUNAME: db2lfr (SAMPLE) 0 
FUNCTION: DB2 UDB, recovery manager, sqlplfrVerifyLogPages, 
probe:1750 
MESSAGE : Saving partial page, pageLso is 2998996157559 
 
This APAR will move these messages to DIAGLEVEL 4.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 fix pack 10.                             * 
****************************************************************
Local Fix:
N/A
Solution
First fixed in DB2 v9.7 fix pack 10.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.11.2013
21.01.2015
21.01.2015
Problem solved at the following versions (IBM BugInfos)
9.7.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.10 FixList