Oracle Standalone Database

After you have installed the PATROL for Oracle Enterprise Database KM, you must configure a monitoring policy.

You can use the information in this topic to configure an Oracle Enterprise Database monitoring policy with the TrueSight console.

This topic includes the following information:

Before you begin

You must download and install the PATROL for Oracle Enterprise Database KM.

To configure the monitor type

Click to view a short video on how to configure an Oracle Data Guard environment using TrueSight console.

 https://youtu.be/35JKTSm6PAk

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

ParameterSelection
Monitoring SolutionOracle Enterprise Database
Monitoring ProfileOracle Environment Monitoring
Monitor TypeOracle Standalone 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.

FieldDescription
Environment name

Enter a unique environment name for monitoring the Oracle Database. A container will be created with this environment name that will hold all the Database instances.

Note

  • The name cannot include blank spaces or any of the following special characters: # $ \ ' | ~ ! @ % ^ ; ` ( ) { } ? \ " [ ] + = & : > < * /
  • Do not use non-English characters to specify an environment name.
  • Once 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 you can change the environment name.

The remaining environment details are in the following sections:

Standalone instance connection details

FieldDescription
Oracle host

The host name or the IP address used for the standalone Oracle Database.

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 .

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 port

The port number used to connect with the standalone Oracle Database.

The default port number is 1521.

Oracle connection type

Specify the Oracle connection type:

  • Service
  • SID
Oracle connection methodEnter the name of the Oracle Database service or SID to monitor. The service or SID name appears in the tnsnames.ora file. Use the command lsnrctl services to find the name.
Connect as SYSDBA

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

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

User name

The monitoring user name of the Oracle Database.

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

Password
Confirm password

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

Enter a SQL query name.

Note

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.

Note

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 Database activity categories that you want to monitor.

Monitoring CategoriesDescription
Operating System usage

Monitors the operating system utilization statistics and system resources.

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

Sessions

Monitors the sessions activity of the Oracle Database.

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

UNDO Usage

Monitors the UNDO space usage in the system.

If the Oracle Database is set for automatic UNDO_MANAGEMENT, this monitoring category is not created for this monitoring policy.

For more information, see the UNDO Usage (KOE_INST_UNDO) monitoring category.

Services

Monitors the Oracle services executed inside the Database.

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

Pluggable Database

Monitors the pluggable Databases that are supported by the Oracle Database 12c.

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

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

Users

Monitors the Oracle Database users activity.

For more information, see the Users (KOE_INST_USERS) monitoring category.

System

Monitors the system performance of the Oracle Database.

For more information, see the System (KOE_INST_SYSTEM) monitoring category.

Listeners

Monitors the listener port of the Oracle Database.

For more information, see the Listeners (KOE_INST_LISTENER) monitoring category.

Wait Events

Monitors the wait events in the Oracle Database.

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

ASM

Monitors the performance of the Oracle Database ASM disks.

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

Tablespaces 

FieldDescription
Tablespaces

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 is DB12, 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


Note

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


Jobs 

FieldDescription
JobsSelect this option to monitor the jobs and transactions running in the Oracle Database.
Long running job time (minutes)

The duration for jobs that are running longer than the defined duration (default 30 minutes). Any job that exceeds this duration sets an alert.

Job overdue time (minutes)

The duration for jobs that are overdue because they are not executed (2 minutes late). These jobs may be delayed, broken, or failed.

For more information, see Jobs (KOE_INST_JOBS).

Environment Settings details

FieldDescription
Logging 

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

The log files are created under 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 Database instances are discovered under the Oracle host device.

If it is disabled, all the Oracle 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.

JVM Arguments
The optional Java Virtual Machine (JVM) arguments for the Java collector
User nameThe local user name to start the Java process.

Password

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 have completed configuring the environment, click OK to add this to the environment configurations list. This environment is displayed on the Environment Configuration list. 

Click Cancel to exit without saving any changes. 

If you want to verify the configuration on your TrueSight console, click here.


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

Comments