Sto Rage(c) [mailto:netbacker@gmail.com] wrote: [...]
vol options <vol name> no_atime_update on
On Tue, Dec 05, 2006 at 08:11:21PM +0100, Willeke, Jochen wrote:
do i have to check some things before activating this? I mean is it absolutely for sure that the DB does record it's own timestamps?
Stephen C. Woods writes
This is only the read access time, not the write/create time.
It's much more likely that it's the other clients sharing the volume, not the Oracle DB, which will be (mildly) perturbed by the absence of atime updates ("mildly" because client-side caching means atimes have dodgy semantics under NFS in the first place).
If you can put your Oracle database files in a separate (maybe flexible) volume, then you can turn off atime updates just for that volume.