After recognising that filesystemio_options parameter is corrupted (it showed asuncche_size value instead of asynch) even after the database was rebounced, I changed it to asynch dynamically and trussed CKPT process. There are calls for open() subroutine but they are with DSYNC flag: open("/<...>/system01.dbf", O_RDWR|O_DSYNC|O_LARGEFILE) = 13 open("/<...>/tools01.dbf", O_RDWR|O_DSYNC|O_LARGEFILE) = 17 open("/<...>/users01.dbf", O_RDWR|O_DSYNC|O_LARGEFILE) = 16 And all that for file system mounted with CIO option. Looks like file system mounted with CIO without changed database parameter might worsen database performance. Regards, Andrey Goryunov On 21/02/07, Allen, Brandon <Brandon.Allen@xxxxxxxxxxx> wrote:
Not positive on this, but I think it's because in 9i Oracle doesn't issue the O_CIO flag with its file open calls, so it relies on the filesystem's default mount options. -----Original Message----- From: fmhabash@xxxxxxxxx [mailto:cnewtonne@xxxxxxxxx] If this is the case, why is it required then to mount the FS with cio for 9i even if you set it to 'setall'. Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it. -- //www.freelists.org/webpage/oracle-l
-- Sincerely, Andrey Goryunov.