IBM Support

IBM Security Guardium - DB2 Fixpack Update Without First Stopping ATAP And Now Unable To Capture Traffic From DB2 On Linux

Troubleshooting


Problem

IBM Security Guardium - When updating DB2 fixpack, it is required to stop ATAP before proceeding. Updating DB2 fixpack without first stopping ATAP will result in traffic collection issues.

Symptom

No traffic is being captured

Cause

Updating DB2 fixpack without first stopping ATAP corrupts DB2

Diagnosing The Problem

Confirm with DBA that db2 fixpack was updated without first stopping ATAP.

Resolving The Problem

1. Make sure you have a backup of your DB2.

2. Stop DB2 database.

3. Deactivate A-TAP:
/opt/guardium/guard_stap/guard_stap/guardctl db_instance=udbxinsd
db-home=<$DB2_HOME> deactivate

4. Verify that A-TAP being deactivated:
/opt/guardium/guard_stap/guard_stap/guardctl db_instance list-active

5. Run the following command
Example: /opt/ibm/db2/V10.5/instance/db2iupdt <instance name>

6. Activate ATAP:
/opt/guardium/guard_stap/guard_stap/guardctl db_instance=udbxinsd
db-home=<$DB2_HOME> activate

7. Verify that A-TAP being activated:
/opt/guardium/guard_stap/guard_stap/guardctl db_instance list-active

8. Start DB2 database.

[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Guardium S-TAP","Platform":[{"code":"PF016","label":"Linux"}],"Version":"10.0;10.0.1;10.1;10.1.2;9.0;9.1;9.5","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
16 June 2018

UID

swg21997621

Page Feedback