fusion-io and problems with FILESYSTEMIO_OPTIONS = DIRECTIO or SETALL errors like ORA-01157
Last updated on DECEMBER 07, 2016
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Information in this document applies to any platform.
***Checked for relevance on 07-Dec-2016***
Fusion-io is a solid state disk technology that includes an SDK allowing developers direct access to the storage (memory in ssd). There are multiple vendors that partner with fusionio to produce NAND flash based storage cards for use as storage.
As pointed out in bug 13480832:
Unlike normal SSD solutions, FusionIO internally uses 256 byte sectors...so both 512 and 4k sectors are emulated. Since this is the case...and we can't really do a native 256 byte sector, there wouldn't be a performance benefit to having Oracle use 4k sectors. The biggest benefit would be a reduction in ram usage of the FusionIO driver (which tracks sectors in the server's ram.
It is worth ensuring customers are on version 2 drivers as there are many improvements at the time of this writing. (early 2012).
This has also impacted ASM ability to create diskgroups and is being further investigated in bug 13941884.
database startup attempts give:
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: '/u07/oradata/pdw1/undotbs01.dbf'
ASM diskgroup creation attemts give:
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15080: synchronous I/O operation to a disk failed
Fusion-io devices configured to non 512 byte sector size. (sometimes larger sector sizes are chosen to allow lower os memory usage due to fewer sectors to track in memory).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms