However, the IO administrator was not pleased. He didn't argue with my analysis, but he said he didn't want the database files moved. I asked why. He said because he was saving the devices. I asked, "Saving them for what?" And he actually said, "I'm saving them in case we really need them." While I appreciated his honesty, I knew my role was complete, and the DBAs and the IO administrator had some work to do.

My point is that while we have wonderful load-balancing and management IO capabilities, IO problems are commonly the result of nontechnical issues, and those are just as important as the technical challenges.

Most people in IT are aghast at the cost of an IO subsystem capable of meeting an Oracle system's IO requirements. While I don't disagree with the fact that there is a considerable amount of money spent on IO subsystems, I think it is important to understand the technical challenges IO vendors face to make the impossible, well, possible. It starts with a basic understanding of IO subsystem queuing theory.