Jobs with running status in OEM while it was already finished

Question

Hi
We have rebooted our server and all the jobs which are suppose to run some scripts in the server are showing running state for more than 16hours now! checking the scripts logs it was successfully executed and finished. When trying to delete the running jobs and schedule a new one it refuses to stop (although its not even running in reality). What can we do to clear this running status and let oem to schedule new ones? or how can we resolve this situation?
We are running Enterprise manager 10g
Swaid

Answer 1

Hi Jozsef,
I've tried to follow the instructions in that Metalink note and the job seems to be deleted from mgmt_job table as well as the executions for that job in mgmt_job_execution; but still everything is hanging and when i checked in the EM page it still shows the job in running state! how can I clean it? and why is it hanging in the first place?
I've looked into the agent trace and its not getting updated since the problem has started and here is a bit of the last messages we have in the trace:
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = Host, value = snmsmaster:3938
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = Connection, value = Keep-Alive, TE
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = TE, value = trailers, deflate, gzip, compress
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = User-Agent, value = RPT-HTTPClient/0.3-3
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = Accept-Encoding, value = gzip, x-gzip, compress, x-compress
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = Content-type, value = application/octet-stream
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = Content-length, value = 593
2009-04-17 12:05:09 Thread-2413 ERROR http: --- Error context dump end for incoming request ---
The emoms trace is getting updated with some repeated error messages that looks like below:
2009-04-18 15:56:57,114 [HealthMonitor] ERROR em.jobs pingPastDue.604 - Job step continuing
2009-04-18 15:57:13,362 [HealthMonitor] ERROR emd.main run.291 - HealthMonitor : Found errant task : TaskRegn:ID3440,Callback:class oracle.sysman.emdrep.jobs.JobWorker,Iterative:true,Duration:900,DueTime:1240059433359
2009-04-18 15:57:13,363 [HealthMonitor] ERROR em.jobs pingPastDue.602 - Entry - 15 Minute timeout error for jobstep:Stepname: Command
Commandname: remoteOp
Commandtype: Short-Running
StepId: 97914
jobIdStr: 679733b18b7a5698e04400144fa10220
executionIdStr: 67bd0ff86c9b4268e04400144fa10220
iterateParam: null
iterateParamIndex: -1
Swaid