Linux-UNIX: Oracle-specific guardctl parameters

Use these guardctl parameters when configuring A-TAP for an Oracle database.

Example: 
/usr/local/guardium/guard_stap/guardctl --db-user=oracle11 --db-type=oracle --db-instance=on12rh60 --db-home=/home/oracle11/product/11.1.0/db_1 --db-base=/home/oracle11 --db-version=11.2 store-conf
Note: Hyphen and underscore are interchangeable in the guardctl parameters.

Oracle required parameters

Required Parameter Value How to determine
db_user Oracle user name Use the database instance user name.
db_instance Oracle instance name Use the value from $ORACLE_SID
db_type Oracle
db_home DB HOME. for example $ORACLE_HOME DB admin has these details.
db_base Database instance user home directory (Database owner home directory) DB owner $HOME (~DB_USER), and must match db_install_dir in the corresponding Inspection Engine. See db_install_dir.
db_version The database version Run SQL > SELECT * FROM V$VERSION

Oracle optional parameters

Optional Parameter Value How to determine When is it required
db_relink No/yes A-TAP activation method
db_use_instrumented No/yes A-TAP activation uses a relinked version of Oracle previously created with the guardctl instrument command.

Instrumentation is required for:

  • Oracle 12 and later SSL for all non-Windows platforms
  • Oracle SSL on AIX
  • Oracle ASO prior to Oracle 11.2 on AIX

Instrumentation is automatic when Oracle is linked from the activate command or through the Guardium UI.

db_bits 32 or 64 DB instance architecture (32 for 32-bit, 64 for 64-bit) Required only if A-TAP is not able to recognize the architecture.