This topic applies for Oracle, Informix and DB2 database servers only. For these database types, when S-TAP starts it must have access to the database home. If your environment uses a clustering scheme in which multiple nodes share a single disk that is mounted on the active node, but not on the passive node, the database home is not available on the passive node until failover occurs.
S-TAP can be configured for delayed loading by setting a configuration file property, wait_for_db_exec. When starting, if S-TAP finds that there is no access to the database home, it checks the wait_for_db_exec value (see below), and takes the appropriate action.
-1 (the default): S-TAP will not start.
Any positive value: S-TAP will sleep for the specified number of seconds, and then try to access the database home again.
Before setting this property to a positive value, be sure to set all other necessary configuration properties and test that the S-TAP starts and collects data correctly.
Note: This property is new with S-TAP version 6.1. It can only be set by editing the configuration file, and not from the Guardium administrator console. For more information about editing the configuration file, see Configuration overview.