HP-UX

About your swap configuration:

Code:

TYPE      AVAIL    USED    FREE  USED   LIMIT RESERVE  PRI  NAME
dev       16384       0   16384    0%       0       -    1  /dev/vg00/lvol2
dev       30016       0   30016    0%       0       -    1  /dev/vg00/secswap

Since we dont know what external storage you use (if its the case...), I will figure out that your swap devices were not dreated at the same time and are here to correct memory access trouble of the beginning.
What will happen if you were to use the swap now? It will take the biggest first...
The impact? Your biggest is huge with only one access (unless its a multidisk striped device...) and two devices on the same root disks is not a good idea...
About CPU, Methyl and I have same way of seeing things: Not knowing what is running at what moment and for how long, you CANNOT diagnose what you have as an issue, Im tempted to say your thresholds are badly set...
I never had any serious trouble with the HP servers I managed at the time for I knew what was running on them and could ( and NOT a software ) see just by leaving glance running and looking time to time if things where normal or not... some strong calculations of stats can take 100%CPU during days (Yes! days...) a RDBMS transaction lasting hours is very suspicious but only the DBA can tell if normal or not
One classical issue figure is the box that "freezes" periodically with 100% CPU and I/O...

Your kernel has some huge values for Semaphores and Shared Memory, but only 5% of memory allocated to disc buffers (suggesting that your database engine is doing most of the disc buffering). What Database Engine are your running?

Assuming that your Nimsoft monitoring package can't tell you what you want to know, visually monitoring with HP_UX Glance at the time that the suspect application is running should help spot an abnormal process with view to more detailed monitoring with database statistics (assuming that you have a mainstream database engine).

Looking at the Nimsoft website (I don't know the product myself) I see that it has a dashboard for "Processor Queue". This is the most important figure in the context of CPU usage.