urgent---oracle dbsnmp process occupying RAM [message #126364] |
Mon, 04 July 2005 01:15 |
rram_k
Messages: 3 Registered: July 2005
|
Junior Member |
|
|
Hi,
We have oracle 9i running on solaris machines.
The dbsnmp process is occupying unusual amount RAM and swap. Please let us know whether I can kill that process...
Regards
ram
CPU states: 95.7% idle, 1.3% user, 2.8% kernel, 0.2% iowait, 0.0% swap
Memory: 8192M real, 130M free, 26G swap in use, 175M swap free
PID USERNAME LWP PRI NICE SIZE RES STATE TIME CPU COMMAND
9595 oracle 16 59 0 25G 6630M sleep 32:46 0.00% dbsnmp
24081 root 62 59 0 293M 164M sleep 10:18 0.05% .kjs
|
|
|
Re: urgent---oracle dbsnmp process occupying RAM [message #126384 is a reply to message #126364] |
Mon, 04 July 2005 03:00 |
shettyshetty
Messages: 18 Registered: June 2005 Location: Malaysia
|
Junior Member |
|
|
Hello Ram,
Which release of Oracle 9i are you using?
If it is Oracle 9.2.0.1, then it is due to Bug 2445663 (Small DBSNMP memory leak running jobs). This has been fixed in patchset 9.2.0.3 & above.
For the time begining, you can stop & restart the agent.
agentctl stop
agentctl start.
Hope this helps.
Sunil
|
|
|
Re: urgent---oracle dbsnmp process occupying RAM [message #126401 is a reply to message #126384] |
Mon, 04 July 2005 04:59 |
rram_k
Messages: 3 Registered: July 2005
|
Junior Member |
|
|
Hi Sunil,
Thanks for your reply. Actually I am running oracle in the failover mode. There are two nodes in the cluster and the oracle DB is running on node1. In node1, this agent is not running. The node2 is the failover node and there is no oracle DB running here. I just wanted to know whether stopping and starting the agent in node2 will affect the Oracle DB in node1. Waiting for your reply.
Regards
Ram
|
|
|
Re: urgent---oracle dbsnmp process occupying RAM [message #126404 is a reply to message #126364] |
Mon, 04 July 2005 05:12 |
shettyshetty
Messages: 18 Registered: June 2005 Location: Malaysia
|
Junior Member |
|
|
Hello Ram,
Well, usually agent is run in the node where the DB resides.If you are not running the agent in Node 1, it doesn't really make sense(Unless the person who configured has some reasons) to run it on the failover node. You can stop the agent & it will not have any impact on the primary node whatsoever.
-Sunil Shetty
|
|
|
|