Wednesday, December 12, 2007

Enterprise Manager

We had a problem using OEM 10g. During the day a database proces (ora_j001) was consuming 100% cpu. Because of this OEM coud not be reached, oms down. Looking for a solution, I ran into the job_queue_processes database parameter. This parameter was set to 10 in our database. I searched the net and could only find out that the value of this parameter should be > 0, if you want to use OEM. Prefered value is 10 (our original value...), but it looks like a value of 10 leads to the 100 % cpu problem.
I changed the job_queue_processes parameter to 2, also changed the aq_tm_processes parameter to 1. The OEM database seems to be more stable, but I don't know if everthing still works in OEM....
Has anyone got any experience with this ??

1 comment:

Anonymous said...

Did you even solved the problem?