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.
Before you begin
You must download and install PATROL for Oracle Enterprise Database. For more information see Installing and Performance and scalability data.
To configure the monitor type
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.
Click Add and enter the following details.
| Field | Description |
|---|---|
| Environment name | Enter a unique name for the environment. We recommend you to use alphanumeric characters in the environment name. Note
|
| Oracle credentials | |
| User Name | The SYSDBA monitoring user name of the Oracle Database. |
| Oracle connection name | Enter the name of the Oracle Database SID to monitor. The SID name appears in the 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. |
Password | The user password of the Oracle Database. If you are using vault to access the password in BMC Helix Operations Management, enter the query string in the Password and Confirm password field. |
| Connect as | Select how the specified user would connect to the database:
If you select NON SYS, ensure that the standby databases to be monitored are in the read-only mode in Active Data Guard. |
| Data Guard details | |
| Oracle Data Guard connection method | Select how to connect to the Data Guard databases: 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 have Oracle RAC instances, but no standalone Data Guard instances, the value entered in the field acts as a container of RAC instances. The value is not used for the Oracle RAC instances connections. |
Data Guard instance connection details | |
| Oracle host | The host name or the IP address used for the Data Guard Oracle Database. 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. |
| Oracle Data Guard connection method | Select how to connect to the Data Guard database instance:
|
| 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. |
| 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 | |
| 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 | Select the Oracle Database activity categories that you want to monitor.
|
| Jobs | |
| Jobs | Select this option to monitor the jobs and transactions running in the Oracle Database. |
| Long running job time (min) | 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 (min) | The duration for jobs that are overdue because they are not executed (2 minutes late). These jobs may be delayed, broken, or failed. |
| Tablespaces | |
| Tablespaces | Select this option to monitor the tablespaces. To monitor large and very large tablespaces under separate application classes (Oracle Large Tablespace (KOE_INST_LARGE_TABLESPACE) and Oracle Very Large Tablespace (KOE_INST_VERY_LARGE_TABLESPACE)), configure the minimum size (in MB) of the large and very large tablespaces in the following configuration variables (both are required). Set configuration variables on the Configuration Variables > Add Configuration Variable page.
Replace Restart PATROL Agent after configuring these configuration variables. If you do not configure values in one or any of these variables or if the value in For example, you configure the value of the Note: These configuration variables are not applicable to UNDO and TEMP tablespaces. |
| 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.
Note Be cautious when you add spaces while entering the regex search string. Extra space is considered as a character by the search string. |
Filter for top n queries by total wait time For more information, see Monitoring of wait time attributes of SQL query. | |
| Total wait time monitoring | Select this option to enable the filter for top n queries by total wait time. |
| Top Number of queries | Enter the number of queries that you want to filter. |
| Maximum query instances limit | Enter the maximum number of query instances to filter. |
| Number of days to keep query instances | Enter the number of days to store the query instance. |
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: # $ \ ' | ~ ! @ % ^ ; ` ( ) { } ? \ " [ ] + = & : > < * / |
| SQL query | Enter a SQL query. Note The SQL query must not contain the semicolon (;). |
| Collection time (min) | 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 | |
| Logging | Select this option to enable detail level logging for all PostgreSQL databases configured on this environment to get more details about policy configuration and data collection.
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. |
| Java collector settings | |
| Java path | Specify the path to the JRE directory (also known as $JAVA_HOME environment variable) on the PATROL Agent host.
If you enter a path for the JRE directory, you must enter the full path, such 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. |
| Data collection interval (min) | The time interval used for data collection from the environment. |
| 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. |
| Wait time SQL data collection interval (min) | Enter the total time interval in minutes to collect or report the value for the wait time SQL attributes. This attribute is valid for SQL instances attributes only. The default wait time for SQL data collection time is 5 minutes. For more information, see Monitoring of wait time attributes of SQL query. |
Comments
Log in or register to comment.