Skip to content
English
Submit a support ticket Customer portal
Back to www.opslogix.com
  • There are no suggestions because the search field is empty.

Oracle Management Pack Installation Guide

Installation guide for the Opslogix Oracle Management Pack for System Center Operations Manager

Applies to: Opslogix Oracle Management Pack (all versions)
Last updated: November 2026 · Latest version: 26.11.4544.0

See also: Upgrade guide for 26.11.4544.0 · Version support · Release notes

Installation guide

Before importing the Opslogix Oracle Management Pack, please read the license agreement in the installation folder carefully.

Prerequisites

  • The Opslogix Oracle Management Pack requires System Center Operations Manager 2016, 2019, 2022 or 2025.
  • Microsoft .NET Framework 4.7.2 or higher, on 64-bit Windows, must be installed on all resource pool members (the SCOM management or gateway servers, not the Oracle servers).
  • You don't need to install an Oracle client or ODAC on the resource pool members: the Opslogix Oracle Collector includes Oracle's managed .NET driver (ODP.NET). Do not install Oracle ODAC components manually on the pool members.

Compatibility

The Opslogix Oracle Management Pack supports Oracle Database 19c, 21c, 23ai and 26ai, including patch updates. These are the versions supported by the Oracle ODP.NET driver included in the pack. See Version support Oracle Management Pack.

  • Oracle 19c
  • Oracle 21c
  • Oracle 23ai
  • Oracle 26ai

Monitoring Architecture

The Opslogix Oracle Management Pack monitors Oracle 19c, 21c, 23ai and 26ai databases on any operating system. Nothing is installed on the Oracle servers.

To monitor Oracle servers, the Opslogix Oracle Management Pack makes use of an Operations Manager Resource Pool. This pool contains one or more management/gateway servers that will act as a monitoring proxy to gather the Oracle monitor data and passing the monitoring information from Oracle servers to Operations Manager. Only a SCOM management server or a SCOM gateway server can be considered a resource pool member. The best scenario for efficient monitoring would be to add two or more members to the resource pool. Doing this will enable you to get failover and load balancing functionalities. In the case of one pool member going down the others will take over and by default, the load will be spread over the available members.

The Opslogix Oracle Collector service is installed automatically on all pool members during the first Test Connection (see "Add the Oracle instance(s)"). It connects to each Oracle instance through the Oracle listener, by default on TCP port 1521; make sure this port is open from all pool members to the Oracle servers.

Configuring the Oracle Management Pack

Configuration steps

Importing the Management Packs

Before importing the Opslogix Oracle Management Pack make sure that you have the following files available:

OpsLogix.BaseLibrary.mp
OpsLogix IMP - Licensing Dashboard (.mpb)
OpsLogix.IMP.Generic.Reports.mpb
OpsLogix.IMP.Oracle.Library.mpb
OpsLogix.IMP.Oracle.mpb
OpsLogix.IMP.Oracle.Collector.mpb
OpsLogix.IMP.Oracle.Config.2012.mpb (monitor templates)
OpsLogix.IMP.Oracle.Config.Dashboard.2012.mpb (configuration dashboard)
OpsLogix.IMP.Oracle.Dashboards.mpb
OpsLogix.IMP.Oracle.Tasks.mpb
OpsLogix.IMP.Oracle.Reports.mpb
OpsLogix.IMP.Oracle.DataGuard.mpb (optional)
OpsLogix.IMP.Oracle.Overrides.mpb (optional, for your overrides)

*The version number displayed as “x” will change with every release.

To import the Opslogix Oracle Management Pack complete the following steps:

Navigate to the Administration section of the Operations Manager console:

  1. Right click Management Packs -> Import Management Packs… -> Add -> Add from Disk
  2. Browse to the location where you’ve unpacked the Opslogix Oracle Management Pack.
  3. Click Open -> Import -> Add From Disk
  4. Import all .mp and .mpb files from the Management Packs folder of the release.

Please note:

After importing the Oracle Management Pack, wait for ± 15 minutes to allow the Management Pack to distribute its components.

Add license key

  • Obtain a valid license key by contacting support@opslogix.com or fill in the contact form on opslogix.com
  • Navigate to Monitoring -> OpsLogix -> OpsLogix License Dashboard. See step 1 and 2.
  • Click the Add license See step 3 and 4.
  • Paste the obtained license key in the Add License Dialog without any preceding or trailing spaces or carriage returns. If you are importing multiple licenses, copy and paste all the licenses sent by OpsLogix (in the license file) without any preceding or trailing spaces or carriage returns. See step 5.
  • Click the Import License(s) See step 6.

Add the monitoring Proxy/Pool

  • Login to an Operations Manager Management Server with a user account that has administrator permissions in Operations Manager and open the Operations Console. Then navigate to the Administration pane. See step 1.
  • Select the Resource Pools See step 2.
  • Now select: Create Resource Pool. See step 3.
  • Add the members that you want to act as the Oracle monitoring proxy. See step 4 and 5.
  • Save the Resource pool. See step 6.

Setting up the Oracle monitoring account

The Opslogix Oracle Management Pack requires read permissions on an Oracle database for monitoring. If you do not have a suitable Oracle account/login for monitoring, you can create a monitoring account by using the following Oracle SQL statements. The example below creates an Opslogix user account for monitoring.

CREATE USER opslogix

IDENTIFIED BY <password> -- Assign password

DEFAULT TABLESPACE users -- Assign space for table and index segments

TEMPORARY TABLESPACE temp -- Assign sort space

QUOTA UNLIMITED ON users -- Assign unlimited quota

GRANT CREATE SESSION, SELECT ANY DICTIONARY,SELECT ANY TABLE TO opslogix -- Assign privileges

For minimal privileges, see KB: How to create the monitoring account for the Oracle monitoring.

Add the Oracle instance(s)

  • Navigate to Administration -> OpsLogix MP Configuration -> Oracle IMP Configuration Dashboard and click on the Add/Remove Monitoring Instance See step 1 and 2.
  • On the Add/Remove Instance tab select the resource pool from which you would like to monitor an Oracle instance by using the Resource Pool dropdown box. See step 3 and 4.
  • Enter the Fully Qualified DNS Name of the Oracle server you would like to monitor in the Server Name Then enter the Oracle instance name in the Instance Name box. In the User Name box enter the monitoring user name (See chapter: Setting up the Oracle monitoring account) and enter the password twice in the password fields. See step 5.
  • Select using the “DBA Role” list box the correct privilege role. You can choose “SYSDBA”,

“SYSOPER” or ”SYSDG”. If you want to connect without using special privileges you can leave this field empty.

  • Click Test Connection and the connection will be tested using the selected monitoring host. See step 6.
  • If the connection test is successful click Add Instance. See step 7 and 8.

Repeat the steps mentioned above for all the Oracle Instances you would like to monitor.

The first Test Connection for a resource pool also installs the Opslogix Oracle Collector service on all members of that pool. If the test fails, see the articles "Troubleshooting: Collector service not deployed or no Oracle instances monitored" and "Troubleshooting: Instance connection alerts and common ORA errors".

Assign the Oracle Licensing

After we have added a new Oracle Instance to monitor we have to assign a license to it.

  • Navigate to Administration -> OpsLogix MP Configuration -> Oracle IMP Configuration Dashboard and click on the Assign See step 1 , 2 and 3.
  • Press the Refresh button to load the current assigned licenses. See step 4.
  • In the table below select the instances you want to assign a license too. See step 5.
  • Click Update to save the selected assignments. See step 6.

Bulk Import\Export Oracle Instances

Sometimes you’ll have to add multiple Oracle instances for monitoring. This can be very time consuming. To save yourself a lot of time and trouble you can also use the Bulk Import\Export option. The Export function will export all existing Oracle connections to an XML file that you have specified. The Import function will to the reverse. Before you can use the import function you will have to follow some steps. First you will have to prepare an import file and as the final step of the process do the importing itself.


Please follow the steps below to create the import file:

  • Create a text file with the extension of .XML
  • Add the following row below in the text file:
    <OracleInstances>
  • For every Oracle instance you want to add a new row as shown below. Replace the parameters by the correct values. Keep in mind that the password must be plain text; delete the file after the import. The attribute names are case-sensitive; copy them exactly from the sample below. MonitoringPool must be the internal name of the SCOM resource pool, as shown in the Name column of: Get-SCOMResourcePool | Format-Table Name, DisplayName. DBAPrivilege can be SYSDBA, SYSOPER, SYSDG or empty.
<OracleInstance
MonitoringPool="internalNameOfTheResourcePool"
ServerName="fqdnOfTheServer"
InstanceName="serviceName"
Port="1521"
UserName="monitoruser"
Password="plainPassword"
DBAPrivilege=""
MaxConnections="20"
MinConnections="1"
ConnectionLifetime="0"
ConnectionTimeout="600"
/>
  • When you have added all the Oracle instance rows, as a final step add the row below in the text file:
    </OracleInstances>

Save the file to a location on a disk and continue below.

Next use the “Bulk Import\Export Oracle Instances” tab of the Oracle IMP Configuration Dashboard to select the XML file created above.

  • Navigate to Administration -> OpsLogix MP Configuration -> Oracle IMP Configuration Dashboard and click on the Bulk Import\Export Instances See Step 1.
  • To Import: Press Import and select the .XML file that contains the Oracle instances to add to the monitoring. See step 2 .
  • To export, Press Export and select the .XML file were to add all the existing Oracle instances. See step 3
  • The logging of the import/export will be shown in the log area. See step 4

Please note that NO connection checks will be performed.

DataGuard configuration

If you are using DataGuard monitoring, then first import the DataGuard Management Pack. When you have done that, follow the steps as described in the ADD THE ORACLE INSTANCE(S) paragraph. Except this time, you will have to add the DG (primary and standby) instances by selecting the DBA Role to “SYSDBA” or “SYSDG”. This is an important step since this privilege is needed to be able to monitor standby instances. For SYSDBA connections to a mounted standby database, enter the SID instead of the service name. See the article "Data Guard monitoring: setup and troubleshooting".

Alert log monitoring

Alert log monitoring is disabled by default. See the article "How to enable Oracle alert log monitoring" for the steps.