to Divan:

"Jobs" katoriji zapuskajutsja cherez OEM nje sovsjem to zhe samoje shto te "jobs", katoriji zapuskajut v baze cherez dbms_job.submit! Primer - sdelal job "run SQL script" v OEM, no v target database v dba_jobs on njepojavljajetsja, potomu shto za zapusk etogo job'a otvechajet OES, a nje sama baza.

V baze nado smotretj parametri:

JOB_QUEUE_PROCESSES dolzhen bitj > 0
JOB_QUEUE_INTERVAL ot 1 do 3600 (sekundi)

select * from dba_jobs

Nado smotretj njeuveljichivajetsja lji failures dlja job'a. Mozhet bitj njepraveljnij user ...

Paprobuj zapustjitj Job iz OEM, kogda Intelligent Agent njerabotajet.
Pustj njedumalji, shto ja tut fuflo govorju, maljenkij fragment iz OES concepts:

From job scheduling to job completion, the following steps occur:

1) From the Console Jobs pane, a job is scheduled against one or more targets of the same type that is made up of one or more tasks.

2) The Oracle Management Server stores the information and checks if the target node is up or down. If the node or its Intelligent Agent is down, the Oracle Management Server queues the job.

3) Once the node can be contacted, the Oracle Management Server sends the job information to the Intelligent Agent residing on the managed node. Jobs can be sent to multiple nodes concurrently.

4) The Intelligent Agent executes the job on schedule.

5)The Intelligent Agent returns any related job messages back to the Oracle Management Server for display in the appropriate consoles based on administrator access levels. If the Intelligent Agent cannot get in touch with the Oracle Management Server, it queues the messages.