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

DB2AUDIT: USE OF UNINITIALIZED OBJECT SCHEMA IN AUDIT DATA.

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
The db2audit might produce audit data with corrupted object 
schema (objschema) if the package is being rebound. This problem 
comes up due to use of uninitialized object schema. 
The following steps illustrate how this problem can happen. 
 
1. Enable audit with category checking. 
 
db2 create audit policy pol1 categories checking status both 
error type normal 
db2 audit database using policy pol1 
 
2. Rebind some package(s) to generate audit events. 
Note: upgrade database or db2updvX command will rebind many 
system packages, then it might produce the corruption.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher               * 
****************************************************************
Local Fix:
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First fixed in Db2 11.1 Mod 3 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.08.2017
19.03.2018
19.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)