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

KB: How do I enable Debug Logging for the SCOM Oracle Monitoring

In some cases it is needed to get more internal logging on what the SCOM Oracle Monitor processes are executing. Using a special registry key you can accomplish this.

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

Activate debug logging

Do these steps on every SCOM management or gateway server in the resource pool used for Oracle monitoring (the servers where the Opslogix Oracle Collector is running).

  1. Run these commands as administrator:
    reg add "HKLM\Software\OpsLogix\Oracle\client modules" /v "DebugLevel" /t REG_DWORD /d 5 /f
    reg add "HKLM\Software\OpsLogix\Oracle\collector" /v "DebugLevel" /t REG_DWORD /d 5 /f
  2. Stop the Microsoft Monitoring Agent (HealthService).
  3. Clear the Operations Manager event log.
  4. Increase the maximum size of the Operations Manager event log; trace logging writes many events.
  5. Restart the "OpsLogix Oracle Collector" service.
  6. Start the Microsoft Monitoring Agent (HealthService).

All debug messages are now written to the Operations Manager event log, with event sources starting with "OpsLogix Oracle". The collector itself logs with event source "OpsLogix Oracle Collector".

Deactivate debug logging

Debug logging generates a lot of events. When you have collected the information you need, remove the registry values created in step 1, or set DebugLevel to 0, and restart the services as above. Possible values:

DebugLevel Logging Mode
-1 SilentMode
0 ExceptionMode (Default)
1 VerboseMode
3 DebugMode
5 TraceMode