Linux-UNIX: Preparing to install K-TAP

Edit online

The Software TAP (S-TAP®) installation process checks the database kernel to determine whether a Kernel TAP (K-TAP) is created to work with that kernel. If not, the K-TAP Loader can create the K-TAP by compiling it, or by using the FlexLoad mechanism. For Linux databases, if a matching K-TAP exists, you can check in advance by using the Finding the correct K-TAP version for your Linux kernel database.

This flow is relevant for S-TAP installation with both Guardium® Installation Manager (GIM) and non-GIM methods.

FlexLoad mechanism guidelines:
  • SUSE requires that the primary kernel version (for example, 4.12.14 of the version 4.12.14-23.1) matches and the vendor-specific version falls within range of a release. For example, the digits that follow 4.12.14 must be higher than the existing module in the list.
  • All others require that the primary kernel version (X.Y.Z) matches in addition to the major vendor-specific version number (A in X.Y.Z-A.B.C). The digits that follow X.Y.Z in the OS kernel version must be higher than the module to be flex loaded. For example, kernel 3.10.0-514.6.1.el7.ppc64le accepts a flex match for a module that is built for 3.10.0-514.2.2.el7.ppc64le.
  • In all cases, the kernel module that represents the most recent kernel with matching rules and is also older than the kernel version installed, is chosen. Module families also need to match. For example, el5, el6, el7, pae, x86_64, and so on.
  1. For Linux databases only: Check whether your database operating system-kernel version has a K-TAP module match.
    1. On your database, as user root, run the command uname -r to output only the kernel version. The kernel version is similar to 2.6.18-164.10.1.el5.
    2. Open the Finding the correct K-TAP version for your Linux kernel database.
    3. Paste in your kernel version, select your Guardium version and operating system, and click Search. The database filters to show the relevant K-TAP version.
      Tip: The Match column displays one of the following filters:
      Exact
      You can proceed with the S-TAP installation.
      Flex
      Enable the FlexLoad mechanism when you install S-TAP (step 4) or have the S-TAP compile the K-TAP during installation (step 3).

      If there is no match at all, you can either compile the K-TAP by using S-TAP, or you can order a custom build (step 6).

  2. For non-Linux databases: Look at the list of supported kernels in the fix pack of the target S-TAP install version, for example Guardium_10.6_KTAP_List.zip, from Fix Central.
    • If there is a match, you can proceed with the S-TAP installation.
    • If there is no match, you can either compile the K-TAP during S-TAP installation (step 3), you can try FlexLoad (step 4), or you can order a custom K-TAP (Linux-UNIX: Requesting a K-TAP module).
  3. If K-TAP Loader did not find an exact match or a close match, the FlexLoad mechanism is OFF, and the required packages are installed on the database system (see Linux-UNIX: S-TAP compilation of K-TAP), it attempts to build one to match your Linux kernel. All that you need to build the K-TAP is the S-TAP installer.
  4. If K-TAP Loader cannot find the correct kernel module and if FlexLoad mechanism is ON, K-TAP Loader finds the closest matching kernel module and loads it. The following parameters control the FlexLoad mechanism:
    • GIM installation: KTAP_ALLOW_MODULE_COMBOS
    • Shell installation: --ktap_allow_module_combos
    • RPM: --set-flexload
  5. If you ordered a custom K-TAP build, after two weeks you have a custom modules-xxx.tgz file. You specify that file during the shell installation with the --modules flag, or with the GIM_ALLOW_CUSTOMED_BUNDLES flag when you install with GIM.
  6. If K-TAP cannot load the kernel module by any of these three modes, it informs you with a "Failed to load" message. It either installs the S-TAP without the K-TAP (and with the PCAP packet-capturing mechanism instead), or fails the S-TAP installation. If you reach this point, you need to order a custom K-TAP build.
  7. If you have several systems that are running the same Linux distribution, you can build a K-TAP on one system and copy it to the others. For example, you might build a K-TAP on a test system and then copy it to one or more production database servers after testing. If you use GIM to install the S-TAP, GIM can automatically copy the bundle that contains the new K-TAP to a Guardium system. You can then distribute this bundle from the Guardium system to other database servers.