Oracle Real Application Cluster or Real Application Cluster One Node Database

This topic provides you instructions to configure both RAC and RAC One Node databases by using the Oracle RAC Database monitor type.

To configure the monitor type

In the Add Monitoring Configuration panel, select the following parameters for the Oracle Enterprise Database KM:

Monitoring SolutionOracle Enterprise Database
Monitoring ProfileOracle Environment Monitoring
Monitor TypeOracle RAC Database

For the Global Monitoring Setting, you can enable Logging for all of the configured PATROL Agent environments to confirm that all of the PATROL for Oracle Enterprise Database environments are correctly configured.

To add an environment configuration

Click Add and enter the details in the Environment Configurations pane.

Environment name

Enter a unique environment name for monitoring the Oracle Database. A container is created with this environment name that holds all the RAC instances.


  • The name cannot include blank spaces or any of the following special characters: # $ \ ' | ~ ! @ % ^ ; ` ( ) { } ? \ " [ ] + = & : > < * /
  • Do not use non-English characters to specify an environment name.
  • When you save the environment configuration, you cannot change the name without losing the historical data of the environment. You can change the environment name by making a copy of the monitoring solution.

The remaining environment details are in the following sections:

RAC instance connection details

In the RAC instance connection details section, click Add. The RAC instance connection details pane is displayed.

Oracle SCAN

Enter the host name or the IP address used for the Oracle RAC.

You can use the $HOSTNAME variable for the Oracle host. The name is taken from the PATROL agent that is registered in the  TrueSight console's Devices page Open link .

The IP address can be in the IPv4 or IPv6 format. An example of an IPv6 address is [2001:db8:28:3:f98a:5b31:67b7:67ef]

Oracle SCAN listener port

Enter the port number that is used to connect with the Oracle RAC Database.

The default port number is 1521.

Oracle RAC service name

Enter the RAC service that you want to monitor. To get a list of RAC services, use the srvctl command.

Connect as SYSDBA

Select this option to connect to the Oracle RAC instance as SYSDBA privileged user.

Note: BMC does not recommend to monitor using a user with SYSDBA privileges.

Oracle credentials
User name

The monitoring user name of the Oracle RAC Database.

Note: Confirm that the user has permission for object access, see Monitoring categories and user permissions.

Confirm password

The monitoring user password of the Oracle RAC Database.
Oracle Custom SQL Queries
Query name

In the Oracle Custom SQL Queries section, click Add. On the Custom SQL Query pane, enter a name for the query.


The name cannot include blank spaces or any of the following special characters: # $ \ ' | ~ ! @ % ^ ; ` ( ) { } ? \ " [ ] + = & : > < * /
After you save the environment configuration, you cannot change the name without losing the environment's historical data. You can change the environment name by making a copy of the monitoring solution and then changing the environment name.

SQL query

Enter the SQL query.


The SQL query must not contain the semicolon (;).

Collection time (minutes)Enter the SQL query collection time. The default collection time is 10 minutes.
Enable number of records annotationSelect this option to display the query result as an annotation on number of records metric.

Monitoring Categories details

Select the Oracle RAC Database activity categories and tablespaces that you want to monitor.

The Node availability monitor category is discovered by default.

Monitoring CategoriesDescription

Monitors the performance of the Oracle Database ASM disks.

For more information, see the ASM Disk (KOE_INST_ASM_DISK) monitoring category.

Fast Recovery Area

Monitors the performance of the Oracle Fast Recovery Area disks.

For more information, see the Oracle Fast Recovery Area (KOE_INST_FRA) monitoring category.

Operating System usage

Monitors the operating system utilization statistics and system resources.

For more information, see the .Operating System Usage (KOE_INST_OS) v2.0 monitoring category.

Pluggable Database

Monitors the pluggable databases.

If the Oracle Database is not a pluggable type, this monitoring category is not created for this monitoring policy.

For all RAC instances, information about pluggable tablespaces is shown globally outside the hierarchy of pluggable databases.

For more information, see the .Pluggable Database (KOE_INST_PLUGGABLE_INSTANCE) v2.0 monitoring category.


Monitors the Oracle services executed inside the Database.

For more information, see the Services (KOE_INST_SERVICE) monitoring category.


Monitors the sessions activity of the Oracle Database.

For more information, see the Sessions (KOE_INST_SESSIONS) monitoring category.

Wait Events

Monitors the wait events in the Oracle RAC Database.

For more information, see the Event Class (KOE_INST_EVENT_CLASS) monitoring category.



Select this option to monitor the tablespaces.

For more information, see Tablespaces (KOE_INST_TABLESPACE).

Tablespaces filtering options
Filtering mode

Select the filtering mode:

  • None
  • Include
  • Exclude
Include/Exclude matching criteria

Based on the selection of the filtering mode, specify the tablespaces to include or exclude from monitoring. Use comma (,) only to separate the tablespaces.

For example, consider the tablespace name as DB12. For this tablespace, you can use any of the following methods to include or exclude tablespaces from monitoring:

  • Starts with: ^DB.*
  • Contains: .*B1.*
  • Ends with: .*12$
  • Equals to: DB12


Be cautious when you add spaces while entering the regex search string. Extra space is considered as a character by the search string.

Environment Settings details


Select this option to enable debugging operations for all Oracle instances configured on this environment.

The log files are created under the PATROL_HOME directory:

  • Java: PATROL_HOME/Patrol3/koekm/logs/java
  • PSL: PATROL_HOME/Patrol3/log/koe-*.kmlog

For more information about logging, see Using debug logging in the TrueSight Infrastructure Management operator console.

Device mapping

By default, device mapping on the TrueSight console is enabled. If enabled, all the Oracle RAC Database instances are discovered under the Oracle host device.

If it is disabled, all the Oracle RAC Database instances are discovered under the PATROL Agent host device.

Java collector settings

Java home

The path to the JRE directory (aka $JAVA_HOME environment variable) on the PATROL Agent host.

If you use the $JAVA_HOME variable, the Java location is depends on the following:

  • No user name and password are entered for the Java collector settings; the KM uses the Java location of the user running the PATROL agent.
  • A user name and password are entered for the Java collector settings; the KM uses Java location of the user entered in the collector settings.

If you enter a path for the JRE directory, you must enter the full path, such as C:\Program files\Java\jre1.8.0_151. Do not use the short path format.

If you do not enter a value in this field, the KM looks for the Java installed in the PATROL Agent home directory as:

  • Linux$PATROL_HOME/../openjdk$PATROL_HOME/../jre64
  • Windows%PATROL_HOME%/../openjdk%PATROL_HOME%/../jre64
JVM Arguments
The optional Java Virtual Machine (JVM) arguments for the Java collector
User nameThe local user name to start the Java process.


Confirm password

The user password to start the Java process.

Collection settings

Availability Collection Interval (minutes)

The time interval used to check for the environment's availability for collecting data.

The default interval is one minute.

Data Collection Interval (minutes)

The time interval used for data collection from the environment.

The default interval is five minutes.

Note: Entering a data collection time that is less than 5 minutes will result in a performance issue for the KM.

Long running data collection queries (minutes)

The time interval use to determine when a running query is blocked. The query is blocked because its execution duration is equal to, or greater than, this interval's threshold.

The default interval is 30 minutes.

After you complete configuring the environment, click OK to add this to the environment configurations list. This environment is displayed on the Environment Configuration list. 

To exit without saving changes, click Cancel

To verify the configuration, click here.

Was this page helpful? Yes No Submitting... Thank you