IBM Support

Guardium fails to collect shared memory traffic from Informix

Troubleshooting


Problem

Infosphere Guardium STAP will not collect shared memory traffic from Informix if the inspection engine is misconfigured. It may still collect TCP traffic.

Symptom

TCP traffic from Informix is collected, but shared memory traffic is not.

Cause

Misconfigured inspection engine.

Resolving The Problem

Check the inspection engine configuration under Admin Console - Local Taps - STAP control. The value in the "Process Name" field should match the result of the following command issued on the DB server:


ls -lrt /INFORMIXTMP/.inf.*

This command will get the correct value on any UNIX platform. Informix must be running for this command to return a value.

For Linix servers, ATAP must be configured to collect any shared memory traffic. The same value should be set to the --db-info parameter in the ATAP confguration before activating ATAP.

(Note: when activating ATAP Informix must not be running.)

See the topic "A-TAP" in the online help for more information about configuring the ATAP. Online help is available here:

http://pic.dhe.ibm.com/infocenter/igsec/v1/index.jsp

Related Information

Guardium Online Help

[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Guardium Database Activity Monitor","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"9.0;8.2","Edition":"All Editions","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
16 June 2018

UID

swg21664479

Page Feedback