Getting Started
      Back to home
      1. Knowledge Base | OpsLogix
      2. Oracle Management Pack
      3. Getting Started

      Upgrade Guide

      Upgrade guide for OpsLogix Oracle Management Pack V21.9.2657.0 for System Center Operations Manager

      This guide describes the upgrade path from previous versions of the to the latest version of the Oracle management pack.

      NOTICE:Please read the release notes found here before upgrading.

      Starting from of version 21.9.2568.0 or higher you will need to upgrade your license key before continuing to implement this version. This key upgrade is free for all subscribed users. Please go to https://portal.opslogix.com/ download the new license and apply it following the steps described here : Update the license   

      If the license key is not updated monitoring will stop and every Oracle target will be undiscovered.

      Software Prerequisites

      • The OpsLogix Oracle Management Pack requires Microsoft System Center Operations Manager 2012 SP1, 2012 R2, 2016, 180x or 2019.

      • The OpsLogix Oracle Management Pack makes use of Microsoft .NET Framework 4.5. It is required that Microsoft .NET Framework 4.5 is installed on all SCOM Management Server and Gateway Servers that are resource pool members in the resource pool used for Oracle monitoring.

      • The Management Pack can be upgraded from of Oracle Management Pack version V1.3.16.x or above

      Oracle Compatibility

      The OpsLogix Management Pack for Oracle supports the following Oracle versions:

      Oracle 10g Update 2 
      Oracle 11g 
      Oracle 12c
      Oracle 19c

      UPGRADE STEPS

      The steps below show the upgrade process for OpsLogix Oracle Management Pack.

      1. SETTING UP THE ORACLE MONITORING ACCOUNT

      Review if the already configured Oracle user account has still the correct privileges. Please see installation manual “SETTING UP THE ORACLE MONITORING ACCOUNT” and “SECURITY LOCKDOWN” to configure the monitoring account. See also KB: How to create the monitoring account for the Oracle monitoring

      2. IMPORT THE NEW MANAGEMENT PACKS

      Import the management packs contained in this release. It is not necessary to uninstall any of the previously imported OpsLogix management packs before importing the current version. If the Operations Manager Console shows errors during the import and the “Install” button is disabled, check if there are management packs already imported with the same version or higher, if this is the case, remove these management packs from the import list. The “OpsLogix IMP - Base Library”, “OpsLogix IMP - Licensing UI for OpsMgr 2012” and “OpsLogix Generic Reports” frequently cause the issue described above.

      Notice: After a successful import please remove, if exists, the management pack named “OpsLogix IMP - Oracle ODAC x64 Pack”.

      Notice: If you are updating from a lower version than 1.3.2184.0 you will have to remove management pack "OpsLogix IMP - Licensing UI for OpsMgr 2012" first before importing this release.

      3. RESTART THE SCOM CONSOLE

      After importing restart the SCOM console to reload the special UI components.

      4. INSTALL \ UPDATE THE ORACLE COLLECTOR

      From of version 1.3.1702.0 of the Oracle management Pack the Oracle monitoring data is collected by a collector service called “OpsLogix Oracle Collector”. To install or update the collector:  After importing this MP version, you will have to do a connection test for only 1 configured Oracle connection per used SCOM resource pool by using the “Test Connection” in the “Oracle IMP Configuration Dashboard”. During this check the OpsLogix Oracle Collector will be installed or updated on all the members of the selected SCOM Oracle resource pool.

      If you get a error code -1 during the Test Connection please have a look at this KB  Fixing Error Code -1

      If the service is not deployed, some common causes are:

      • You have added a new member to the SCOM resource pool and did not do the “Test Connection”
      • You use a SCOM Gateway Server as a resource pool member. Using a gateway is supported, however, in some cases the deployment of the collector service fails. Most of the time due to security issues.
      • Microsoft .Net Framework 4.5 is not installed on the SCOM Management Server or SCOM Gateway Server.
      • A virus scanner is preventing the deployment of the install package.

      If the collector service fails to deploy automatically it needs to be installed manually by following the steps below:

      • On all pool members (SCOM Management Servers and Gateway Servers) that are member of the resource pool used for monitoring Oracle, navigate to “Control Panel\Programs\Programs and Features” and check if the “OpsLogix Oracle Collector” software is installed.
      • If the program “OpsLogix Oracle Collector” is not installed then logon to the SCOM member server(s) to install the “OpsLogix Oracle Collector” manually by copy from an ‘other’ working member server the file in directory “….\Operations Manager\Server\Health Service State\Resources\*” named “Oracle.MP.RestBase.Server.NTService.Installer.exe” and execute this on the new member host(s). You can continue using all default setting.
      • Or follow the steps in the installation manual named “NO ORACLE INSTANCES ARE MONITORED”

      5. ASSIGN A LICENSE TO THE INSTANCE

      After you have imported all the management packs - and you have checked that the Oracle collector is installed on all the resource pool members - you need to assign a license to every Oracle instance you would like to monitor using the “Oracle IMP Configuration Dashboard”. See installation manual chapter “ASSIGN THE ORACLE LICENSING”.

      6. RESTART THE SCOM AGENTS

      On all the SCOM MS servers that are member of the SCOM resource pool you use for the Oracle monitoring restart the SCOM agent to reload the new modules and trigger the discovery.