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

From: Frits Hoogland <frits.hoogland_at_gmail.com>
Date: Thu, 16 Oct 2014 17:44:32 +0200
Message-Id: <17909E81-9B62-4C85-AD52-E6583A1FCF3D_at_gmail.com>



Yes, DNFS has the database (processes) directly talking to the NFS server, so it excludes a filesystem on the machine on which the database processes are running. Regular NFS means it's mounted as a filesystem on the server where the database is running. So yes, DNFS (probably, I can't test this) does not use filesystemio_options, I found regular NFS to use filesystemio_options settings.

Frits Hoogland

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

On 16 Oct 2014, at 17:29, Hans Forbrich <fuzzy.graybeard_at_gmail.com> wrote:

> On 16/10/2014 3:35 AM, Frits Hoogland wrote:

>> 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.

> Then it becomes important to know which NFS?
>
> I believe DNFS behaves different than standard NFSv3 which may be different again from NFSv4
>
> /Hans
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Oct 16 2014 - 17:44:32 CEST

Original text of this message