FS Mount Options Advices

  With Standard mount options With optimized mount options

Oracle binaries

/u01

mount –o rw

Cached by AIX (fscache)

mount –o noatime

Cached by AIX (fscache)

noatime reduce inode modification on read

Oracle Datafile

/u0[2-5]

mount –o rw

Cached by AIX (fscache)

Cached by Oracle (SGA)

mount –o noatime,cio

Cached by Oracle (SGA)

Oracle Redolog

/u0[6-7]

mount –o rw

Cached by AIX (fscache)

Cached by Oracle (SGA)

mount –o noatime,cio

jfs2 agblksize=512 (to avoid io demotion)

Cached by Oracle (SGA)

Oracle Archivelog

/u08

mount –o rw

Cached by AIX (fscache)

mount –o noatime,rbrw

Use jfs2 cache, but memory is released after read/write

Concurrent I/O should only be used for Oracle .dbf files (data & index, rbs or undo, system and temp) online redo logs and/or control files. When used for online redo logs or control files, these files should be isolated in their own JFS2 file system(s) that have been created with agblksize=512. File system(s) containing .dbf files should be created with agblksize=2048 if DB_BLOCK_SIZE=2k, or agblksize=4096 if DB_BLOCK_SIZE>= 4k or larger. Failure to implement these agblksize guidelines is likely to result in a severe performance penalty.

Note: 

Do not, under any circumstances, use CIO mount option for the file systems containing the Oracle binaries. Additionally, do not use DIO/CIO options for file systems containing archive.

Read MetaLink ID 960055.1

For more tips about configuring and tuning AIX for Oracle, see Oracle_on_AIX_Webinar.