IMPAX 6.5.1 Server Knowledge Base home > Oracle Server home
When the Oracle Server is experiencing a heavy load, you can identify what processes are using the most resources. Use the Solaris prstat command to identify the top CPU processes on the Oracle Server and the oracle-whois command to provide more information on the processes. You can use this information to decide what processes to shut down or what other actions to take.
To check Oracle database CPU processes
At the command prompt, type prstat
A list of the processes using the most CPU is displayed.
To identify the Oracle processes you want more information on, type
oracle-whois pid (Solaris) or oracle-whois.bat pid (Windows)
where pid is the operating system process ID.
![]() | Note: You can pass multiple PID as arguments. For example, oracle-whois 9826 10381 27658 23483 |
Example
After listing the processes (type prstat at the terminal window) using the most CPU, type oracle-whois 9826 10381 27658 23483. The following information is displayed on-screen:
| OS-USER | USERNAME | SPID | MACHINE | PPID | SES_STAT | LAST_DB_CMG | PROGRAM |
| SYSTEM | MVF | 9826 | WORKGROUP\WELL | 105:119 | ACTIVE | SELECT | mvf_wellness_notifier.exe |
| SYSTEM | MVF | 10381 | WORKGROUP\WELL | 99:111 | ACTIVE | SELECT | MVF_WE~2.EXE |
| root | MVF | 27658 | as2 | 27984 | ACTIVE | INACTIVE | mvf-scp@as2 (TNS V1-V3) |
| SYSTEM | MVF | 23483 | WORKGROUP\WELL | 86:97 | ACTIVE | SELECT | javaserv.exe |
where:
| Column | Description |
|---|---|
| OS-USER | The operating system user name |
| USERNAME | The Oracle Server user name |
| SPID | The process ID on the Oracle Server |
| MACHINE | The machine that the client program which originated this session runs on |
| PPID | The process ID on the client |
| SES_STAT | Displays the session status |
| LAST_DB_CMG | The last type of command that the session issued |
| PROGRAM | The program that owns this session, for example, mvf-jdlt, mvf-scp |
See also
Determining available space for the database
Monitoring database statistics
Topic number: 8877 Applies to: IMPAX 6.5.1 Server Knowledge Base |