Troubleshooting
Problem
Teradata EXIT sometimes stops logging traffic to Guardium after setting parameter exit_lib_shmem_size=52428800
This was noted in the following environment
Teradata STAP EXIT
STAP version v11 r106701
Teradata 16.2
Linux SDIFX-1-2 3.0.101-0.187.TDC.1.R.0-default #1
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 3
The problem has been noted under the following scenario
- Amending the exit_lib_shmem_size as follows
exit_lib_shmem_size 52428800
exit_lib_shmem_size 52428800
- Restart the STAP - no traffic is logged
It may appear to some customers that the only way to log the traffic is to uninstall and then re-install the Guardium STAP.
Cause
This is due to shared memory segments not being shut down correctly
This is due to shared memory segments not being shut down correctly
The Exit library is linked directly with Teradata - the amended shared memory parameters are not activated correctly until the current running Teradata Exit process is released. Once Teradata is restarted the Teradata Exit library is then correctly loaded with the updated shared memory parameters and traffic is then monitored and sent to the Guardium Collector(s) as expected
If the exit_lib_shmem_size value is changed the process that attaches to the shared memory segments must then be restarted. -ie the Teradata must be restarted to pick up the new shared memory parameters
The EXIT library (which makes use of Guardium APIs) and main control of the shared memory segments is written by Teradata.
Remediation
The Teradata database will need to be restarted to release the shared memory segments and pick up the new correctly
If the above remediation is followed after amending the exit_lib_shmem_size and traffic does not appear to get monitored (having previously been monitored successfully prior to the amended exit_lib_shmem_size ) then customers should engage Teradata support who can make the necessary investigation in the first instance
(Teradata may need to collaborate with the Guardium if they believe any Guardium APIs needs investigating)
(Teradata may need to collaborate with the Guardium if they believe any Guardium APIs needs investigating)
Related Information
Document Location
Worldwide
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCJM6A","label":"IBM Security Guardium S-TAP for IMS on z\/OS"},"Component":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Was this topic helpful?
Document Information
Modified date:
19 February 2020
UID
ibm12801199