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

How to move the Oracle Management Pack to a new SCOM management group

Move your Oracle monitoring, licenses and connections to a new SCOM management group, for example during a side-by-side SCOM migration.

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

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

Use this article when you move to a new SCOM management group, for example during a side-by-side migration to a newer SCOM version. If you upgrade SCOM in place (the management group keeps its name), your license stays valid; only check the requirements in Version support.

Before you start: request a license for the new management group

Oracle Management Pack license keys are tied to the name of the SCOM management group. A key for your current management group does not work in a new one. Contact Opslogix sales (sales@opslogix.com) or support with the name of the old and the new management group to get a license key for the new management group.

1. Prepare the new management group

  1. Import the Oracle management packs from the latest release, as described in the Installation Guide.
  2. Import the new license key with the Opslogix Licensing Dashboard, on a management server of the new management group.
  3. Create the SCOM resource pool for Oracle monitoring and add the management or gateway servers.
  4. If you have override management packs or management packs created with the Oracle authoring templates, export them from the old management group (Export-SCOMManagementPack) and import them in the new one.

2. Move the Oracle connections

  1. In the old management group, open the Oracle IMP Configuration Dashboard, tab Bulk Import\Export Instances, and click Export.
  2. Edit the exported XML file:
    • The export does not contain passwords. Add a Password attribute with the password of the monitoring account to every OracleInstance line.
    • Set MonitoringPool to the internal name of the resource pool in the new management group, as shown in the Name column of Get-SCOMResourcePool | Format-Table Name, DisplayName.
  3. In the new management group, import the file on the Bulk Import\Export Instances tab. Delete the file afterwards; it contains passwords in plain text.

You can also add the connections with the PowerShell module.

3. Start monitoring in the new management group

  1. Run Test Connection for one connection per resource pool. This installs the Opslogix Oracle Collector on all pool members.
  2. Assign a license to every instance (Assign tab).
  3. Check that the instances, tablespaces and performance data appear in the Monitoring pane.

4. Clean up the old management group

When monitoring works in the new management group, remove the Oracle instances and management packs from the old one. See How to uninstall the Oracle Management Pack.