Knowledge Base

Showing results for 
Search instead for 
Did you mean: 

How to resolve Database Collector not reporting metrics

Users utilizing version 4.3.x Database Agents may experience an issue where the database Collector does not start, and no longer reports metrics to the Controller.


The Database Agent logs will show one of the following errors for the problematic Collector:


Case-1: java.sql.SQLException: ORA-24247: network access denied by access control list (ACL)

: java.sql.SQLSyntaxErrorException: ORA-00904: : invalid identifier, event after applying the Case-1 solution


To resolve case 1, follow the permissions instructions within the documentation for configuring the Oracle RAC.


Another option would be to add the following JVM property to the custom agent build (for custom build information, contact support) if uninterested in making changes to the database permissions.



For case 2, run the following SQL command in the Oracle cluster environment.


select HOST_NAME from gv$instance;


Then validate network connectivity. The Database Agent's machine must be able to TelNet on the listener port (configured for the Collector) for all hosts that are returned from the above query. 



  1. As of version 4.3.x, only one Collector should be sufficient to monitor an entire Oracle cluster.
  2. The Database Agent and Collector user should have access to all the nodes in the Oracle cluster.
  3. If the Database Agent has been upgraded from 4.x to 4.3 then only a single Collector should be enough, the remaining Collectors can be deleted.
  4. Once a Collector is deleted then all historical data will be lost. It is not possible to restore the deleted Collectors.
Version history
Revision #:
7 of 7
Last update:
‎07-06-2017 01:24 PM
Updated by:
Labels (1)

Found this article helpful? Click the Thumbs Up button.
Have an additional comment? Post it below.