Linux and UNIX systems: Copying a new K-TAP module to other systems

When you build a new K-TAP module for a Linux database server, you can copy that module to other database servers that run the same Linux distribution.

Before you begin

Use this procedure after you have built and tested a K-TAP module on a Linux database server.

About this task

If you use the Guardium Installation Manager (GIM) to manage agents on your database servers, use GIM to copy the module. See the link below for the procedure to use.


  1. Log in to the database server with the tested K-TAP.
  2. Change directory to /usr/local/guardium/guard_stap/ktap/current/ and run ./guard_ktap_append_modules to add the locally built modules to modules.tgz.
  3. Copy the updated modules.tgz file to the target server.
  4. Log in to the target server and change directory to /usr/local/guardium/guard_stap/ktap/current/.
  5. Run the K-TAP loader with the retry parameter and the full path to the updated modules.tgz file. For example:
    guard_ktap_loader retry /tmp/modules-9.0.0_r55927_v90_1.tgz
  6. Restart the S-TAP to connect it to the new K-TAP module.


The custom K-TAP module is ready to use on the target system. Repeat this procedure for each matching Linux system to which you want to deploy the K-TAP module.