Re:Details on the Oracle failure at JPMorgan Chase
by GBond on Saturday September 18, 2010 @10:37AM
(#1704230)
This is likely the case since the post mentioned that storage controller was initially blamed (but cleared).
Re:Details on the Oracle failure at JPMorgan Chase
by jasonwatkinspdx on Monday September 20, 2010 @02:58AM
(#1708057)
I rarely work with Oracle, so I'm not very familiar with the product line. Thanks for the correction.
What they had here would appear to be database A running on storage A which is replicated at the storage level to storage B where database B waits in an idle state. Because the replication system is "blind" - it only sees its own filesystem containing bytes, not Oracle data structures - it can't tell a good Oracle block from a bad one and copies it.
I do this sort of setup for a living and you would be amazed at how many "architects" there are around who have completely drunk the storage vendor kool-aid and don't really understand how anything works (not even storage...).