BMC PATROL for Oracle Enterprise 1.0.00 Beta

Beta content The beta version of the KM includes Oracle standalone local and remote instance monitoring.

Downloading the Beta image from FTP

Go to the following location to download the beta image ftp://ftp.bmc.com/pub/PATROL_for_Oracle_Enterprise/1.0.00/BETA_180417-085803/
Select and download “koe_LINUX-WINDOWS_1000.zip” on your machine.

Importing the image in TrueSight

Login to TrueSight console and go to Administration→Repository.
Go to Installation Components and select Import.
Select Single Solution and Browse option.
Select the beta image which we downloaded from ftp location and click Import.

Configuring Oracle Enterprise monitoring in TrueSight

Prerequisites

Before configuring the KM, ensure that the following prerequisites are met:

Oracle Enterprise KM Beta image has been installed on PATROL Agent server.
It is required to create a user with minimum privileges before configuring the KM.

This table lists the supported resources for the BMC PATROL for Oracle Enterprise product.

Resource	Resource
PATROL products	PATROL Agent 10.7.00.04 and 11.0.00.02 PATROL Installation Utility 10.7.00, 11.0.00, and 11.3.00
Oracle database version	11gR2 12cR1 12cR2
TrueSight Operations Management	11.0.00 10.7.00
Operating system	Microsoft Windows Microsoft Windows Server 2012, 64-bit Microsoft Windows Server 2012, R2 64-bit Microsoft Windows Server 2016, 64-bit Linux Red Hat Enterprise Linux AS/ES version 6.x thru 7.4 for x86 (64-bit)
Java Runtime Environment (JRE)	1.8

PATROL for Oracle Enterprise monitoring categories and permissions

PATROL for Oracle Enterprise provides the following monitoring categories and permissions for an Oracle standalone database instance.For initial connection and availability monitoring, you must use the GRANT CREATE SESSION TO <username> permission. This permission allows the user to gain access to the Oracle environment to monitor the database. Depending on the monitoring category, you must grant specific permissions so that each user can access the Oracle objects that are required for each of the monitoring categories. The following table lists the monitoring category and the required Oracle objects used to perform the monitoring functions.

Monitoring category	Monitor types	Grant types	Variables and authorizations
Availability and Connection	Instance (KOE_INSTANCE)	GRANT CREATEGRANT SELECT	SESSION TO ON V$PARAMETER TO
Operating System usage	Operating System Usage (KOE_INST_OS)	GRANT SELECT	V$RESOURCE_LIMITV$OSSTAT
Tablespaces	Tablespaces (KOE_INST_TABLESPACE)	GRANT SELECT	DBA_TABLESPACE_USAGE_METRICSDBA_TABLESPACES
Sessions	Sessions (KOE_INST_SESSIONS)	GRANT SELECT	V$SESSION
UNDO usage	UNDO Usage (KOE_INST_UNDO)	GRANT SELECT	V$PARAMETERV$UNDOSTAT
Services	Services (KOE_INST_SERVICE)	GRANT SELECT	V$SERVICEMETRIC
Pluggable database	Pluggable Database (KOE_INST_PLUGGABLE_INSTANCE)Pluggable Tablespace (KOE_INST_PLUGGABLE_TBS)	GRANT SELECT	DBA_PDBSV$PDBSV$DATABASEV$SESSIONCDB_TABLESPACESCDB_TABLESPACE_USAGE_METRICS
Pluggable database		ALTER USER	SET CONTAINER_DATA=ALL CONTAINER=CURRENT
Users	Users (KOE_INST_USERS)	GRANT SELECT	V$METRIC
Systems	System (KOE_INST_SYSTEM)	GRANT SELECT	V$METRIC
Jobs	Jobs (KOE_INST_JOBS)	GRANT SELECT	DBA_SCHEDULER_JOB_RUN_DETAILSDBA_SCHEDULER_RUNNING_JOBSDBA_SCHEDULER_JOBS

Here is an example of Session category:
GRANT CREATE SESSION TO <username>;
GRANT SELECT ON V_$SESSION TO <username>;

Configuring Oracle standalone database monitoring in TrueSight

After you have installed the PATROL for Oracle Enterprise KM, you must configure a monitoring policy. You can use the information in this topic to configure an Oracle Enterprise monitoring policy with the TrueSight console.

This topic includes the following information:

To configure the monitor type

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

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 environments are configured successfully.

To add an environment configuration

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

Field	Description
Environment name	Enter a unique environment name for monitoring the Oracle database. A container gets created with this environment name that holds all the TrueSight instances.Note: The name cannot include blank spaces or any of the following special characters: # $ \ ' \| ~ ! @ % ^ ; ` ( ) { } ? \ " [ ] + = & : > < * / After you save this 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 change the environment name.

Field

Description

Environment name

Enter a unique environment name for monitoring the Oracle database. A container gets created with this environment name that holds all the TrueSight instances.Note: The name cannot include blank spaces or any of the following special characters: # $ \ ' | ~ ! @ % ^ ; ` ( ) { } ? \ " [ ] + = & : > < * / After you save this 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 change the environment name.

The remaining environment details are in the following sections:

Standalone instance connection details

Field	Description
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.
Oracle port	The port number used to connect to the standalone Oracle database.The default port number is 1521.
Oracle service name	The name for the Oracle database service to monitor.The service name is the TNS alias that is used to remotely connect to the database. This service name is in the Tnsnames.ora file on your clients.Note: You may need to contact the database administrator for the exact Oracle database service name.
User name	The monitoring user name for the Oracle databaseNote: Confirm that the user has permission for object access, see Monitoring-categories-and-user-permissions.
Password Confirm password	The user password for the Oracle database

Monitoring Categories details

Select the Oracle database activity categories that you want to monitor.

Monitoring Categories	Description
Operating System usage	Monitors the operating system utilization statistics and system resources.
Tablespaces	Monitors the Oracle instances tablespace usage.
Sessions	Monitors the session's activity of the Oracle instance.
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.
Services	Monitors the Oracle services executed inside the database.
Pluggable Database	Monitors the performance and availability of pluggable databases that are supported by Oracle Database 12c.If the Oracle database is not a pluggable type, this monitoring category is not created for this monitoring policy.
Users	Monitors the Oracle users activities.
System	Monitors performance and availability of the Oracle's instance system performance.
Jobs	Monitors the jobs and transactions running in the Oracle instance.This monitoring category includes the following settings: Long running job time in minutes The duration for jobs that are running longer than the defined duration (default 30 minutes). Any job that exceeds this duration sets and alert. Job overdue time in minutes The duration of jobs that are overdue because they are not executed (2 minutes late). These jobs may be delayed, broken, or failed.

Environment Settings details

Field	Description
Logging	Select this option to enable debugging operations for all Oracle instances configured in this environment.The log files are created under PATROL_HOME directory: Java: ~/koe/logs/java PSL: ~/log/koe-*.kmlog
Device mapping	By default, device mapping on the TrueSight user console is enabled (check box selected), and the PATROL instance appears as a device in the following TrueSight components: Presentation Server Infrastructure Management Integration Service Enabling device mapping consolidates TrueSight monitoring at the device level.Clear this check box to disable the device creation on the Presentation Server.
Java collector settings
Java home	The path to the JRE directory (aka $JAVA_HOME environment variable) on the PATROL Agent host. The Java version must be version 8 or later.If you use the $JAVA_HOME variable, the Java location depends on the following: No username and password are entered for the Java collector settings; the KM uses the Java location of the user running the PATROL agent. A username 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 name	The local username to start the Java process.
Password	The user password to start the Java process.
Confirm Password	Re-enter the password.
Collection Interval
Availability Collection Interval (min)	The time interval used to check for the environment's availability for collecting data.The default interval is one minute.
Data Collection Interval (min)	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 (min)	The time interval used 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.The following screenshots show the output and hierarchy of a configured Oracle instance:

The devices hierarchy structure of a monitored system.
Global configuration status (Root container monitor type) with annotation. In the screenshot below, the parameter value is 0 (OK status), and the annotation shows that the environment added successfully.
Environment configuration status (Root container of standalone instances) with annotation. In the screenshot below, the parameter value is 0 (OK status), and the annotation shows that the backend collector is started.

Oracle device hierarchy.
Oracle device instance status. In the screenshot below, the instance status 0 (OK) indicates that the instance is active.
If the status is Not OK, the annotation shows the root cause of the error and also possible corrective actions.