Diagnosing 'broken' job

Question

Oracle 10.2.0.4.0 EE on HP-UX 11.23
OEM (dbcontrol) is reporting 1 "broken" job and 2 "failed" jobs. Googling on fixing 'broken' jobs. A select on dba_jobs returns two rows. Following suggestions found elsewhere (mostly Burleson's site) I tried
SQL> select job from dba_jobs where broken='Y';
       JOB
        50
        51
2 rows selected.
SQL> exec dbms_job.broken(JOB=>50, NEXT_DATE=>SYSDATE+1/1440, BROKEN=>FALSE);
PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.
SQL> select job from dba_jobs where broken='Y';
       JOB
        51
1 row selected.wait a couple of minutes ....
SQL> /
       JOB
        50
        51
2 rows selected.
SQL> exec dbms_job.run(50);
BEGIN dbms_job.run(50); END;
ERROR at line 1:
ORA-12011: execution of 1 jobs failed
ORA-06512: at "SYS.DBMS_IJOB", line 413
ORA-06512: at "SYS.DBMS_JOB", line 275
ORA-06512: at line 1
SQL>I keep running into dead ends on how to diagnose why the job is failing ... pointers appreciated.

Answer 1

sb92075 wrote:
I keep running into dead ends on how to diagnose why the job is failing ... pointers appreciated.manually invoke same procedure as JOB 50 does & see what happens
SQL> select what from dba_jobs where job=51;
WHAT
BEGIN /*Quest PPCM Bottleneck job */  quest_ppcm_bottleneck.collect_data; END;
1 row selected.
SQL> BEGIN /*Quest PPCM Bottleneck job */  quest_ppcm_bottleneck.collect_data; END;
  2  /
BEGIN /*Quest PPCM Bottleneck job */  quest_ppcm_bottleneck.collect_data; END;
ERROR at line 1:
ORA-06550: line 1, column 39:
PLS-00201: identifier 'QUEST_PPCM_BOTTLENECK.COLLECT_DATA' must be declared
ORA-06550: line 1, column 39:
PL/SQL: Statement ignoredAnd the package body for QUEST_PPCM_BOTTLENECK is wrapped, so I'm not able to see what it is -- at least I don't know that I can. But being it is a well used commercial package, I'd not expect something like the error shown.
FWIW, and should have pointed out in my original, this database was rebuilt from scratch -- used dbca to create a template from it, then create scripts from the template. Run the CREATE DATABASE and related scripts from dbca, then reload the application schemas from the nightly export.
We could delete and re-install Spotlight (the only Quest product installed there) but as it's not critical at this point, I'd rather work through the problem as a learning exercise.