Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Database Performance Analyzer (DPA) > Unable to start monitor for an Oracle database instance

Unable to start monitor for an Oracle database instance

Created by Robert Holtam, last modified by Rodim Suarez on Mar 12, 2017

Views: 94 Votes: 0 Revisions: 4

Overview

When attempting to start the monitor, it just loads with the message -  Monitor Attempting to Start.
Last error in the log says:

The alert [Falcon Oracle Archiver Errors] failed to run against database [Name_Instance] due to the connection error: com.confio.ignite.common.jdbc.exceptions.MonitoredDatabaseConnect ionException: A connection to the monitored database [Name_Instance] could not be established: Connection to the Oracle Listener could not established. Check that host is accessible and the listener is running on the specified port [cause=org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: IO Error: The Network Adapter could not establish the connection]

 

Updating the connection information works and can putt/telnet without errors. TNS resolution is also working.

Environment

DPA 10.0.352

Resolution

Restart the Ignite PI process/service on application server for DPA.

 

Last modified
17:10, 12 Mar 2017

Tags

Classifications

Public