Memory consumption and swap utilization - Oracle

[satish]

Dear Erman,

We observed overall slowness in database a day before and the team is looking over the awr and ash reports.

we would like to know if memory has created any problem here.Below is the top ouput collected during the period.Looks like the system is swapping.Could you please correct us if we are wrong

[oracle@ABCOPOP admin]$ top
top - 14:13:29 up 140 days, 21:52, 4 users, load average: 5.43, 5.56, 5.78
Tasks: 476 total, 2 running, 474 sleeping, 0 stopped, 0 zombie
Cpu(s): 3.5%us, 0.8%sy, 0.0%ni, 95.7%id, 0.1%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 32930016k total, 32192836k used, 737180k free, 231516k buffers
Swap: 65535992k total, 3251028k used, 62284964k free, 30226744k cached

Thank you

[satish]

Dear Erman,

The actual issue was

Issue:

1)the listener was getting stuck and it is not accepting any connections.However we are not able to see any errors in alert log or listener log.

2)During the issue,we are unable to bring down the listener or even we not able to check the status of listener,the command is just hanging

We are able to connect as sysdba and run queries on database.

processes 2000
sessions 3000
sga_max_size 5G
sga_target_size 5G
pga_aggregate_target 1356M
sort_area_size 65536

There is no indication of memory problem in any logs

Every week,we are facing this and we are rebooting the server as we are not able to shut down the database

Thank you

[satish]

By the way,this is a standard edition with 11g release 1 version

[ErmanArslansOracleBlog]

The partial top output that you sent to me is not enough for dealing with this.

We need to see lots of things ->

At least we need to see the following in the first place;

/var/log/messages (for the problematic period)
Listener logs (for the problematic period)
alert log (for the problematic period)
"sar -q" outputs (for the problematic period)
"sar -W" outputs (for the problematic period)

[satish]

Thanks erman for the updates.

Unable to get the information for the problematic period.We will provide the information next time we face the issue