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

INCORRECT APPLICATION ID MAY BE WRITTEN IN DB2AUDIT LOG

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When audit log is taken for validate category record, the 
authentication event may have incorrect application id for 
failing authentication. 
 
The following an example for failing authentication from a 
remote client with invalid user id and password. Its application 
id is recorded in a wrong format. 
 
timestamp=2012-03-16-14.49.19.722368; 
  category=VALIDATE; 
  audit event=AUTHENTICATION; 
  event correlator=2; 
  event status=-30082; 
  database=SAMPLE; 
  userid=e95q5f; 
  execution id=REMOTEAPP; 
  origin node=0; 
  coordinator node=0; 
  application id=09BDCC35.07BA.120316054921; 
  application name=odbcad32.exe; 
  auth type=SERVER; 
  plugin name=IBMOSauthserver; 
 
The following is a successful authentication event record for 
the same remote client. Its application id is recorded 
correctly. 
 
timestamp=2012-03-16-14.15.53.539512; 
  category=VALIDATE; 
  audit event=AUTHENTICATION; 
  event correlator=2; 
  event status=0; 
  database=SAMPLE; 
  userid=e95q5f; 
  authid=E95Q5F; 
  execution id=REMOTEAPP; 
  origin node=0; 
  coordinator node=0; 
  application id=9.189.204.53.11270.120316051553; 
  application name=odbcad32.exe; 
  auth type=SERVER; 
  plugin name=IBMOSauthserver;
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* User using db2audit                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.1 Fix Pack 2.                          * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 10.1 Fix Pack 2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2012
31.12.2012
31.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList