Hardware - big Sun Solaris 2.6 with EMC drives. 20+ processors.
Veritas. Hardware under lock and key at undisclosed location with
guards and security with those little red laser beams to detect people
getting too close. Or so I've heard. <g>
Problem - High wio. Nobody seems to know why and no one has the time
to look for the source of the problem. Oracle is probably the
culprit, but which database and which tables aren't known. DBA too
busy or doesn't know how to look at the problem.
Me - Access to the machine (telnet) trying to find the source of the
problem. I have regular user privies.
iostat -x gives me numbers like this - and there's a whole lot more
(pages and pages)
sd168 0.2 0.2 7.4 1.4 0.0 0.0 13.0 0 0
sd169 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0
sd170 3.9 0.1 63.2 1.1 0.0 0.0 3.6 0 1
sd171 6.7 0.6 101.1 5.3 0.0 0.0 3.6 0 2
sd172 6.8 0.2 102.0 1.8 0.0 0.0 3.6 0 2
sd173 6.8 0.1 102.5 1.5 0.0 0.0 3.5 0 2
sd174 6.7 0.1 101.8 1.4 0.0 0.0 3.6 0 2
For those devices being used, I'd like to find out which tables are
causing problems. This gives me sd devices which I assume are created
by Veritas. I can't map them back to the mounted file system.
With Oracle, I have table information -
/DB42/PROJ/ORACLE/tab00/PROJ_tab01.dbf is on
So my goal is to find out that if the disk activity is on
/dev/vx/dsk/proj-table/vol01, I can narrow down the activity to a set
of tables, but I only have the device info from iostat.
What I want to know is if I see that device sd174 has a lot of
traffic, I want to know which database table(s) are getting the
traffic. I want to avoid Oracle stats because I want disk activity
and I think the Oracle stats may not reflect disk activity if the
tables are cached. Besides, I don't have DBA rights.
Is there a way to convert between the devices reported by iostat and
find out where they are in the filesystem so I can figure out what's
causing all the io activity?