It could be an old file and not being used. In that case, you
could delete it. Or, you could play it safe and symlink all three.
BTW, shared writeable mmap was checked in 2.6.23. It will be
available in 1.4.
Silviu Marin-Caea wrote:> About FAQ 49, specifically, this paragraph:
> "Also as OCFS2 does not currently support shared writeable mmap, the
health
> check (GIMH) file $ORACLE_HOME/dbs/hc_ORACLESID.dat and the ASM file
> $ASM_HOME/dbs/ab_ORACLESID.dat should be symlinked to local filesystem. We
> expect to support shared writeable mmap in the OCFS2 1.4 release."
>
>
> In $ORACLE_HOME/dbs there are three hc_ files. Assuming the ORACLE_SID is
> prod for the RAC and prod1, prod2 for each node respectively, we have three
> files named:
> hc_prod.dat
> hc_prod1.dat
> hc_prod2.dat
>
>
> It's clear what to do with hc_prod1.dat and hc_prod2.dat, but what
about
> hc_prod.dat? Do I leave in the shared home?
>
>
>
>
> A little additional info on hc_ files:
>
> "Q1: What is the $ORACLE_HOME/dbs/hc_<ORACLE_SID>.dat file?
> A1: The $ORACLE_HOME/dbs/hc_<ORACLE_SID>.dat is created for the
instance
> health check monitoring. It contains information used to monitor the
> instance health and to determine why it went down if the instance isn't
up.
> The file will be recreated at every instance startup.
>
> Q2: What happens if the $ORACLE_HOME/dbs/hc_<ORACLE_SID>.dat file is
deleted?
> A2: Per Bug 4645405 UNABLE TO START DB - ORA-7445 [KSIHSMRINI()+152]
[SIGBUS],
> if you replace the file with an empty "dummy" copy, you will get
an ORA-7445
> error. Therefore, if the file gets deleted on the fly while the database
is
> up, or if the file is replaced with a 0 byte file, simply delete the file
and
> restart the database. The file will be correctly recreated at the next
> database startup."
>
>
> _______________________________________________
> Ocfs2-users mailing list
> Ocfs2-users@oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-users
>