DB2 Audit operations may fail with DIA8506C error in db2diag.log

Technote (troubleshooting)


Problem(Abstract)

db2diag.log contains various errors such as 'DIA8506C Unexpected end of file was reached' or 'Unexpected System Error' or RETCODE such as 'ZRC=0x870F0009' 'ZRC=0x875C00CD' or sqlcode: -1042

Symptom

The following messages can be seen in db2diag.log when DB2 attempts to audit.

2013-11-08-00.08.39.394606-300 I2075E629 LEVEL: Error
PID : 27045 TID : 46913005021504 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : FOO
APPHDL : 0-33 APPID: *LOCAL.db2inst1.131108050839
HOSTNAME: db2host
EDUID : 18 EDUNAME: db2agent (FOO)
FUNCTION: DB2 UDB, bsu security, sqlexAuditOpenAdjust, probe:149
RETCODE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does not exist"
DIA8506C Unexpected end of file was reached.
DATA #1 : Hexdump, 4 bytes
0x00002AAAC8FFB380 : 0900 0F87 ....

2013-11-08-00.08.39.473542-300 I2705E554 LEVEL: Error
PID : 27045 TID : 46913005021504 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : FOO
APPHDL : 0-33 APPID: *LOCAL.db2inst1.131108050839
HOSTNAME: db2host
EDUID : 18 EDUNAME: db2agent (FOO)
FUNCTION: DB2 UDB, bsu security, sqlexAuditWriteBufferToDisk, probe:14164
MESSAGE : ZRC=0x875C00CD=-2024013619=SQLEX_UNEXPECTED_SYSERR
"Unexpected System Error"
DATA #1 : Hex integer, 4 bytes
0x40000011

...

2013-11-08-00.08.39.474498-300 I4308E930 LEVEL: Error
PID : 27045 TID : 46913005021504 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : FOO
APPHDL : 0-33 APPID: *LOCAL.db2inst1.131108050839
HOSTNAME: db2host
EDUID : 18 EDUNAME: db2agent (FOO)
FUNCTION: DB2 UDB, bsu security, sqlexAuditData::logEvent, probe:1089
MESSAGE : ZRC=0x875C00CD=-2024013619=SQLEX_UNEXPECTED_SYSERR
"Unexpected System Error"
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1042 sqlerrml: 3
sqlerrmc: 205
sqlerrp : SQLEXADT
sqlerrd : (1) 0x875C00CD (2) 0x000000CD (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:


Cause

db2audit file for the database is either corrupt or has wrong file size.


Resolving the problem

Find the corresponding Audit Data Path by issuing 'db2audit describe' command. Then rename the audit file for the database that is reporting the error in db2diag.log.

For example:
db2audit describe
DB2 AUDIT SETTINGS:

Audit active: "TRUE "
Log audit events: "FAILURE"
Log checking events: "FAILURE"
Log object maintenance events: "FAILURE"
Log security maintenance events: "FAILURE"
Log system administrator events: "FAILURE"
Log validate events: "FAILURE"
Log context events: "FAILURE"
Return SQLCA on audit error: "FALSE "
Audit Data Path: "/home/db2inst1/auditdata/"
Audit Archive Path: ""

ls -al /home/db2inst1/audidata/
-rw------- 1 mayooran pdxdb2 3 2013-11-07 23:54 db2audit.db.FOO.log.0
-rw------- 1 mayooran pdxdb2 30869 2013-11-08 00:58 db2audit.instance.log.0

In this example, the audit file db2audit.db.FOO.log.0 should be renamed to resolve the issue.

Related information

DB2 operations may fail with SQL0902C and DIA8506C mess

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

9.5, 9.7, 9.8, 10.1, 10.5

Operating system(s):

AIX, Linux, Solaris, Windows

Software edition:

Advanced Enterprise Server, Enterprise Server, Express, Express-C, Personal, Workgroup Server

Reference #:

1655610

Modified date:

2014-01-22

Translate my page

Machine Translation

Content navigation