Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Log & Event Manager (LEM) > Integrate the Oracle Database with SolarWinds LEM

Integrate the Oracle Database with SolarWinds LEM

Table of contents

Overview

This article contains the procedures for integrating your Oracle database with your SolarWinds LEM implementation. 

Environment

All LEM versions

Steps

Notes:​

  • Install a LEM Agent on your database server.
  • We support the following versions of Oracle on the following operating systems:

 

 

  Oracle 9 Oracle 10 Oracle 11
Windows X X X
Linux   X X

 

Best Practices for Oracle Auditing

Configure auditing on your Oracle database to suit the needs of your environment. At minimum, we recommend you audit access rights to the database, such as login, logout, and change events. For more detailed auditing, we recommend you use our Recommended Oracle Audit script to enable auditing for sessions and most schema changes in addition to the basic auditing noted above.

 

To enable the minimum recommended auditing:

  1. Open SQL*Plus and connect to your database.
  2. Run the following command:

AUDIT SESSION, ROLE, USER BY ACCESS;

 

To enable enhanced auditing using the Recommended Oracle Audit script:

  1. Download the attached script and save it to a known location.
  2. Open SQL*Plus and connect to your database as SYSDBA.
  3. Run the following command at the SQL> prompt.
    @PATH\Recommended_Oracle_Audit.sql|
    where PATH is the file path for the script.
  4. Restart your database in Enterprise Manager.

 

Configure Oracle on Windows to integrate with a LEM Agent

Use the following procedure to configure your Oracle database for integration with a LEM Agent.

Note: If you are configuring Oracle on a Linux server, configure it to report its logs using syslog messages after completing the following procedure. For more information, see the procedure on Configuring Oracle on Linux to Syslog to a LEM Agent.

  1. Open SQL*Plus and connect to your database.
  2. Run the following command to determine whether auditing is already turned on:
    SELECT NAME,VALUE FROM v$parameter WHERE NAME LIKE 'audit%';

    If auditing is turned on, this command should return the following results.

    audit_trail OS
    audit_sys_operations TRUE

  3. If the command returns unexpected results, run the following commands:
    ALTER SYSTEM SET audit_sys_operations = TRUE SCOPE=SPFILE;
    ALTER SYSTEM SET audit_trail = "OS" SCOPE=SPFILE;

    Note: Alter these commands if you did not start your database with the default spfile configuration.
  4. Restart the database services.
    Note: If you are running Oracle 9, be sure to restart your database using the spfile option, as this is not the default configuration when using SQL*Plus. If you are using Enterprise Manager instead, this should not be a concern.
  5. Repeat Step 2 in this procedure to verify your changes were applied correctly.

 

Configuring Oracle on Linux to Syslog to a LEM Agent

Use the following procedure to configure Oracle to send Syslog messages to a local facility on your LEM Agent for Linux implementations.

 

  1. Open SQL*Plus and connect to your database.
  2. Run the following command to determine whether auditing is already turned on:
    SELECT NAME,VALUE FROM v$parameter WHERE NAME LIKE 'audit%';

    If auditing is turned on, this command should return the following results:

    audit_trail OS
    audit_sys_operations TRUE
    audit_syslog_level local6.debug

  3. If the command returns unexpected results, run the following commands:
    ALTER SYSTEM SET audit_sys_operations = TRUE SCOPE=SPFILE;
    ALTER SYSTEM SET audit_syslog_level = "local6.debug" SCOPE=SPFILE;
    ALTER SYSTEM SET audit_trail = "OS" SCOPE=SPFILE;

    Note: Alter these commands if you did not start your database with the default spfile configuration.
  4. Restart the database services.
  5. Repeat Step 2 of the Configure Oracle to Integrate with a LEM Agent procedure to verify your changes were applied correctly.
  6. Open /etc/syslog.conf for editing and add the following entry:
    # Oracle Audit Trail local6.log
    local6.* /var/log/local6.log
  7. If local6.log does not exist, create an empty file at /var/log/local6.log before you proceed.
  8. Run the following commands to restart the syslog service:
    sh /etc/init.d/syslog stop
    sh /etc/init.d/syslog start

 

Configure the Oracle Auditor Connector on Your LEM Agent

Use the following procedure to configure the Oracle Auditor connector on the LEM Agent installed on your database server. For Windows implementations, use the Oracle Auditor - Windows connector. For Linux implementations, use the Oracle Auditor - Syslog connector.

  1. Open your LEM Console and log in as an administrator.
  2. Click the Manage tab, and then click Nodes.
  3. Locate the LEM Agent on your database server, click the gear icon next to it (left), and then click Connectors.
  4. In the Connector Configuration window, enter Oracle Auditor in the search box at the top of the Refine Results pane.
  5. Click the gear icon next to the Oracle Auditor connector for your host operating system, and then click New.
  6. Enter a custom Alias or accept the default.
  7. If you are configuring the Oracle Auditor - Syslog connector, verify that the Log File path matches the path you supplied in your initial configuration.
  8. If you are finished configuring the connector, click Save.
  9. Click the gear icon next to the new connector, denoted by an icon in the Status column, and then click Start.
  10. Click Close to close the Connector Configuration window.
Last modified
12:41, 8 Feb 2017

Tags

Classifications

Public