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 IC77591 Status: Closed

AUTOMATIC BACKUP POLICY UPDATE DISPLAYS WRONG VALUE FOR LOGSPACE
CONSUMEDSINCELASTBACKUP IN THE DB2DIAG.LOG AND NOTIFICATION LOG

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
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:  ".
Problem Summary:
**************************************************************** 
* 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.05.009                          * 
****************************************************************
Local Fix:
Solution
Problem was first fixed in Version 9.5 fixpack 9 . The fix 
should be applied to the DB2 LUW server.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.07.2011
29.07.2011
29.07.2011
Problem solved at the following versions (IBM BugInfos)
9.5.5.009,
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)