Troubleshooting: Collector service not deployed or no Oracle instances monitored
What to do when the Opslogix Oracle Collector service is missing on a resource pool member, or when your Oracle instances are not monitored.
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
Symptoms
- Oracle instances are added in the configuration dashboard, but no objects, health states or performance data appear.
- Test Connection fails, or works from one pool member but not from another.
- The "State Oracle Collector Service" view in the Oracle folder of the Monitoring pane does not list every pool member.
How the collector is deployed
The collector is installed or updated on all members of a resource pool when you run "Test Connection" for an Oracle connection of that pool in the "Oracle IMP Configuration Dashboard". You can also run the task "OpsLogix Deploy Oracle Collector Task" on a management server; it deploys the collector to all members of the selected SCOM resource pool.
Common causes
- You added a new member to the resource pool and did not run a Test Connection afterwards.
- Microsoft .NET Framework 4.7.2 or higher is not installed on the pool member.
- The pool member is a SCOM gateway server. Gateways are supported, but the automatic deployment sometimes fails there because of security settings.
- A virus scanner blocks the installer.
Check the collector
On each pool member, check in "Control Panel\Programs\Programs and Features" that "OpsLogix Oracle Collector" is installed, and in the Services console that the "OpsLogix Oracle Collector" service is running.
Install the collector manually
- On a pool member where the collector works, go to the folder "...\Operations Manager\Server\Health Service State\Resources" and search its subfolders for the file "Oracle.MP.RestBase.Server.NTService.Installer.exe".
- Copy the file to the pool member without the collector and run it as administrator. You can keep all default settings.
- Restart the Microsoft Monitoring Agent (HealthService) on that server.
- Run a Test Connection again in the configuration dashboard.
Still no Oracle instances monitored?
- Check that a license is assigned to the instance (configuration dashboard, Assign tab). Instances without a license are not monitored.
- Check the license itself; see KB: How do I update my Opslogix Oracle Management Pack license.
- Check the "Instance connection" alerts; see the article "Troubleshooting: Instance connection alerts and common ORA errors".
- Turn on debug logging; see KB: How do I enable Debug Logging for the SCOM Oracle Monitoring.