IBM Support

Guardium S-TAP related Warning in db2diag.log - Error opening shared memory area errno=1 err=8

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

[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Guardium Database Activity Monitor","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"10.0;10.1;9.0;9.1;9.5","Edition":"","Line of Business":{"code":"LOB76","label":"Data Platform"}}]

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.

Document Information

Modified date:
16 June 2018

UID

swg21994576

Page Feedback