Shulou(Shulou.com)05/31 Report--

The purpose of this article is to share with you what to do if there are ORA-12005 errors in oracle. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

The solution of Oracle Job ORA-12005 error

-an error message in the warning log was found in the two databases at 23:00 every night:

ORACLE_HOME = / oracle/oracle/product/10.2.0/db_2

System name: HP-UX

Node name: crm2db1

Release: B.11.31

Version: U

Machine: ia64

Instance name: tjcrm2

Redo thread mounted by this instance: 1

Oracle process number: 5104

Unix process pid: 16600, image: oracle@crm2db1 (J002)

* SERVICE NAME: (SYS$USERS) 2013-09-21 230015 01.532

* SESSION ID: (4803.7857) 2013-09-21 230015 01.532

* 2013-09-21 2300 purl 01.532

ORA-12012: error in automatic execution of job 2289

ORA-12005: cannot schedule automatic refresh of past time

-View related job

Select job,log_user,schema_user,what,LAST_DATE,LAST_SEC,THIS_DATE,THIS_SEC,NEXT_DATE,NEXT_SEC,INTERVAL from dba_jobs where job=2289

JOB LOG_USER SCHEMA_USER WHAT LAST_DATE LAST_SEC THIS_DATE THIS_SEC NEXT_DATE NEXT_SEC INTERVAL

-

2289 INST INST begin 22-SEP-13 00:02:12 22-SEP-13 23:00:00 TRUNC (SYSDATE + 1)-1 Universe 24

DELETE_KEY_INFO

End

It was found that interval was TRUNC (SYSDATE + 1)-1 Compact 24. In the view all_jobs, the following meanings are:

(a) the completion time of the successful implementation of LAST_DATE:Date on which this job last successfully executed--job

(B) LAST_SEC:Same as LAST_DATE. Start time of the last successful execution of This is when the last successful execution started.-- ~

(C) THIS_DATE:Date that this job started executing (usually null if not executing)-this field is blank when no job is executing. If there is a job running, this time is the start execution time of the job.

(d) THIS_SEC:Same as THIS_DATE. This is when the last successful execution started.

(e) the next execution time of NEXT_DATE:Date that this job will next be executed--job.

(F) NEXT_SEC:Same as NEXT_DATE. This is when the last successful execution started .

(G) INTERVAL:A date function, evaluated at the start of execution, becomes next NEXT_DATE

-cause analysis:

When job is executed, it is 21-SEP-13 23:00:00, so it is planned that the next execution time is trunc (21-SEP-13 23:00:00 + 1)-1 21-SEP-13 24 = or equal to 21-SEP-13 23:00:00, but after job execution, it is already 22-SEP-13 00:02:12, when the database is

Found that the next execution time is less than the current time. So report the wrong message. But job has been successfully implemented.

-solution:

Modify the INTERVAL so that the next execution is longer than the time after the current execution.

EXEC dbms_ijob.interval (job,interval)

Exec dbms_ijob.interval (2289 retrunc (SYSDATE + 1) + 23max 24'); = > when executing job under other users under sys, use dbms_ijob

Commit

Exec dbms_ijob.next_date (2289 memorials date) ('2013-09-23 2300 purge 00mm hh34:mi:ss'))

Commit

Thank you for reading! This is the end of the article on "what to do if there are ORA-12005 errors in oracle". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.