Linux-UNIX: Troubleshooting A-TAP configuration issues

This section summarizes common mistakes made during A-TAP configurations, their symptoms, and how to avoid them.

Table 1. A-TAP configuration issues and recommendations
Symptoms Mistake Platform How to Avoid
Activation command fails. Wrong db_home parameter All Verify that the value of db_home is correct.
Activation command fails. OS user logged in All Always make sure the OS user is not logged in. Use w command to see which users are logged in.
12.1 Activation fails for Oracle Database 23ai. Activating A-TAP with wrong parameters for Oracle Database 23ai.   Before you activate A-TAP, set the following parameters:
  • db_version = 23
  • db_use_instrumented = no
Database does not start. Wrong instance name All Verify the db_instance name is specific correctly.
Traffic is not logged. Wrong or missing db_version AIX Always specify numeric version (for example, 10.2 or 9.2 ). The version number can have only one digit after the decimal point.For Db2: Verify that the IE configuration is correct. Run the script find_db2_shmem_parameters.sh, located under stap_directory/bin. Execute it either as root or Db2 user, using the db2 instance name as a parameter. It returns the shared memory parameters, including Db2 shared memory size, Client position and header size. Verify that the IE parameters defined in Guardium match these returned values.
Fails to activate. Missing Oracle-guard-instrumented AIX Instrument command must be run first to create a re-linked instrumented Oracle executable
Error during A-TAP activation. Insufficient disk space, install exits   Clean up disk space and retry. If that does not help, change db_space=8 to db_space=1.