Error On Auto Execute Of Job
Contents |
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! Oracle PostersOracle Books Oracle Scripts Ion Excel-DB Don Burleson Blog
error on auto execute of job 86250 ORA-12012 Auto Execute Error Tips Expert Oracle Database Tips by BurlesonOra-12012 Error On Auto Execute Of Job Sys . Dra_reevaluate_open_failures
Consulting February 11, 2015 Question: I am receiving the following error in my Alert log. But my job is not ora-12012 error on auto execute of job sysman . em_ecm_vcpu_job broken and there are no failures. Any idea what is going on and how I can resolve this? ORA-12012: error on auto execute of job 62 ORA-12005: may not schedule automatic refresh for times in the
Ora-12012 Error On Auto Execute Of Job Oracle_ocm . Mgmt_config_job_2_2
past dbms_refresh.refresh('"AAI"."A_REST"'); Broken = N Failure = 0 Interval = trunc(sysdate)+23/24 Last Date =10/21/2005 12:02:15 AM Next Date =10/21/2005 11:00:00 PM ORA-12012: error on auto execute of job 62 ORA-12005: may not schedule automatic refresh for times in the past How do I find out the cause of this ORA-12012 error and the accompanying ORA-12005 error? Answer: ORA-12012 error is a generic error and you need to look closer to find ora-12012 error on auto execute of job oracle_ocm . mgmt_config_job the real error code that indicates why the job failed. To diagnose any error, you start by using the oerr utility to display the ORA-12012 error: ORA-12012: Error on Auto Execute of Job Cause: An error was caught while doing an automatic execution of a job. Action: Look at the accompanying errors for details on why the execute failed. As is indicated by the utility, the required action is to look at the accompanying errors for details on why the execute failed. In this case, the accompanying error is: ORA-12005: may not schedule automatic refresh for times in the past. This means that there's something wrong with the part of your code dealing with the automatic refresh, specifically the interval. Your interval is set as follows: interval = trunc(sysdate)+23/24 The code you have written sets an interval where Oracle is trying to run the job at a time in the past, which it simply cannot do. So, change your interval to this: interval = trunc(sysdate+1)+23/24 And your Oracle job will run smooth as silk! An ORA-12012 error should come with an accompanying error that will basically tell you what you did wrong. Fix that, and assuming there are no other problems, your job should run just fine. ****************************** The BC Oracle forum h
x64 with Active Dataguard. The following error shows on a scheduled basis ORCL1: Sat Jan 18 23:00:06 2014 Errors in file /u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_j008_6097.trc: ORA-12012: error on auto execute of job "SYS"."BSLN_MAINTAIN_STATS_JOB" ORA-06502: PL/SQL: numeric or value error ORA-06512: at "DBSNMP.BSLN_INTERNAL",
Ora-12012 Error On Auto Execute Of Job 1
line 2073 ORA-06512: at line 1 Reason: The underlying table required as part of one
Ora-12012 Error On Auto Execute Of Job Oracle_ocm . Mgmt_config_job_2_1
of the schedule maintenance tasks has invalid values. The related table is DBSNMP.BSLN_BASELINES. After taking a look at the job log we ora-12012 error on auto execute of job sys . ora$at_ see the failed execution attempts: SQL> select log_date,status from dba_scheduler_job_run_details where job_name='BSLN_MAINTAIN_STATS_JOB'; LOG_DATE STATUS ------------------------------------- ------------------------------ 11-JAN-14 11.00.07.315077 PM -06:00 http://www.dba-oracle.com/t_ora_12012_error_on_autoexecute.htm FAILED 04-JAN-14 11.00.05.595559 PM -06:00 FAILED 18-JAN-14 11.00.06.554385 PM -06:00 FAILED 28-DEC-13 11.01.05.966337 PM -06:00 FAILED 22-JAN-14 03.36.50.995888 PM -06:00 FAILED 5 rows selected. FIX Procedure: Look for the values on the table, detect the invalid values and remove them. SQL> select * from DBSNMP.BSLN_BASELINES; DBID INSTANCE_NAME BASELINE_ID BSLN_GUID TI A STATUS http://hrivera99.blogspot.com/2014/01/ora-12012-error-on-auto-execute-of-job.html LAST_COMPUT ---------- ---------------- ----------- -------------------------------- -- - ---------------- ----------- 3038864366 orcl 0 0A03A0424F06F7E6B3841C6CC0999F7C NW N ACTIVE 131027:0000 3038864366 ORCL2 0 A396EEB2AB3A39AF477DC4A1AEE70CC9 ND Y ACTIVE 131228:2300 3038864366 ORCL1 0 176C36D62D62855075AD0BBD90B2DA30 ND Y ACTIVE 131228:2300 You must know exactly which row you're deleting, in my very particular case I know which rows do not make sense since this database was recently involved in a fail over scenario and the former name is still being held in the table. The corrupt row is removed with a simple DELETE command: SQL> DELETE FROM DBSNMP.BSLN_BASELINES WHERE INSTANCE_NAME ='orcl'; 1 row deleted. SQL> commit; Commit complete. Manually re-execute the job and check the execution log, it must show the job executed successfully. It takes a couple of minutes after execution to show the results in the log table. SQL> exec dbms_scheduler.run_job('BSLN_MAINTAIN_STATS_JOB',false); PL/SQL procedure successfully completed. The issue was fixed, validate it by querying he DBA_SCHEDULER_JOB_RUN_DETAILS view. SQL> select log_date,status from dba_scheduler_job_run_details where job_name='BSLN_MAINTAIN_STATS_JOB'; LOG_DATE
productResults.length + resourceResults.length > 0 ? 'See all Search Results' : 'Full site search'}} > > CA Support Online > Support by Product > Support by Product Getting this error: ORA-12012: error on auto execute of job 9 Document ID:TEC1134193 Last Modified Date:01/05/2016 {{active http://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.tec1134193.html ? 'Hide' : 'Show'}} Technical Document Details Products CA Business Service Insight http://www.nazmulhuda.info/ora-12012-error-on-auto-execute-of-job-sys-bsln_maintain_stats_job Components CA Business Service Insight:OBLCRE Symptoms: You start to get this error: ORA-12012: error on auto execute of job 9 ORA-02289: sequence does not exist ORA-06512: at "OBLICORE.PART_MNG_PKG", line 16 ORA-06512: at "OBLICORE.PART_MNG_PKG", line 440 ORA-02289: sequence does not exist ORA-01403: no data found Cause: It’s trying error on to run one of the scheduled jobs and the job is not created properly. Normally this gets created during the install as long as the Oracle job scheduling service is installed. It may be that they only added the service after the fact or something went wrong during the job creation. Resolution: You should be able to recreate error on auto it from the installation media (it’s a simple job that then reads a table for what to clear, but the job is always there). Run: Select * from user_jobs; To see the job. Please make sure: 1. The database package Part_Mng_Pkg is compiled. 2. The raw data job exists, scheduled and unbroken The job can be recognized by What= Part_Mng_Pkg.G_TABLE_NAME :='T_RAW_DATA';Part_Mng_Pkg.raw_data_purge; Additional Information: The Part_Mng_Pkg.sql can be found under the DVD: DVD:\SetupDB\InstallDB\Build_Schema\Packages Please help us improve! Will this information enable you to resolve your issue? Yes No Please tell us what we can do better. {{feedbackText.length ? feedbackText.length : '0'}}/255 {{status}} Not what you were looking for? Search Again> Product Information Support by Product> Product Documentation> Communities Join a Community> Education Find training by product> SHARE THIS {{link.title}} Copyright © 2016 CA. All rights reserved. {{link.title}} North America (English) Chat with CA Just give us some brief information and we'll connect you to the right CA Expert. Our hours of availability are 8AM - 5PM CST. All Fields Required First Name Last Name E
FunctionsPL/SQLORA ERRORBugsScriptsToolsMySQLLinuxOtherContact ORA-12012: error on auto execute of job "SYS"."BSLN_MAINTAIN_STATS_JOB" ORA-12012: error on auto execute of job "SYS"."BSLN_MAINTAIN_STATS_JOB" ORA-06550: line 1, column 807: PLS-00201: identifier 'DBSNMP.BSLN_INTERNAL' must be declared Cause: You might get this error when database is created using template from old database or by cloning from another database. Therefore, table DBSNMP.BSLN_BASELINES contains inconsistent information that is causing the job to fail. Solution: If you delete the inconsistent rows from table DBSNMP.BSLN_BASELINES it will fix the problem but you can fix this easiest way by following the below guidelines. SQL> select log_date,status from dba_scheduler_job_run_details where job_name='BSLN_MAINTAIN_STATS_JOB'; LOG_DATE STATUS --------------------------------------------------------------------------- ------------------------------ 13-AUG-14 09.45.36.831010 AM +02:00 FAILED 17-AUG-14 09.00.00.980275 AM +02:00 FAILED SQL> sqlplus / as sysdba -- Drop the DBSNMP user by executing catnsnmp.sql script. SQL> @$ORACLE_HOME/rdbms/admin/catnsnmp.sql -- Create the DBSNMP user by executing catsnmp.sql SQL> @$ORACLE_HOME/rdbms/admin/catsnmp.sql-- Re-execute the job SQL> exec dbms_scheduler.run_job('BSLN_MAINTAIN_STATS_JOB',false); PL/SQL procedure successfully completed. SQL> select log_date,status from dba_scheduler_job_run_details where job_name='BSLN_MAINTAIN_STATS_JOB'; LOG_DATE STATUS --------------------------------------------------------------------------- ------------------------------ 13-AUG-14 09.45.36.831010 AM +02:00 FAILED 17-AUG-14 09.00.00.980275 AM +02:00 FAILED 20-AUG-14 02.50.36.799841 PM