IC87902: INCORRECT APPLICATION ID MAY BE WRITTEN IN DB2AUDIT LOG

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error 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;
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * User using db2audit                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Version 10.1 Fix Pack 2.                          *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in DB2 UDB Version 10.1 Fix Pack 2.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC87902

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-04

  • Closed date

    2012-12-31

  • Last modified date

    2012-12-31

  • APAR is sysrouted FROM one or more of the following:

    IC82079

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RA10 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

10.1

Reference #:

IC87902

Modified date:

2012-12-31

Translate my page

Machine Translation

Content navigation