Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Re: Using NetApp Filers for a DWH
For your second question: The WAFL technology can have a disastrous effect on full table scans and fast full scans in Oracle10g. You can create this simple mouse trap:-
According to my tests in Oracle10g, many db file sequential read events showed up in the trace file after the update. I have seen as much as 89% degradation in performance. NetApp blamed this on Oracle as a 10g bug. Oracle kinda admitting it, but until now there is no resolution. However, when the same test was ran in Oracle 9.2.0.4 it didn't produce this problem.
-Richmond Shee.
co-author of Oracle Wait Interface
http://www.amazon.com/exec/obidos/tg/detail/-/007222729X/
Hemant K Chitale <hkchital_at_singnet.com.sg> wrote:
I am looking for notes / experiences / suggestions about using [or NOT
using] NetApp Filers
for a DataWarehouse [Oracle 9i].
Two areas of concern I have are :
1. Snapshot areas -- ie, the %age of blocks reserved in a volume to
facilitate snapshots.
In a DWH, a very large [probably 100 to 150%] portion of the database
blocks could be updated
in a day. How do we size space for Snapshots ? Would frequent Snapshots
help ?
2. WAFL and "block-redirection" -- if the Filer actually writes each block
seperately on updates,
what the Database might see as "contigous" blocks in an extent where the
rows of the table
have been deleted and reloaded [ie all or almost all of the blocks have
been affected], might very
well be randomly distributed across the disks. How would multiblock reads
fare ?
Hemant K Chitale
Oracle 9i Database Administrator Certified Professional
http://web.singnet.com.sg/~hkchital
![]() |
![]() |