Re: Is filesystemio_options relevant when the database is on ASM ?

With version 11 ASM (ASM needs to be available on the node where the database lives), and when using Exadata, filesystemio_options is NOT relevant to the database processes when using files (redo, data, temp) on local ASM managed devices. I am not sure with version 12, probably the locality between the device and the ASM instance which it manages is relevant.

When using NFS underneath ASM, I've witnessed filesystemio_options being honoured by the database, which means it needs setting it to 'setall' for the combination AIO+DIO. Which makes sense, because you need to create a file on a (NFS) filesystem to be used as ASM disk device.

Frits Hoogland

http://fritshoogland.wordpress.com
frits.hoogland_at_gmail.com
Office : +31 20 5939953
Mobile: +31 6 14180860

On 16 Oct 2014, at 11:25, Chitale, Hemant K <Hemant-K.Chitale_at_sc.com> wrote:

> Is filesystemio_options relevant when the database is on ASM ?
>
>
> Hemant K Chitale
>
>
>
>
> This email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please delete all copies and notify the sender immediately. You may wish to refer to the incorporation details of Standard Chartered PLC, Standard Chartered Bank and their subsidiaries at https://www.sc.com/en/incorporation-details.html.

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