article Receiving "Could not connect to database" from Oracle Monitor

This article suggests how to troubleshoot and resolve issues related to connecting to an Oracle database with any of the three up.time Oracle service monitors (Basic Check, Advanced Metrics or Tablespace Check).

If an Oracle monitor is failing with the message Could not connect to database, check the following points to ensure that the monitor is properly configured:

  1. Review tnsnames.ora from the Oracle server being contacted.
    • Find corresponding SID entry in the file (the SID field in the Oracle service monitor needs to match the GLOBAL_NAME field, or if it isn't set, the SERVICE_NAME field in tnsnames.ora).
    • Make sure the port matches.
  2. Make sure the necessary firewall port exceptions are in place on the OS and networking devices between up.time and the Oracle database server.
If the connectivity issue still persists, try the following steps, which should generate some messaging that will provide further insight on the root cause of the issue:
  1. Log into Oracle with the same user account that up.time is configured to use to see if any warnings or errors are returned.
  2. On the up.time Monitoring Station server, change the loggingLevel from INFO to DEBUG in <uptime_dir>/uptime.conf to provide further logging (restart the up.time Data Collector or uptime_core service for the change to take effect).  The increased logging can be reviewed in <uptime_dir>/logs/uptime.log.

Related Articles

Running up.time with an Oracle database


By: uptime Support | Date Created: 1-16-2006 | Last Modified: 7-22-2014 | Index: 053


Oracle Advanced Metrics service monitor


This article outlines the performance metrics that the up.time Oracle Advanced Metrics monitor collects from an Oracle database.

By: uptime Support | Date Created: 1-23-2007 | Last Modified: 7-4-2011 | Index: 121


Understanding your Oracle Connection Settings


This article outlines how you can use the information in the Oracle TNS connection string to populate database-specific fields that need to be set in the uptime.conf file.

By: uptime Support | Date Created: 2-27-2007 | Last Modified: 6-30-2011 | Index: 146


Migrating Your DataStore To a New Database


This article outlines how to move your DataStore between different database types.

By: uptime Support | Date Created: 2-21-2007 | Last Modified: 6-30-2011 | Index: 142


Oracle database not responding in up.time interface


If you are seeing a Database Not Responding message in up.time GUI, with something similar to the following error: =================== Database is not responding ...

By: uptime Support | Date Created: 10-14-2009 | Last Modified: 8-13-2011 | Index: 436


User Comments

No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement