truss

I'm a DBA so no abuse please! I've for 5 Oracle Forms processes that are spinning and am trying to find out if they're doing anything:
Running HPUX 11.11

CPU TTY  PID USERNAME PRI NI   SIZE    RES STATE    TIME %WCPU  %CPU COMMAND
 9   ?  2735 oracle   241 20 24228K 16668K run   2607:29 84.92 84.78 f60webm
 4   ? 15925 oracle   241 20 24228K 16636K run   2664:49 84.43 84.28 f60webm
11   ? 16088 oracle   241 20 26676K 19116K run   2602:14 82.92 82.77 f60webm
 8   ?   726 oracle   241 20 24228K 16636K run   2432:42 79.87 79.73 f60webm
10   ? 17403 oracle   241 20 26676K 20016K run   2616:34 71.73 71.61 f60webm

I've run tusc -p against them and get the following from all the processes:

$ tusc -p 15925
( Attached to process 15925 ("f60webm webfile=5,2408,PID387") [32-bit] )
[15925] In user-mode ................................................................................... [running]

When I run tusc against some other Oracle forms processes I can see they are sleeping, then waking up and doing something:

[27795] read(4, 0x4009ef98, 6000) ................................................................. [sleeping]
[27795] read(4, "c4e89da1h 1f~ 11", 6000) ......................................................... = 8
[27795] setitimer(ITIMER_REAL, 0x680f4374, NULL) .................................................. = 0
[27795] setitimer(ITIMER_REAL, 0x680f4188, NULL) .................................................. = 0
[27795] write(4, "K 05", 2) ....................................................................... = 2
[27795] setitimer(ITIMER_REAL, 0x680f4188, NULL) .................................................. = 0
[27795] setitimer(ITIMER_REAL, 0x680f4374, NULL) .................................................. = 0
[27795] read(4, 0x4009ef98, 6000) ................................................................. [sleeping]

I guess my question is - can I kill the 5 spinning processes as they dont look like they're doing anything.

Thanks,
Fraze

Something is really wrong with those Forms processes.
Running in user mode means they are using cpu to execute user mode code - not making any system calls. They're stuck in a loop.

Thanks Jim - think its time for a kill!