Broken ORACLE_OCM jobs

I was messing around with the Logging Level setting in the scheduler and I appear to have broken something, but I'm not sure what. The jobs that are broken are the two owned by ORACLE_OCM, MGMT_CONFIG_JOB and MGMT_STATS_CONFIG_JOB. All I did was change and restore the Logging Level using OEM for these and a number of other scheduler jobs. Now these two jobs are failing with "ORA-06576: not a valid function or procedure name".
They call the ORACLE_OCM.MGMT_CONFIG package, it's still there. If I compare the ORACLE_OCM schema with an instance where the jobs are not failing they come up as identical.
I realize I could just re-run the OCM installation, but that seems silly. All I did was touch the job definitions, this looks like something simple and stupid, I'm just not seeing it.
Does anyone know what I'm not seeing?

In the end I did re-run the OCM installation. It just took a moment and it fixed the problem. I still don't know what touching the jobs did, but whatever it was it was easy to fix.

Similar Messages

Diagnosing 'broken' job

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.

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.

How to cancell all scheduled jobs

Is there a Command line (or) any other option to kill all scheduled jobs, because when cloning of data happens from Production to other testing instance, scheduled jobs will still be running and are consuming space.
We could use admin screen , killing one by one is taking lot of time.
Appreciate your input
Thanks

Hi user10596151,
you can try the following:
To disable all of the scheduled workbooks immediately, use the following PL/SQL block. The PL/SQL block should be run as a privileged user (such as 'system').
Declare
cursor c1 is
select job from all_jobs where what like '%EUL5%';
begin
for i in c1 loop
dbms_job.broken(i.job,true);
end loop;
end;
Note: For Discoverer 4 replace EUL5 with EUL4

DBMS_JOB.BROKEN

Hi,
Is it possible that broken jobs (Using DBMS_JOB) executes? I have broken a job for statspack statistics collection using command
execute dbms_job.broken(42,true); and then I checked user_jobs. Broken column was Y that time but still its executed and trying to execute that job.
Can you tell me how this has happened?
Malay

Normally a broken flag is set to Y by Oracle after 16 unsuccessful attempts.
The attempts will be made in a interval which is multiples of 2 like, 2, 4, 6,....
and once it reaches the 16th attempt and still fails it sets the flag to Y.
Now you have to manually run the job, and set the broken flag to N.
Did you commit the operation after dbms_job.broken(42,true) ?

Monitor failed jobs

Hi
Is there any difference between Failed Job Count and Broken Job Count ?
Thanks

Yes please see the definition below.
Broken Job Count The Oracle Server job queue is a database table that stores information about local jobs such as the PL/SQL call to execute for a job such as when to run a job. Database replication is also managed by using the Oracle job queue mechanism using jobs to push deferred transactions to remote master sites, to purge applied transactions from the deferred transaction queue or to refresh snapshot refresh groups.
A job can be broken in two ways:
Oracle has failed to successfully execute the job after sixteen attempts. The job has been explicitly marked as broken by using the procedure DBMS_ JOB.BROKEN
This metric checks for broken DBMS jobs. A critical alert is generated if the number of broken jobs exceeds the value specified by the threshold argument.
Failed Job Count The Oracle Server job queue is a database table that stores information about local jobs such as the PL/SQL call to execute for a job such as when to run a job. Database replication is also managed by using the Oracle job queue mechanism using jobs to push deferred transactions to remote master sites, to purge applied transactions from the deferred transaction queue or to refresh snapshot refresh groups.
If a job returns an error while Oracle is attempting to execute it, the job fails. Oracle repeatedly tries to execute the job doubling the interval of each attempt. If the job fails sixteen times, Oracle automatically marks the job as broken and no longer tries to execute it.
This metric checks for failed DBMS jobs. An alert is generated if the number of failed job exceeds the value specified by the threshold argument.

Problem in Materialized Views

Hi,
I have two servers one is remote database (it resides in public ip) and another one is local database.
I have created Materialized view in Local System to replicate the data from remote system to Local System, Local system Internally creates Jobs , because of this replication Local System continuously ping the remote system, if any point of time network goes down, Local System unable to ping the remote system , at that time it gives Request timed out, due to this Reason jobs were going to fail. Is there any possibility to start these jobs automatically without manual intervention.
Can you please suggest to go forward this.
Regards,
Paparao

you may have another dbms_job or unix cron job to control and enable some of or all of broken jobs easily? A sample code may be like this one;
DECLARE
CURSOR C1 IS SELECT * from USER_JOBS
                          WHERE THIS_SEC IS NULL AND BROKEN='Y';
ND DATE;
stmt VARCHAR2(200);
BEGIN
FOR C1R IN C1 LOOP
    stmt := 'SELECT '||C1R.INTERVAL||' FROM DUAL';
    EXECUTE IMMEDIATE stmt INTO ND;
    DBMS_OUTPUT.PUT_LINE(C1R.JOB||'-'||TO_CHAR(ND, 'DD/MM/YYYY HH24:MI:SS'));
    DBMS_JOB.BROKEN(C1R.JOB, FALSE, ND);
END LOOP;
END;
/

How to get a materialized view get to refresh itself after the job is "broken"

we created a materialized view sometime ago with the following statement:
create materialized view SXV_PUB_EMPLOYEE_CERT_ALL_M
refresh complete on demand
start with to_date('30-08-2009 04:00:00', 'dd-mm-yyyy hh24:mi:ss') next trunc(sysdate) + (28/24)
as
select sxv_emp_cert_all.*
from sxv_employee_certification_all sxv_emp_cert_all;
this week we found out it had not been refresh for about a month
In dba_jobs the column broken was 'Y', next_date time something like 01-01-4000 and failures 16
when I ran it manually by executing
BEGIN DBMS_MVIEW.REFRESH('SXV_PUB_EMPLOYEE_CERT_ALL_M', 'C'); END;
I found that one of the columns was too small (probably a columns of one of the underlying tables had been extended since the creation of the materialized view)
After fixing this I ussied yesterday (on 29-8-2013) the statement :
alter materialized view SXV_PUB_EMPLOYEE_CERT_ALL_M
refresh complete on demand
start with to_date('30-08-2009 04:00:00', 'dd-mm-yyyy hh24:mi:ss') next trunc(sysdate) + (28/24)
after this the table dba_jobs showed me 30-08-2013 04:00:00 as next date
I was expecting it to run this night at 04:00, but it didn't
the last_date column value was still from about a month ago, the column broken still shows 'Y'
and the next date 30-08-2013 04:00:00 (while it should been set to 31-08-2013 01:00:00
Rrunning
BEGIN DBMS_MVIEW.REFRESH('SXV_PUB_EMPLOYEE_CERT_ALL_M', 'C'); END;
gave no errors this time
and in User_Mview_Analysis the last_refresh_date column showed the date/time I had executed it
Any idea how to get the job "unbroken" again so that the view refreshes itself every night?
the database is Oracle Database 10g Release 10.2.0.4.0
regards,
Remco

thanx for all your helpful and correct answers . but eventually I found it myself
exec dbms_job.broken(<jobnumber>, false);

Broken jobs and failed jobs

hi all..
please tell me difference between broken jobs and failed jobs
thanks

Please refer documentation .
Failed Jobs
If a job has the status of FAILED in the job table, it was scheduled to run once but the execution has failed. If the job was specified as restartable, all retries have failed.
If a job fails in the middle of execution, only the last transaction of that job is rolled back. If your job executes multiple transactions, you need to be careful about setting restartable to TRUE. You can query failed jobs by querying the SCHEDULERJOB_RUN_DETAILS views.
Broken Jobs
A broken job is one that has exceeded a certain number of failures. This number is set in max_failures, and can be altered. In the case of a broken job, the entire job is broken, and it will not be run until it has been fixed. For debugging and testing, you can use the RUN_JOB procedure.
You can query broken jobs by querying the SCHEDULERJOBS and SCHEDULERJOB_LOG views.
Regards
Renjith Madhavan

Query regarding broken jobs

I am using Oracle 10.2.0.2 on Solaris
There are a number of job which run continously every few seconds during deployment and a few of them fail over.
I am facing lock issues in the database so I was wondering if the new sessions created by the DBMS_JOB package would be dropped automatically if the jobs fail and also whether the locks which were used by the jobs would be automatically released?

Hi,
any idea about how to fix it ?Most shops monitor for broken jobs, and incoke scripts to repair them automatically: http://www.dba-oracle.com/t_verifying_auditing_replication.htm
Hope this answers your question . . .
Donald K. Burleson
Oracle Press author
Author of "Oracle Tuning: The Definitive Reference":
http://www.dba-oracle.com/bp/s_oracle_tuning_book.htm

How can a broken job "re-enable" itself?

I have noticed that a "broken" job will have re-started itself when I check it the next day. How is this possible?
No one in my group deals with this job, except for me.
There is no other job in any other schema that would enable this job.
I have used both TOAD and the DBMS_JOB package to disable this job. Still, this job refuses to stay broken. Any ideas?

What version of Oracle?
From the 9.2 Administrators Guide >> If a job returns an error while Oracle is attempting to execute it, Oracle tries to execute it again. The first attempt is made after one minute, the second attempt after two minutes, the third after four minutes, and so on, with the interval doubling between each attempt. If the job fails 16 times, Oracle automatically marks the job as broken and no longer tries to execute it. However, between attempts, you have the opportunity to correct the problem that is preventing the job from running. This will not disturb the retry cycle, and Oracle will eventually attempt to run the job again. <<
How is the job being ran? By the next value or is the job being demanded in by another process so that the next value in dba_jobs for this job is not really used?
HTH -- Mark D Powell --

Unable to drop a broken job

Hi Friends,
i want to drop a broken job but it is taking long time why?
i am using below syntax:
begin
dbms_job.broken(job=> 345,FALSE);
commit;
end;
Thanx.

Hi,
you can drop the job and recreate it. To drop the job :-
BEGIN
DBMS_SCHEDULER.drop_job (job_name => 'job_name);
END;To create a job
BEGIN
DBMS_SCHEDULER.create_job (
    job_name        => 'job_name',
    job_type        => 'PLSQL_BLOCK',
    job_action      => 'BEGIN your_procedure; END;',
    start_date      => SYSTIMESTAMP,
    repeat_interval => 'freq=hourly; byminute=0; bysecond=0;',
    end_date        => NULL,
    enabled         => TRUE,
    comments        => 'any_comment_you_want.');
END;
/

Last moment a job was broken.

Hello,
first of all sorry for the triviality of this question, it's my first one and i'm quite new to the Oracle world.
I've searched in the forums and also a bit on the web trying to answer to this question:
Is there a way to know the last moment a job was marked as broken, therefore know the moment (date and time) when the status of that job was restored to "not broken"?
Maybe i was searching with the wrong keywords because, as you can see, my english is not that good or maybe the solution is so obvious that nobody ever asked for it..
Thanks in advance,
Matteo

The LAST_DATE in DBA|ALL|USER_JOBS will show the date the job was last executed successfully. The first attempt to execute a failed job will occur after one minute, the second attempt after two minutes, the third attemp after four minutes, etc. The job is marked as broken after the job fails 16 times. From this, you can calculate the time the job broke from the LAST_DATE the job ran successfully.

Dbms_job: question about broken jobs

Hi.
I have defined the following job:
VARIABLE jobno NUMBER
BEGIN
DBMS_JOB.SUBMIT (:jobno,'test_proc;',SYSDATE,'SYSDATE + 5/86400');
COMMIT;
END;
When the procedure is invalid the job queue tries to start it 16 times and marks the job as broken.
Is there an option that dbms_job does an automatic recompile of the procedure after the job has the broken status?
Thanks
Markus

you could do a two-step job to compile the proc, then execute it.
VARIABLE jobno NUMBER
BEGIN
DBMS_JOB.SUBMIT (:jobno,'BEGIN
ALTER PROCEDURE test_proc COMPILE;
test_proc;
END',SYSDATE,'SYSDATE + 5/86400');
COMMIT;
END;

Hi Job is broken

Job is broken ,Now we need to disable or reexecute!!
Please ans any one

1
The xxxx_JOB is marked as BROKEN.
if we can disable or re_execute it
Edited by: lllllllll on May 31, 2011 11:04 AM
Edited by: lllllllll on May 31, 2011 11:20 AM
Edited by: lllllllll on May 31, 2011 2:57 PM

Broken clean up job

Hello,
recently we had a severe problem at our site. All our application
components (of all applications) were unavailable.
Analysis of this problem revealed:
1. One of the live application components (a form) was edited.
Saving the form took a lot of time (It caused the browser to
time-out).
2. traces in udump and bdump showed deadlocks
3. database was very active with deletes on WWA_MODULE_SESSIONS$,
the delete action took about a hour
4. table WWCTX_SSO_SESSION$ has a lot of active sessions, most of
them are weeks, even months old.
A post in this forum:
http://forums.oracle.com/forums/message.jsp?id=475615 showed the
cleanup job was broken in portal 3.0.6.6.5 (which is the version
I use).
Therefor session information in WWA_MODULE_SESSIONS$ isn't
regularly cleaned.
The link mentioned above shows a fixed version of the cleanup
job.
Some questions:
- did this fix made it to a formal (and thus an Oracle supported)
patch ?
- did anyone tried the change mentioned in the link?
- what will happen when I apply the change and run the job on a
site with > 70,000 sessions to be cleaned?
- What can I do to prevent application A to stop working when I'm
editing application B?
Thanks in advance,
Ton

Ton,
Yes, the session cleanup job is fixed in 3.0.9 but broken in
previous versions. Please file a bug on this issue to get a
backport to 3.0.6.6.5 if you need it.
Thanks -
PE

Broken ORACLE_OCM jobs

Similar Messages

Maybe you are looking for