"Translated from MoS article" in the RAC database, the Hc_<sid>.dat file is used by instances under other oracle_home.

In a RAC database, the Hc_<sid>.dat file is used by instances under other oracle_home.


Reference text:
RAC database Hc_<sid>.dat is used by instance of different Oracle_home (Doc ID 1618161.1)


Suitable for:
Oracle database-enterprise edition-version 11.2.0.0 and later
Information in this document applies to any platform.


Symptoms:
In the cluster environment, different Oracle home runs under different database


A health check file for a database is used by an instance under other Oracle home Hc_<sid>.dat.

Hc_<sid>.dat files is shared with other databases ' instances.       Example:-----------#lsof/u0n COMMAND PID USER FD TYPE DEVICE size/off NODE NAME Oracle 8167 Oracle 60r VREG 388,50 1544 48967 hc_sqa2d101.dat Oracle 8167 Oracle 72R VREG 388,50 15          78760 hc_sqa2e101.dat Oracle 8563 Oracle 60r VREG 388,50 1544 48967 Hc_sqa2d101.dat Oracle 8563 Oracle 72r VREG 388,50 1544 78760 hc_sqa2e101.dat ... oracle 20049 Oracle 60r VRE     G 388,50 1544 48967 hc_sqa2d101.dat ===> ora_pz99_s20dv101 Oracle 20049 Oracle 72R VREG 388,50 1544 78760 Hc_sqa2e101.dat ===> ora_pz99_s20dv101. Hc_sqa2e101.dat file is used by ora_pz99_s20dv101 of s20dv101 instance. #ps-ef | Egrep ' 8167 |           8563 |20049 ' Oracle 8167 1 0 23:45:33?           0:11 ora_cjq0_sqa1d101 Oracle 8563 1 0 23:46:54? 0:02 ora_smco_sqa1e101 Oracle 1074 2870 12:04:05 pts/1 0:00 egrep 8167 |           8563 |20049 Oracle 20049 1 0 00:24:22? 0:25 ora_pz99_s20dv101

This behavior also occurs in Oracle Restart/siha node.


Change:
Out-of-place migration.


After the Out-of-place upgrade, the old file system cannot be unmount off because it is still in use.
File Hc_<instance_name>.dat under the old Oracle_home/dbs directory is locked by many processes in other instances.


Reason:
This is reported in


BUG 14351771-hc_<sid>. DAT SHARED with other DATABASES


Which is duplicate of unpublished bug 12792223.

Solution:
Apply Patch: 12792223.


The bug was resolved in 11.2.0.4 and later versions.