Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > 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_ret on Mar 12, 2017

Views: 570 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

Tags

Classifications

Public