Re: Fwd: AIX Concurrent I/O for Oracle archive logs
From: Rich Jesse <rjoralist_at_society.servebeer.com>
Date: Tue, 25 May 2010 16:17:58 -0500 (CDT)
Message-ID: <fbbf59c8fd4a01c750ed2862aac8be21.squirrel_at_society.servebeer.com>
> From: David Roberts <big.dave.roberts_at_googlemail.com>
>
> With the appearance of Advanced format hard drives, Oracle has indicated
> that they want to know the underlying disk physical file format for ASM file
> systems and redo logs.
Date: Tue, 25 May 2010 16:17:58 -0500 (CDT)
Message-ID: <fbbf59c8fd4a01c750ed2862aac8be21.squirrel_at_society.servebeer.com>
> From: David Roberts <big.dave.roberts_at_googlemail.com>
>
> With the appearance of Advanced format hard drives, Oracle has indicated
> that they want to know the underlying disk physical file format for ASM file
> systems and redo logs.
However, the OP's asking specifically about *archived* redos. If SETALL is used, redo log files are automagially attempted to be opened CIO on AIX. At least on my 5.3 system they are as shown the "lsof +fg" command the Brandon posted.
My current redo generation and RMAN backup patterns don't generally give me enough of a window to verify this for archived redos however, nor FRA files for that matter. And as the oracle account here doesn't have access to /dev/mem nor /dev/kmem and I don't have access to root, I'm afraid I'm not going to be of much more help.
Perhaps a shell script looping the lsof running in a semi-tight loop (with a 1-second sleep perhaps?) while generating excess redo would show something fun?
Rich
-- http://www.freelists.org/webpage/oracle-lReceived on Tue May 25 2010 - 16:17:58 CDT