Database activity monitoring (DAM) : Configuring target database monitoring : Configuring Oracle monitoring
Configuring Oracle monitoring
FortiDB can use several methods to collect audit information from Oracle databases.
The TCP/IP sniffer method is provided by the appliance version of FortiDB only. For detailed configuration instructions, see “Configuring monitoring using the TCP/IP sniffer (all database types)”.
To configure auditing for an Oracle database
To change the collection method or polling frequency for monitoring, first stop monitoring. You cannot change these settings while FortiDB is monitoring the target database.
1. Ensure the required database pre-configuration is complete.See “Oracle target database pre-configuration”.
2. In the navigation menu, click DB Activity Monitoring > Monitoring Management, and then click the name of the target that connects to the database you want to monitor.
3. Obtain the value of your database’s audit_trail parameter.
4. On the General tab, for Collection Method, select one of the following options:
Oracle audit_trail parameter value
Collection method
Agent required?
db, extended
For Oracle 9i only. Monitoring Oracle 9i databases has the following limitations:
Table and table column policy - Cannot retrieve the SQL statement text
Table, user, and session policy - No effect with Suspicious Location rule
Session policy - No effect with Extremely Long Session rule and High Read Ratio rule
xml, extended
XML File Agent
FortiDB's XML file agent provides high performance for auditing Oracle target databases. To use the XML file agent option, run the FortiDB XML file agent in your target database. For more information, see “Oracle XML file agent installation and configuration (UNIX, Windows)”.
5. If you selected DB, EXTENDED, for Polling Frequency(secs), enter the polling frequency for audit collection, in seconds.
6. Click Test to confirm the connection with the method you selected.
7. Under Monitoring, click Start Monitoring.
For more information about monitoring, see “Monitoring settings and messages”.
See also
Target monitoring configuration tabs and options
Oracle target database pre-configuration