Oracle Java Memory Performance
It’s a good practice to monitor your system memory from time to time especially in Oracle Applications E-Business Suite. Today we will focus on how to monitor performance the Java memory used by Oracle Applications.
You can query for top Java memory usage using the Unix script as below.
Multiply the result figure from first column with 4096 and divide by 1024 to obtain the value in kB.
Java Memory Monitoring
$ UNIX95= ps -eo vsz,ruser,pid,args | sort -rn | grep java | grep applprod 182332 applprod 4908 /opt/java1.4/jre/bin/PA_RISC2.0/java -DCLIENT_PROCESSID=4908 22588 applprod 24976 /opt/java1.4/jre/bin/PA_RISC2.0/java -DCLIENT_PROCESSID=24976 22588 applprod 14141 /opt/java1.4/jre/bin/PA_RISC2.0/java -DCLIENT_PROCESSID=14141 14396 applprod 24975 /opt/java1.4/jre/bin/PA_RISC2.0/java -DCLIENT_PROCESSID=24975 14396 applprod 14140 /opt/java1.4/jre/bin/PA_RISC2.0/java -DCLIENT_PROCESSID=14140
The output of the top Java memory doesn’t provide any details on what is the session that utilize lots of memory from the system.
You can use the query below to check and see what is the session that is tight to the running Java memory process.
Oracle Java Process Session
SELECT s.STATUS "Status", s.TYPE "Type", s.username "DB_User", s.osuser "Client_User", s.server "Server", s.machine "Machine", s.module "Module", s.logon_time "Connect Time", s.process "Process", p.spid, p.pid, s.SID, s.audsid, SYSDATE - (s.last_call_et / 86400) "Last_Call" FROM v$session s, v$process p WHERE s.paddr = p.addr(+) AND s.process = <replace WITH Process ID FROM DCLIENT_PROCESSID>;
There are many ways of tuning the memory and we are still looking on the best practice on tuning Oracle Java memory such as tuning the memory heap size and using garbage collectors.
Related Posts
- Java Home In Oracle 11i
- Detect Oracle Memory Hunger Process
- How To Check Top Memory Usage In Unix
- Database Session Memory Usage
- Oracle Memory Allocation
PreviousNext» Speed Up Blog With Apache .htaccess
Leave a CommentJoin the over 2,000 people who get free and fresh knowledge as soon as it’s published.
We respect your email privacy.
We promise never to rent, sell or share information we collect because that would be a violation of everything we stand for.
Period.
January 21, 2010 7:54 pm
Set the FDMXHEAP in your environment file to control the memory heap growth.
#Control the growth of memory heap using FDMXHEAP by setting it to 500MB
FDMXHEAP=500000000
export FDMXHEAP
Rebounce your Concurrent Manager as well as your Apache after the change.
Previously I restart Apache periodically to release the memory heap in system and no longer need to do so after setting the FDMXHEAP.