topic Re: Does /tmp full trigger a failed over in MCSG in Operating System - HP-UX

Does /tmp full trigger a failed over in MCSG

yc_2 — Mon, 11 Aug 2003 05:40:17 GMT

Hi,

Does /tmp full trigger a failed over in MCSG for Oracle ?

Thanks in advance,
YC

Re: Does /tmp full trigger a failed over in MCSG

Massimo Bianchi — Mon, 11 Aug 2003 05:46:24 GMT

Hi,
there are chances that this is possibles, but not directly. A file system full does not trigger anything by itself, but if you have oracle in MC/SG, you use the oracle monitor and uses the /tmp for spool-ing something, then there are chance that some jobs may fail.

If these fails are monitored, then a process failing may trigger something.

But more probably, a /tmp ful will trash your O.S., because it is used by many o.s. programs, and can cause an instable server.

So, indirectly, the answer is yes...

Massimo

Re: Does /tmp full trigger a failed over in MCSG

malay boy — Mon, 11 Aug 2003 05:46:34 GMT

Depend on your lock disk.The one concept for MCSG are lockdisk.It's mean that the server try to hold a lock disk.If the server cannot hold the lock disk , the failed over will happen to the secondary.

regards
mB

Re: Does /tmp full trigger a failed over in MCSG

Tim D Fulford — Mon, 11 Aug 2003 07:31:51 GMT

Generically /tmp/beig full will NOT fail over SG.

However, if you have a service monitor that uses, say, /tmp/ to write to (a temporay status query or something), the service monitor will fail & thus SG may fail over.

It will really depend on HOW you system is configured & being monitored. The other possibility is that /tmp may be used to dump application/database "crash" files. The app/db may have crashed filling up /tmp & failed over anyway. eg /tmp filling up is not the cause, but on of the symptoms.

Regards

Tim

Re: Does /tmp full trigger a failed over in MCSG

Kent Ostby — Mon, 11 Aug 2003 13:19:19 GMT

As stated above, /tmp filling will not absolutely cause a failover.

The best places to look for causes of the failover are in the package logs under the /etc/cmcluster directory and in the /var/adm/syslog/syslog.log (or OLDsyslog.log if the system has been rebooted).

Best regards,

Kent M. Ostby