文章存档
相关博文
- ·
- ·
- ·
- ·
- ·
- ·
- ·
- ·
- ·
- ·
分类： oracle
2011-11-17 14:44:50
今天用nfs打开oracle出现下面错误：
sql> alter database open resetlogs;
alter database open resetlogs
*
error at line 1:
ora-01115: io error reading block from file 1 (block # 1)
ora-01110: data file 1:
'/vvfs/data/1.1/192.168.1.154/ data/ora11g/datafile/system.261.754325643'
ora-27072: file i/o error
linux error: 5: input/output error
additional information: 4
additional information: 1
additional information: -1
多次出现，不知道为什么，dbv检查这个文件一切ok。
最后修改了initgan.ora文件内容，增加：
filesystemio_options='setall'
就一切ok了。
关于这个参数的解释：
======================================
my everyday oracle
friday, june 18, 2010
i/o errors using nfs on netapps storage on oracle 10.2.0.4
i recently faced the following issue, on one of my client environment.
after successfully creating a 10g database using nfs file system on a linux os, i turned it over to the client for production implementation. developers started populating the data using schema level import. when a large table is imported, the import failed with the following errors
ora-01115: io error reading block from file 6 (block # 5631)
ora-01110: data file 6: '/u0201/oradata/reportdata.dbf'
ora-27091: unable to queue i/o
ora-27072: file i/o error
linux-x86_64 error: 5: input/output error
additional information: 4
additional information: 5630
after searching several hours on oracle support, found a document that talked about setting up filesystemio_options to 'setall' on nfs file systems for redo log corruption. we did not have any corruption, but i wanted to try it anyway because since we were using nfs.
alter system set filesystemio_options=setall scope=spfile;
after setting this, developers did the imports successfully without any problem.
parameter: filesystemio_options
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"directio" - this allows directio to be used where supported by the os. direct io bypasses any unix buffer cache. as of 10.2 most platforms will try to use "directio" option for nfs mounted disks (and will also check nfs attributes are sensible).
"setall" - enables both async and direct io. the 'setall' option chooses async or direct i/o based on the platform and file system used.
enabling directio against nfs datafiles/redo logs should always be used so that no writes are ever cached in the os buffer cache. the consistency of writes cannot be guaranteed when relying on stateless nfs to perform asynchronous writes over the network.
at 6:51 am posted by my everyday oracle
sql> alter database open resetlogs;
alter database open resetlogs
*
error at line 1:
ora-01115: io error reading block from file 1 (block # 1)
ora-01110: data file 1:
'/vvfs/data/1.1/192.168.1.154/ data/ora11g/datafile/system.261.754325643'
ora-27072: file i/o error
linux error: 5: input/output error
additional information: 4
additional information: 1
additional information: -1
多次出现，不知道为什么，dbv检查这个文件一切ok。
最后修改了initgan.ora文件内容，增加：
filesystemio_options='setall'
就一切ok了。
关于这个参数的解释：
======================================
my everyday oracle
friday, june 18, 2010
i/o errors using nfs on netapps storage on oracle 10.2.0.4
i recently faced the following issue, on one of my client environment.
after successfully creating a 10g database using nfs file system on a linux os, i turned it over to the client for production implementation. developers started populating the data using schema level import. when a large table is imported, the import failed with the following errors
ora-01115: io error reading block from file 6 (block # 5631)
ora-01110: data file 6: '/u0201/oradata/reportdata.dbf'
ora-27091: unable to queue i/o
ora-27072: file i/o error
linux-x86_64 error: 5: input/output error
additional information: 4
additional information: 5630
after searching several hours on oracle support, found a document that talked about setting up filesystemio_options to 'setall' on nfs file systems for redo log corruption. we did not have any corruption, but i wanted to try it anyway because since we were using nfs.
alter system set filesystemio_options=setall scope=spfile;
after setting this, developers did the imports successfully without any problem.
parameter: filesystemio_options
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"directio" - this allows directio to be used where supported by the os. direct io bypasses any unix buffer cache. as of 10.2 most platforms will try to use "directio" option for nfs mounted disks (and will also check nfs attributes are sensible).
"setall" - enables both async and direct io. the 'setall' option chooses async or direct i/o based on the platform and file system used.
enabling directio against nfs datafiles/redo logs should always be used so that no writes are ever cached in the os buffer cache. the consistency of writes cannot be guaranteed when relying on stateless nfs to perform asynchronous writes over the network.
at 6:51 am posted by my everyday oracle
