75 ways to demystify DB2 #73: Techtip : LinuxShield (McAfee) may cause permission issue on DB2 files.

Body

Recently we have seen a lot of scenarios where LinuxShield (McAfee) was playing a notorious role, so sharing this experience here.
What we observed was, during database connection, crash recovery process etc LinuxShield (McAfee) caused permission issue when DB2 was trying to access a container.
 

Here is an example of db2diag.log entry :

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:24:40
DATA #2 : File name, 65 bytes
/home/db2inst1/NODE0000/SQL00001/SQLT0000.0/SQL00002.DAT
 

Once you confirm the actual file/dir permissions and ownerships are good, you may write your small C program which can open() the file outside db2 and verify that file itself has no issues then check the presence of LinuxShield (McAfee) using ps -elf and if its present then try to disable it temporarily until the DB2 problem is resolved. You will need to open a ticket with Linux or McAfee support to debug this notorious behavior of LinuxShield (McAfee).