Hi Brian!
I saw this too last week! Investigation showed a very large I/O on a disks
containing one of the databases. As soon as I broke the database mirror
everything ran fine again. I then established the mirror again and the next
day I encountered the same problem! I'm now running a non-mirrored database
(ouch!) and I haven't had any performance problems since.
I haven't reported this to Tivoli because we will migrate to TSM 3.7
somewhere next month, but now I see the same problem there... However, we
will put a single database on an AIX mirrored volume.
Looks like a real bug to me!!! I'm running 3.1.2.50.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines