My Oracle Support Banner

Healthcheck Metric failing for a Target Database with Agent (Doc ID 602633.1)

Last updated on MARCH 12, 2021

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
HP-UX PA-RISC (64-bit)
IBM AIX on POWER Systems (64-bit)
Oracle Solaris on SPARC (64-bit)
HP-UX Itanium
Microsoft Windows x64 (64-bit)
Linux x86-64
Linux Itanium


Using a Grid Agent to monitor a Database.
The Agent version is certified to monitor a Database.

The <AGENT_HOME>/sysman/log/emagent.trc shows that the health_check metric is repeatedly failing for this database :

Repeated failure while executing this metric can cause the Agent to re-start, as it runs out of file handlers at the OS level.

 -  The database is a 64 bit installation but emagent executable is of 32 bit installation though the
64 bit agent software is installed.
-   Re-starting the database to create this hc_<SID>.dat file does not help in resolving the Healthcheck Metrics error. 
-  The <DATABASE_OH>/dbs/hc_<SID>.dat file has sufficient permissions to be read by the agent 


Database and Agent have been upgraded to from a lower version.
It is possible that when the Database / Agent were at (or below), this metric was not failing.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 For Sun Solaris SPARC (64-bit), HP-UX PA-RISC (64-bit), IBM AIX Based 
Systems (64-bit) , HP-UX Itanium
 For Linux Itanium Operating System
 Workaround :

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.