DB2 FOR LUW / DB2FORLUW / 970 - DB2

When calling the stored procedures automaint_set_policy or 
automaint_set_policyfile to update the Automatic Backup Policy 
file, the entries in the notification log and the db2diag.log 
regarding the policy changes shows a wrong value for 
logSpaceConsumedSinceLastBackup other than the one configured. 
 
e.g. 
For an update to the automatic backup policy with the following 
backup option 
<BackupCriteria numberOfFullBackups="1" 
timeSinceLastBackup="168" 
logSpaceConsumedSinceLastBackup="6400"/> 
 
It wrongly shows Log space consumed since last backup > 1638400 
MB 
It should be 6400 * 4KB = 25600 KB, instead of 1638400 MB 
 
db2diag.log entry: 
2011-07-18-05.14.42.705515-240 E34162A997         LEVEL: Warning 
PID     : 2244668              TID  : 1029        PROC : db2fmp 
(C) 
INSTANCE: ginaulak             NODE : 000 
EDUID   : 1029                 EDUNAME: db2fmp (C) 
FUNCTION: DB2 UDB, Policy, sqlpiAutomaintSetPolicySpCommon, 
probe:10 
MESSAGE : ADM10515I  The automatic maintenance policy 
"AUTO_BACKUP" has been 
          updated in database "ABC". The policy options have 
been updated from 
          "Backup criteria:   Number of full backups < 2 or 
Elapsed time size 
          last backup > 24 hours or  Log space consumed since 
last backup > 
          131072 MB  Backup mode: OFFLINE Backup policy decision 
target: 
          Backup Type: DISK, Pathname:  " to "Backup criteria: 
Number of full 
          backups < 1 or  Elapsed time size last backup > 168 
hours or  Log 
          space consumed since last backup > 1638400 MB  Backup 
mode: OFFLINE 
          Backup policy decision target:  Backup Type: DISK, 
Pathname:  ". 
 
notification log entry: 
ADM10515I  The automatic maintenance policy "AUTO_BACKUP" has 
been updated in 
database "ABC". The policy options have been updated from 
"Backup criteria: 
Number of full backups < 2 or  Elapsed time size last backup > 
24 hours or  Log 
space consumed since last backup > 131072 MB  Backup mode: 
OFFLINE Backup 
policy decision target:  Backup Type: DISK, Pathname:  " to 
"Backup criteria: 
Number of full backups < 1 or  Elapsed time size last backup > 
168 hours or 
Log space consumed since last backup > 1638400 MB  Backup mode: 
OFFLINE Backup 
policy decision target:  Backup Type: DISK, Pathname:  ".

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The Automatic Backup Policy can be configured, to take       * 
* backups when the a Log Space Consumed Since Last Backup is   * 
* greater than a certain value. This value is user provided.   * 
* When updating the policy, the notification log and           * 
* db2diag.log shows a value other than the one configured for. * 
* This is however just a wrong information being displayed.    * 
* Internally, the value configured for is still being          * 
* correctly used.                                              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to product version 9.07.005                          * 
****************************************************************

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
 

Problem was first fixed in Version 9.7 fixpack 5 . The fix 
should be applied to the DB2 LUW server.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC77591 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

18.07.2011
08.12.2011
08.12.2011

9.7.7.005,
9.7.FP5