IBM Support

Error opening shared memory area when configuring Guardium COMM_EXIT_LIST for DB2

Troubleshooting


Problem

I have configured DB2 COMM_EXIT_LIST to use IBM InfoSphere Guardium libguard. After restarting the DB2 server, I get the following error in the DB2 diag log: 2013-06-28-11.41.12.306169-300 E870950E486 LEVEL: Severe PID : 15764 TID : 139905833363200 PROC : db2sysc 0 INSTANCE: db2001 NODE : 000 APPHDL : 0-16 HOSTNAME: dbhost1 EDUID : 54 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=2 err=8

Resolving The Problem

The message "Shmem_access /.guard_writer0 failed Error opening shared
memory area errno=2 err=8" indicates that the Guardium library was unable to create the shared memory device that it requires. The db2 instance owner must be added as an authorized user using the guardctl command.

  1. Stop the DB2 instance

  2. Authorize the DB2 instance owner using the command below

  3. Start the DB2 instance

Authorizing the DB2 instance owner

If GIM is not installed:

<guardium_installdir>/bin/guardctl authorize-user <db2 instance owner>

if GIM is installed

<guardium_installdir>/modules/ATAP/current/files/bin/guardctl authorize-user <db2 instance owner>

For example, if DB2 instance owner is db2001 and GIM is installed in /usr/local/guardium, the command is:


/usr/local/gim/modules/ATAP/current/files/bin/guardctl authorize-user db2001

[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF016","label":"Linux"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
16 June 2018

UID

swg21642950

Page Feedback