Sorry SlimDave for taking the wind out of your frustration thread but mine has reached a new level.

Next Oracle support told me to run a HANGANALYZE. I told them, the database is not hung anymore because I killed the processes and the swap freed up and the database runs fine. I also told them that when the agent is started, a trace file in network/trace is continually being written to. Meanwhile, the ironic part is that OMS is communicating with the agent just fine until memory and swap gets hosed.

Not knowing about HANGANALYZE, i asked does this thing work when the dB is not hung (I killed the I-agent). Oracle support answered:


Hi Frank,
No HANGANALYZE doesn't work when you are not seeing the problem. I thought you were still seeing frequent hanging.

Kindest Regards,
Tiffany


c.s. never addressed why the agent process chews up memory (leak) and the status of the tar is "Waiting on Customer".

Holy Sheee-it!!!

jodie...In order to really stop the agent, I too have to kill the unix processeses (2 of 'em).