Question & Answer
Question
While the Anti-virus software is actively scanning, DB2 can report SQLO_ACCD "Access Denied" errors. The Anti-virus software locks the file during scanning, and prevents DB2 from accessing it. Which DB2 directories need to be excluded from Anti-virus scanning to prevent the errors from occurring?
This is an example of the db2diag.log errors that are being logged:
This is an example of the db2diag.log errors that are being logged:
2017-06-09-03.38.06.412868-240 E790514E1231 LEVEL: Error (OS)
PID : 30113 TID : 140072015881984 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-8769 APPID: *LOCAL.db2inst1.170611194451
AUTHID : DB2INST1 HOSTNAME: xxx.xxx.xxx EDUID : 684
EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80 MESSAGE : ZRC=0x840F0001=-2079391743=SQLO_ACCD "Access Denied" DIA8701C Access denied for resource "",
operating system return code was "". CALLED : OS, -, open OSERR: EACCES (13) DATA #1 :
Codepath, 8 bytes 4:11:18:19:20:40 DATA #2 : File name,
62 bytes /user/db2inst1/db2inst1/NODE0000/SAMPLE/T0000002/C0000000.LRG DATA #3 :
SQO Open File Options, PD_TYPE_SQO_FILE_OPEN_OPTIONS, 4 bytes SQLO_REVISE, SQLO_READWRITE,
SQLO_SHAREWRITE, SQLO_FORCE_NON_BUFFERED DATA #4 :
Hex integer, 4 bytes 0x00000180 DATA #5 : signed integer, 4 bytes 0 DATA #6 :
Hex integer, 4 bytes 0x00004000 DATA #7 : String, 105 bytes Search for ossError*Analysis probe point after this log entry for further self-diagnosis of this problem. 2017-06-09-03.38.06.413617-240 I791746E5707 LEVEL: Error (OS) PID : 30113 TID : 140072015881984 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-8769 APPID: *LOCAL.db2inst1.170611194451 AUTHID : DB2INST1 HOSTNAME: xxx.xxx.xxx
EDUID : 684 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 Common, OSSe,
EDUID : 684 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 Common, OSSe,
ossErrorIOAnalysis, probe:100 CALLED : OS, -, open OSERR: EACCES (13) DATA #1 : String,
160 bytes A total of 2 analysis will be performed : - User info - Path access permission Target file = /user/db2inst1/db2inst1/NODE0000/SAMPLE/T0000002/C0000000.LRG DATA #2 :
String, 188 bytes Real user ID of current process = 1022 Effective user ID of current process = 1022 Real group ID of current process = 1022 Effective group ID of current process = 1022 DATA #3 : String, 41 bytes current sbrk(0) value: 0x00000000012c0000 DATA #4 : String, 364 bytes Information of each subdirectory leading up to the first inaccessible one is shown in the format below :
[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"--","Platform":[{"code":"PF016","label":"Linux"}],"Version":"10.5;11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
18 June 2026
UID
swg22004989
