Troubleshooting: Instance connection alerts and common ORA errors
The Instance connection monitor alerts when SCOM cannot connect to an Oracle instance. This article explains the Oracle error messages in the alert and what to check.
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
Common Oracle errors
| Error | Meaning | What to check |
|---|---|---|
| ORA-12541: no listener / Cannot connect | The listener is not running or not reachable on the configured host and port. | Is the Oracle listener running? Is TCP 1521 (or your configured port) open from all resource pool members to the Oracle server? |
| ORA-12514: listener does not currently know of service | The instance or service name in the connection is not registered with the listener. | Check the Instance Name in the configuration dashboard. For a mounted Data Guard standby, use the SID. |
| ORA-12170 / connection timeout | The network connection timed out. | Firewalls, routing and DNS between the pool members and the Oracle server. |
| ORA-01017: invalid username/password | The monitoring account or password is wrong. | Update the credentials in the configuration dashboard. |
| ORA-28000: the account is locked | The monitoring account is locked. | Unlock the account in Oracle and check its password policy. |
| ORA-28001: the password has expired | The monitoring account password has expired. | Set a new password in Oracle and in the configuration dashboard. |
| ORA-01031: insufficient privileges | The account is not allowed to connect with the selected DBA role, or lacks a grant. | Check the DBA role (SYSDBA, SYSOPER, SYSDG or none) and the grants; see KB: How to create the monitoring account for the Oracle monitoring. |
| ORA-01219: database not open | The database is mounted, not open (for example a mounted standby). | Supported from V26.4.4517.0 for Data Guard standby databases; see the article "Data Guard monitoring: setup and troubleshooting". |
Is the listener monitored?
Yes, through this connection check. If the listener is stopped or unreachable, the connection fails and you get an alert with the Oracle error message. A separate listener process monitor is not included.
Test the connection
Use "Test Connection" in the "Oracle IMP Configuration Dashboard". The test runs from the resource pool, so it shows exactly what the monitoring sees.
Change the number of retries
The monitor alerts after 2 failed attempts. You can change this with an override on the parameter NumberOfRetrys of the "Instance connection" monitor.