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

SYSIBMADM.LOG_UTILIZATION IS RETURNING SQL0801N on standby

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
SYSIBMADM.LOG_UTILIZATION is returning  SQL0801N  when the
outputs  returned are supposed to be zero.

Example,

=> db2 "select LOG_UTILIZATION_PERCENT from
SYSIBMADM.LOG_UTILIZATION"

LOG_UTILIZATION_PERCENT
-----------------------
SQL0801N Division by zero was attempted. SQLSTATE=22012

This can be reproduced  easily in a  HADR standby database where
all the columns  returned by  LOG_UTILIZATION will be zero.
As a result of that  the  percentage calculation will  have a
division by zero.

Instead of  returning   SQL0801N  it should  return a zero.

The internal counters that track log usage are only updated
during runtime.
HADR standby is considered to be in recovery state (not runtime
state).
So, these values are not tracked.
As a result the monitor will always see 0 for the columns
against this function in the standby.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Any db2 level trying to use LOG_UTILIZATION                  *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 Version 11 Fix Pack 3                         *
****************************************************************
Local Fix:
Don't  run this function in  a  db2 HADR standby.  Or, ignore
the SQL0801N message.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.05.2017
24.04.2020
24.04.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)