Re: Instance evictions with new 11.2.0.4 Grid install (RHEL 6.6 on VMware 5.5)

Per our VM and storage folks, the issue appears to be a compatibility issue between ESXi 5.5 U2 and IBM SVC micro code V.7.X series. VMware engineers will disable the ATS HB feature for this VM cluster.

I'll get back to this install next week to see if that was the actual issue.

Why RAC on VMware is another story, however, that is the requirement for this install.

On Mon, May 18, 2015 at 8:08 AM, Rich <richa03_at_gmail.com> wrote:

> Hi List,
>
> This is probably more related to VMware, however, I thought this list
> might have some insight to offer…
>
>
>
> ASM alert log shows instances being evicted with something like:
>
> WARNING: Write Failed. group:1 disk:1 AU:234 offset:0 size:4096
>
> ERROR: unrecoverable error ORA-15188 raised in ASM I/O path; terminating
> process 115640
>
> PMON (ospid: 115609): terminating the instance due to error 470
>
> In /var/log/messages, I see emits like:
>
> May 18 07:01:32 <DB host name> kernel: sd 3:0:5:0: reservation conflict
>
> May 18 07:01:32 <DB host name> kernel: sd 3:0:5:0: [sdi] Result:
> hostbyte=DID_OK driverbyte=DRIVER_OK
>
> May 18 07:01:32 <DB host name> kernel: sd 3:0:5:0: [sdi] CDB: Write(10):
> 2a 00 00 08 00 13 00 00 01 00
>
> May 18 07:01:32 <DB host name> kernel: end_request: critical nexus error,
> dev sdi, sector 524307
>
> The devices with “reservation conflict” are used by ASM.
>
>
>
> I know there are/were issues with VMware and shared devices which were
> “fixed” by setting the multi-writer flag (
> http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1034165),
> however, this flag is set for these devices per our VM admin.
>
>
>
> Any ideas as to how to troubleshoot this further?
>
> (I have root access to the VMs, but not lower, yet)
>
>
>
> Thanks in advance,
>
> Rich
>
>
>

--
http://www.freelists.org/webpage/oracle-l