IZ40408: DB2 AUDIT MAY CREATE AN EMPTY AUDIT LOG.

DB2 Version 9.5 Fix Pack 4  for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• DB2 audit may create an audit log file of zero bytes (empty)
  when the files system where the logs are located has ran out of
  space.
  DB2 will be able to create the audit log but unable to write
  the header to the log.   The empty audit log file (without a
  proper
  header) is consider corrupted and DB2 will report an error.
  The following error will be logged in db2diag.log:
  
  2008-12-19-15.51.39.993712-300 I1418E607           LEVEL: Error
  PID     : 20078                TID  : 47115795425600PROC :
  db2sysc
  INSTANCE: db2user              NODE : 000          DB   : SAMPLE
  APPHDL  : 0-1380               APPID: *LOCAL.alvinf.081219205139
  EDUID   : 16                   EDUNAME: db2agent (SAMPLE)
  FUNCTION: DB2 UDB, bsu security, sqlexAuditOpenAdjust, probe:150
  RETCODE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does not
  exist"
            DIA8506C Unexpected end of file was reached.
  DATA #1 : Hexdump, 4 bytes
  0x00002ADA003F0848 : 0900 0F87
  ....
  2008-12-19-15.51.39.998418-300 I2026E532           LEVEL: Error
  PID     : 20078                TID  : 47115795425600PROC :
  db2sysc
  INSTANCE: db2user              NODE : 000          DB   : SAMPLE
  APPHDL  : 0-1380               APPID: *LOCAL.alvinf.081219205139
  EDUID   : 16                   EDUNAME: db2agent (SAMPLE)
  FUNCTION: DB2 UDB, bsu security, sqlexAuditWriteBufferToDisk,
  probe:12937
  MESSAGE : ZRC=0x875C00CD=-2024013619=SQLEX_UNEXPECTED_SYSERR
            "Unexpected System Error"
  DATA #1 : Hex integer, 4 bytes
  0x40000011
  

Local fix

• Remove the zero size DB2 audit log file.
  

Problem summary

• DB2 audit may create an audit log file of zero bytes (empty)
  when the files system where the logs are located has ran out of
  space.
  DB2 will be able to create the audit log but unable to write
  the header to the log.   The empty audit log file (without a
  proper
  header) is consider corrupted and DB2 will report an error.
  

Problem conclusion

• Problem was first fixed in DB2 UDB Version 9.5 FixPack 4.
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  DB2 UDB WSE AIX

• Fixed component ID

  5765F3500

Applicable component levels

• R950 PSN

     UP