Seems' like we're going to try this. I'll let you know how it went :)
On 12/14/05, Kevin Closson <kevinc_at_polyserve.com> wrote:
>
> OK then, sure. Test fault injections. Fire
> up some heavily modify intensive workload (e.g.,
> conventional path loads concurrently, several concurrent
> CTAS statements, etc) and drive the I/O up as far as
> possible then reach back to the HBA and pull the gbic.
> After Oracle melts down, reinstate the path to the
> SAN. Make sure ASM and Oracle can come up. Do this
> a few times.
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
--
Christo Kutrovsky
Senior Database/System Administrator
The Pythian Group
--
http://www.freelists.org/webpage/oracle-l
Received on Wed Dec 14 2005 - 16:18:46 CST
