Oracle Data Guard Database
Monitor profiles allow you to configure monitoring of similar properties of your environment. For example, by configuring Oracle Data Guard Database, you can enable monitoring of your data guard databases. While configuring you can configure what to monitor and how to access the environment that you want to monitor. You enter all this information in an infrastructure policy.
OR
After installing a KM, you need to provide the following information to it so that it can start monitoring:
- How to access the environment that you want to monitor. You provide credentials to access the environment.
- What to monitor in your environment. In each KM, similar properties or parts of an environment are grouped in monitor profiles and monitor types. For example, you might want to monitor only Data guard databases of your Oracle environment. In this case, you would use the monitor profile as Oracle Data Guard. In some cases, monitor profiles are further categorized in monitor types that represent a small portion of the environment covered in a monitor profile. You configure monitor profiles and monitor types in an infrastructure policy.
This topic includes the following information:
To configure the monitor type
Click to view a short video on how to configure an Oracle Data Guard environment using TrueSight console.
In the Add Monitoring Configuration panel, select the following parameters for the Oracle Enterprise Database KM:
| Parameter | Selection |
|---|---|
| Monitoring Solution | Oracle Enterprise Database |
| Monitoring Profile | Oracle Environment Monitoring |
| Monitor Type | Oracle Data Guard 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 Environment Configuration details.
| Field | Description |
|---|---|
| Environment name | Enter a unique environment name for monitoring the Oracle Database. A container is created with this environment name that will hold all the TrueSight instances. Note
|
The remaining environment details are in the following sections:
Data Guard details
| Field | Description |
|---|---|
| Oracle RAC connection method | The Oracle Database connection method: SID. |
| Oracle connection name | Enter the name of the Oracle Database SID to monitor. The SID name appears in the Note: This value is used for all standalone Data Guard instances only. For each Oracle RAC instance, this value is not used and you must enter the Oracle RAC service name. If you do not have standalone Data Guard instances, but have Oracle RAC instances, you need to enter a value in the field; however, the value is not used for Oracle RAC instances. If you do not have standalone Data Guard instances, but have Oracle RAC instances, this value acts only as a container of RAC instances. |
| Oracle SYSDBA credentials | |
| User name | The SYSDBA monitoring user name of the Oracle Database. Note: Confirm that the user has permission for object access, see Monitoring categories and user permissions. |
Password | The user password of the Oracle Database. |
Data Guard instance connection details
Click Add and enter the Data Guard instance connection details.
| Oracle connection details | |
|---|---|
| Oracle host | The host name or the IP address used for the Data Guard 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 |
| Oracle port | The port number used to connect with the Data Guard Oracle Database. The default port number is 1521. |
| Mark as primary node | Select this option if the Oracle instance is the preferred primary node of the Data Guard setup. |
Data Guard RAC instance connection details
Click Add and enter the RAC instance connection details.
| Field | Description |
|---|---|
| Oracle SCAN | Enter the Oracle RAC instance SCAN or host name. |
| Oracle SCAN listener port | Enter the Oracle RAC SCAN listener port. |
| Oracle RAC connection method | This field displays how you are connecting to the Oracle RAC instance. In this case, you would connect to the Oracle RAC instance as a service. |
| Oracle RAC Service name | Enter the Oracle RAC service name. |
| Mark as primary node | Select the check box to mark the RAC instance as the primary node. |
Monitoring Categories details
Select the Oracle Database activity categories that you want to monitor.
Note
By default, the Standby Health monitor category is selected.
| Monitoring Categories | Description |
|---|---|
| ASM | 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. |
| Listeners | Monitors the listener port of the Oracle Database. For more information, see the Listeners (KOE_INST_LISTENER) 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 more information, see the .Pluggable Database (KOE_INST_PLUGGABLE_INSTANCE) v2.0 monitoring category. |
| Services | Monitors the Oracle services executed inside the Database. For more information, see the Services (KOE_INST_SERVICE) monitoring category. |
| Sessions | Monitors the sessions activity of the Oracle Database. For more information, see the Sessions (KOE_INST_SESSIONS) monitoring category. |
| System | Monitors the system performance of the Oracle Database. For more information, see the .System (KOE_INST_SYSTEM) v2.0 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) v2.0 monitoring category. |
| Users | Monitors the Oracle Database users activity. For more information, see the Users (KOE_INST_USERS) 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. |
Tablespaces
| Field | Description |
|---|---|
| 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:
|
| Include/Exclude matching criteria | Based on the selection in 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:
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 details
| Field | Description |
|---|---|
| Jobs | Select 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). |
Oracle Custom SQL Queries
| Custom SQL Query | |
|---|---|
| Field | Description |
| Query name | Enter a SQL query name. Note The name cannot include blank spaces or any of the following special characters: # $ \ ' | ~ ! @ % ^ ; ` ( ) { } ? \ " [ ] + = & : > < * / |
| SQL query | Enter a 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 annotation | Select this option to display the query result as an annotation on number of records metric. |
Environment Settings details
| Field | Description |
|---|---|
| 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:
For more information about logging, see Using debug logging in the BMC 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 | Specify 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:
If you enter a path for the JRE directory, you must enter the full path, such as If you do not enter a value in this field, the KM looks for the Java installed in the PATROL Agent home directory as:
|
| JVM Arguments | Enter the optional Java Virtual Machine (JVM) arguments for the Java collector |
| User name | Enter the local user name to start the Java process. |
Password Confirm password | Enter the user password to start the Java process. |
Collection settings | |
| 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 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.
To verify the configuration, click here.
Comments
Log in or register to comment.