Using The OpsLogix Oracle Two-State Monitor Template

Using The OpsLogix Oracle Two-State Monitor Template

Although the OpsLogix Oracle Management Pack covers the most common availability, health and performance metrics that are important to an Oracle environment, occasionally you might need other metrics to suit your particular monitoring needs. With this in mind, the OpsLogix Oracle Management Pack contains templates that allow you to add custom monitors and rules in order to monitor your Oracle environment.

OpsLogix Oracle Two-State Monitor Template

One of those templates is the OpsLogix Oracle Two-State Monitor Template, allowing you to create a Rule that checks values from your Oracle environment and generates alerts in an event when a value is detected or missing, depending on the configuration you’ve specified.

Step 1

After you have clicked Create, you can then check your target’s Health Explorer on your monitor, shown under Performance.

 

 

 

 

Step 2

Select the Oracle Two-State Monitor Rule from the Select the monitoring type list.

 

Step 3

Set a name and a description for your Two-State Monitor.

 

Step 4

Write the query to be executed and pick the column name of the value you would like to monitor. Then pick the target of your monitor and the frequency of monitoring.

 

Step 5

Select if you want the monitor to alert Warning or Critical when it discovers a value Greater, Greater or Equal, Less or Equal or Less than a specified Value.

 

Step 6

Finally, configure the alert details. Choose an alert name, a description, the priority of the alert and the severity. To create the Two-State Monitor press Create.

 

Step 7

After you have clicked Create, you can then check your target’s Health Explorer on your monitor, shown under Performance.

For any other questions or inquiries, please contact sales@opslogix.com

How To Use The OpsLogix Oracle Performance Collection Rule Template In SCOM 2012 & 2016

How To Use The OpsLogix Oracle Performance Collection Rule Template In SCOM 2012 & 2016

Although the OpsLogix Oracle Management Pack covers the most common availability, health and performance metrics that are important to an Oracle environment, occasionally you might need other metrics to suit your particular monitoring needs. With this in mind, the OpsLogix Oracle Management Pack contains templates that allow you to add custom monitors and rules in order to monitor your Oracle environment.

OpsLogix Oracle Performance Collection Rule

One of those templates is the OpsLogix Oracle Performance Collection Rule, that allows you to create a Rule that collects performance data from your Oracle environment in order to visualize the data on the corresponding performance view. In this blog, we’ll provide you an easy 5 step “how to” instruction to make use of this template.

Step 1

Navigate to the Authoring section of the System Center Operations Manager Console, right-click Management Pack Templates and choose Add Monitoring Wizard.

 

 

 

Step 2

Select Oracle Performance Collection Rule from the Select the monitoring type list.

 

Step 3

Choose a name and a description for your performance data collection rule. 

 

Step 4

Pick the counter name, set the query to be executed and pick the column name of the value you would like to store. Then chose the target of your rule and the frequency of the data collection. Then click Create.

 

Step 5

The performance collection rule has now been created so you can check the collected performance data in the Instance Performance view.

 

For any other questions or inquiries, please contact sales@opslogix.com

KB: Fixing the “Object reference not set to an instance of an object” error during the Oracle connection TEST

KB: Fixing the “Object reference not set to an instance of an object” error during the Oracle connection TEST

*Update : Rollup 10 for SCOM 2012 SP1 fixes this issue (https://support.microsoft.com/en-us/kb/3071088)

*Update : Rollup 7 for SCOM 2012 R2 fixes this issue (https://support.microsoft.com/en-us/kb/3064919)

Issue:

You are deploying the OpsLogix Oracle Management Pack to an environment using a Windows 2008 R2 (or earlier) server as an Oracle Monitoring Node (1). Using the “Oracle IMP Configuration Dashboard” to setup the Oracle Instances monitoring you get an error message (3) “Object reference not set to an instance of an object” when clicking the “Test Connection” button (2).

 

Analysis:

This problem is related to the Dot Net version loader. This loader is built into the SCOM agent and will decide with wicht Dot Net version to load at runtime. The OpsLogix Oracle Management pack uses a Dot net 4.0 module. The agent still tryies to load it as a Dot Net 2.0 module which will result in an error.

Solution:

Since this is an internal SCOM agent issue, and not directly OpsLogix related, we have the following workarounds:

  • Microsoft recognised this issue and indicated that the next RU for SCOM 2012/SP1/R2 will include this loading fix.
  • You can manual install a SCOM Gateway instead of a SCOM agent.
    Note:
    • You don’t have to generate any certificates.
    • Do NOT run the Gateway Approval tool.
    • Use the Pending Management for approving the agent add (be sure the SCOM security setting allow this)
    • A SCOM Gateway will work exactly like a normal SCOM agent except it is tuned for handling higher workloads.

If you have any questions please contact our support team at Support@opslogix.com

 

Sizing SCOM for the Oracle Management Pack

Sizing SCOM for the Oracle Management Pack

When implementing a new Management Pack in System Center Operations Manager (SCOM) sizing is extremely important if you want to keep your SCOM environment healthy and responsive. For implementing the OpsLogix Oracle Management Pack there are a few sizing scenarios you might want to consider before importing the Management Pack.

There are also 5 main factors that determine the number of instances you can monitor from one monitoring node:

  • Number of tablespace in an Oracle instance
  • Type of SCOM server used
  • Other workflow that are run on the SCOM agent
  • Number of enabled/disabled/custom rules and monitors in the management pack
  • Hardware sizing

This post is based on V1.3.12.130 of the OpsLogix Management Pack for Oracle.

 

Scenario’s for running the Oracle Management Pack on a Monitoring node:

  1. Running the management pack from a SCOM Management server
  2. Running the management pack from a SCOM Gateway Server
  3. Running the management pack from a SCOM Agent machine

 

 

Running the management pack from a SCOM Management server

When running the management pack from a dedicated SCOM Management server you should be able to monitor 20 instances when the following criteria are met:

  • The Management Server does not run any other major workloads
  • The average number of tablespaces per instance should not exceed 20
  • The server has at least 8 GB RAM and 2 CPU’s
  • Only the default monitors and rules in the management pack are enabled

 

 

Running the management pack from a SCOM Gateway Server

When running the management pack from a dedicated SCOM Gateway server you should be able to monitor 20 instances when the following criteria are met:

  • The Gateway Server does not run any other major workloads
  • The average number of tablespaces per instance should not exceed 20
  • The server has at least 4 GB RAM and 2 CPU’s
  • Only the default monitors and rules in the management pack are enabled
  • For the increased workload you will need to configure registry settings and overrides on the Gateway Server as shown in the appendix.

 

Running the management pack from a SCOM Agent machine

When running the management pack from a dedicated SCOM Agent server you should be able to monitor 20 instances when the following criteria are met:

  • The SCOM Agent Server does not run any other major workloads
  • The average number of tablespaces per instance should not exceed 20
  • The server has at least 4 GB RAM and 2 CPU’s
  • Only the default monitors and rules in the management pack are enabled
  • For the increased workload you will need to configure registry settings and overrides on the SCOM Agent Server as shown in the appendix.

Appendix: Adding registry settings and overrides to scom agents:

In order for the SCOM Agent or Gateway to be able to handle the larger workload the following registry settings need to be set on the server:

  • reg add “HKLM\SYSTEM\CurrentControlSet\services\HealthService\Parameters” /v “State Queue Items” /t REG_DWORD /d 20480 /f
  • reg add “HKLM\SYSTEM\CurrentControlSet\services\HealthService\Parameters” /v “Persistence Checkpoint Depth Maximum” /t REG_DWORD /d 104857600 /f

 

 

For the increased workload you will need to set the following overrides on the SCOM Agent or Gateway Server:

Navigate to:

System Center 2012 Operations Manager – Operations Console > Authoring > Management Pack Objects > Monitors

Locate Health Service > Entity Health > Performance> System Center Management Health Service Performance > System Center Management Health Service Memory Utilization > Health Service Private Bytes Threshold

Right-click and select Properties > then from the ‘Health Service Private Bytes Threshold Properties’ select the Overrides tab> click the Override… button and choose ‘For a specific object of class: Health Service

Find the server you are using as a monitoring node, select it and click OK

Check the Override box by ‘Agent Performance Monitor Type – Threshold’ and change the ‘Override Value’ (scroll to the right) to 31457280000

Save the override.

Navigate to:

System Center 2012 Operations Manager – Operations Console > Authoring > Management Pack Objects > Monitors

Locate Health Service > Entity Health > Performance> System Center Management Health Service Performance > System Center Management Health Service Memory Utilization > Health Service Handle Count Threshold

Right-click and select Properties > then from the ‘Health Service Handle Count Threshold Properties’ select the Overrides tab> click the Override… button and choose ‘For a specific object of class: Health Service

Find the server you are using as a monitoring node, select it and click OK

Check the Override box by ‘Health Service Handle Count Threshold – Threshold’ and change the ‘Override Value’ (scroll to the right) to 31457280000

Save the override.

You receive an “Oracle Instance Connection Monitor” Alert after configuring an instance in the “Oracle IMP Configuration Dashboard”

You receive an “Oracle Instance Connection Monitor” Alert after configuring an instance in the “Oracle IMP Configuration Dashboard”

When configuring the Oracle Management Pack, the management pack sometimes throws “Oracle Instance Connection Monitor” Alerts because it cannot connect to the Oracle database/instance.

 

When this happens, check if the Host Name and Instance Name you configured in the “Oracle IMP Configuration Dashboard” correspond with the names in the TNSNames.ora file.

 

The TNSNames.ora file is usually found in the following directory on Linux servers installed with Oracle 11g: /u01/app/oracle/product/11.2.0.db_1/network/admin.

The Host Name in the “Oracle IMP Configuration Dashboard” should correspond with the HOST field highlighted in the TNSNames.ora.

The Instance Name in the “Oracle IMP Configuration Dashboard” should correspond with the SERVICE_NAME field highlighted in the TNSNames.ora.

More efficient session usage by Oracle Management Pack v 1.3.12.1

More efficient session usage by Oracle Management Pack v 1.3.12.1

The first releases of the Oracle Management Pack did not manage the number of sessions used on an Oracle database all that well. As can be seen in the Oracle Enterprise Manager screenshot below (peak 1 and 2 on the graph), the OPSLOGIX user opens many sessions and causes a rather high CPU and CPU Wait time.

 

With the performance improvements made in version 1.3.12.1 of the Oracle Management Pack, the performance overhead for monitoring the Oracle database has been dramatically reduced. The screenshot below shows the performance of the old Management Pack in peak 3. Peak 4 shows the initial upgrade of the Oracle from the previous version to version 1.3.12.1. Peak 5 shows the normal performance footprint when operating normally. Also notice that there are now only three OPSLOGIX sessions active.