Okay, fair enough. I guess you *did* say that. Still, it's not a very "viable" test on systems where you *might* be allowed to restart the database about once every three or four *months*. (And even then, usually only with a darned good reason.)
Oh well...
Anyway, you raise a pretty good point. The question of whether or not your database is actually *using* Asynch I/O is a pretty important one, as the answer has rather profound implications.
Wouldn't it be nice if it was as simple as select * from v$asynch_io; or something?
I do like your "watch" technique -- I'll file that away for future reference. But it doesn't help me much with an instance that's already running...
Mark Brinsmead wrote,on my timestamp of 29/07/2006 11:55 AM:
> But here's the half where you're wrong. (Or at least, not completely > "right".) Those hypothetical > "other" applications can just as easily be resposibly for the > *increases* in the slabinfo stats as > they are they would be for "non-zero" values. After all, those values > had to increase from zero > *some* *time*, didn't they. ;-)
sure, but the chance of any of them touching the count when you start an Oracle instance is remote. Remember that I said to watch the counter WHEN you start Oracle.
[...]
--
Cheers, -- Mark Brinsmead Staff DBA, The Pythian Group http://www.pythian.com/blogs