Close

Search Results

Oracle Event Monitor Reference Guide

Oracle Event Monitor

Checks Oracle databases to ensure availability.

Overview

This event monitor checks your Oracle database servers. It can make sure the database server is available and can run SQL queries checking the results for specified values.

Before you get started, install the Instant Client Package on your FrameFlow system. Install the Basic client component and the ODBC client component. These components are required to allow the event monitor to connect to your Oracle databases. Use the Oracle client to define a TNS name that connects to the database you want to monitor. After configuring the TNS name, it's a good idea to test it using the tnsping utility that comes with the Oracle client.

Use Cases

  • Checking SQL statement results for specified values
  • Measuring the time taken to execute SQL queries

Monitoring Options

This event monitor provides the following options:

Alert With [Info/Warning/Error/Critical] if the database cannot be contacted

Use this option to get alerts if FrameFlow could not contact the selected database.

TNS Service Name

Enter the TNS name that you defined for your database. The event monitor will use this value to connect to your database.

As of FrameFlow version 2023.1, we've added the ability to monitor multiple databases on the same server with your Oracle Event Monitor. First, add the databases as their own network devices using the format "server@database", then add each database you want to monitor in the "network devices" field of your Oracle monitor. Then, just add the network devices you want to monitor and use the token %%devicename%% in the "TNS Service Name" field. When the event monitor runs, it will swap out the token with the name of each database.

Run a SQL statement

Enable this option if you want to run a SQL statement or stored procedure on the database. The event monitor includes various options to check the results.

SQL statement to run

Enter the SQL statements that will run on the database. It's usually a good idea to verify the SQL code in Oracle itself before pasting it into the Oracle Event Monitor.

Tip: As of version 2023.1, you can run multiple commands in the "SQL Statement to Run" box. Separate each new command with a semicolon.

Show the first [#] result rows in all notifications

With this option enabled, the events and alerts generated by the event monitor will include rows returned by the SQL statement.

Alert with Warning/Error/Critical if a specified text value is found in the results

Enable this option to tell the event monitor to check the rows returned by the SQL statement. Further options allow you to specify what to search for. Enter an asterisk in the "Rows" field to select all rows.

Search for the following text

Enter the text that the event monitor should look for.

Number of rows to check

Tells the event monitor how many result rows it should check for the specified text.

Column number to check

Tells the event monitor in which column it should look for the specified text.

Authentication and Security

Select an authentication profile with credentials that have access to the database being monitored.

Protocols

OLEDB

Data Points

The data points generated by this event monitor depend on the values you choose to monitor.

Sample Output

Tutorial

To view the tutorial for this event monitor, click here.

Back to Library

Comments

There are no user-contributed comments for this page. Be the first to submit a comment!

Add a comment

Home