High CPU utilization on Exadata compute node 

High CPU utilization on Exadata compute node.

Load Average 

Load average can be verified by using  uptime  and top commands. With -c option  by using  top command ,we will get %CPU also.
output of uptime:

exanode02: 18:30:01 up 340 days, 14:28, 0 users, load average: 11.46, 8.75, 8.37
top -c 
[orarom@exanode02 bin]$ top -c
top – 18:37:41 up 340 days, 14:36,  1 user,  load average: 9.65, 9.88, 9.11
Tasks: 6290 total,   7 running, 6283 sleeping,   0 stopped,   0 zombie
Cpu(s):  6.2%us,  1.7%sy,  0.1%ni, 91.8%id,  0.0%wa,  0.0%hi,  0.1%si,  0.0%st
Mem:  528851204k total, 454364596k used, 74486608k free,  4235948k buffers
Swap: 25165820k total,   229724k used, 24936096k free, 42778196k cached

   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND

 39931 orarom    20   0 15.0g    595m  12m S     450.2     0.1      6005:45
/opt/OracleHomes/agent_home/core/12.1.0.5.0/jdk/bin/java -Xmx356M -XX:MaxPermSize=96M -server
194931 root           30  10 13552    6940  496 D     93.0        0.0      0:11.50 bzip2 /opt/oracle.ExaWatcher/archive/Top.ExaWatcher/2018_06_20_17_33_58_TopExaWatcher_exanode02
Reason for High CPU :
 Based on above two commands ,
                    i)server is up and running since 340 days.
                    ii) Agent is running with orarom user  since 250.2 days and taking %CPU as 450.2
Actions to be taken:
Stop the agent and wait for sometime and restart the agent and monitor closely.
What is orarom on exadata?
orarom is a new user on oracle systems that will be created during the setup by Oracle.

See also