Re: Anyone tried kill ASM in 11gR2 RAC?
- From: K Gopalakrishnan <kaygopal@xxxxxxxxx>
- To: exriscer@xxxxxxxxx
- Date: Thu, 21 Jan 2010 06:38:59 -0600
Clusterware failure will happen _only_ when it can not acess the
physical devices (disk timeout in css) and shutting down ASM does not
revoke the access to disks. In your case clusterware _knows_ the
location of ocr/voting information in ASM disks and it can continue
reading/writing even ASM instance is down.
-Gopal
On Thu, Jan 21, 2010 at 2:51 AM, LS Cheng <exriscer@xxxxxxxxx> wrote:
> Hi
>
> I was doing some cluster destructive tests on RAC 11gR2 a few days ago.
>
> One of tests was kill ASM and see how does that affects Clusterware
> operation since OCR and Voting Disks are located in ASM (OCRDATA Disk
> Group). After killing ASM nothing happened as it was quicky started up
> again. So far so good. The next test was same test but changing the ASM
> Disks ownership so when ASM is restarted OCR Disk Group cannot be accessed.
> Surprisingly ASM Was started up, Database Disk Group was mounted OCR disk
> Group obviously did not get mounted but then the Cluster was working without
> any problems.
>
> So how is this happening? Doesnt Clusterware need to write and read to
> Voting Disk every second? I was expecting a Clusterware failure in the node
> but everything worked just as everything were ok.
>
> Thanks!
>
> --
> LSC
>
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
