Troubleshooting
Problem
I have configured Guardium S-TAP to monitor DB2 traffic. Though Guardium S-TAP captures DB2 traffic properly, I keep seeing warnings in db2diag.log: "Shmem_access /.guard_writer0 failed Error opening shared memory area errno=1 err=8". Note that I don't use DB2_EXIT to monitor DB2 traffic.
Symptom
Following warnings repeatedly shown in db2diag.log:
2016-10-21-17.24.02.442147+480 E193444960A506 LEVEL: Severe
PID : 24600000 TID : 8779 PROC : db2sysc 0
INSTANCE: db2inst NODE : 000 DB : SAMPLEDB
APPHDL : 0-376
HOSTNAME: testhost01
EDUID : 8779 EDUNAME: db2agent () 0
FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcCommexitLogMessage,
probe:234
DATA #1 : String with size, 91 bytes
WARNING: Shmem_access /.guard_writer0 failed Error opening shared memory area
errno=1 err=8
Cause
The user doesn't use the DB2_EXIT driver for the Guardium S-TAP, but it seems like DB2 is looking for the driver. It may have been configured sometime in the past.
Resolving The Problem
User can check for a couple of things:
1. From the db2 command line processor, run:
get database manager configuration
See if the following entry exists:
Communication buffer exit library list (COMM_EXIT_LIST) = libguard_db2_exit_64
If it does, it needs to be removed:
UPDATE DBM CFG USING COMM_EXIT_LIST NULL
2. Also check the commexit directory (~/sqllib/security64/plugin/commexit) and delete or move the following file if it exists:
db2inst4@leopard:~/sqllib/security64/plugin/commexit> ls libguard_db2_exit_64.so
Note that DB2 must be restarted after these changes. Then you should no longer see those warnings in db2diag.log.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21994576