Ora-23319

[steeve123]

onnected to Oracle8i Enterprise Edition Release 8.1.7.4.1
Connected as backup


SQL>
SQL>
SQL>
SQL> declare
2 l_job number := null;
3 begin
4 sys.dbms_job.submit(job => l_job,
5 what => 'begin PROC_BEGIN_BACKUP; end;',
6 next_date => sysdate + 1,
7 interval => '(trunc(SYSDATE))+1 +(22/ 24)');
8 commit;
9 end;
10 /

declare
l_job number := null;
begin
sys.dbms_job.submit(job => l_job,
what => 'begin PROC_BEGIN_BACKUP; end;',
next_date => sysdate + 1,
interval => '(trunc(SYSDATE))+1 +(22/ 24)');
commit;
end;

ORA-23319: parameter value "(trunc(SYSDATE))+1 +(22/ 24)" is not appropriate
ORA-06512: at "SYS.DBMS_JOB", line 57
ORA-06512: at "SYS.DBMS_JOB", line 129
ORA-06512: at line 4

SQL>



This work on 15 of my database except this one.
Any idea why?

[chduarte]

Don't you have any parameter for this PROC_BEGIN_BACKUP procedure? Maybe is missing a double single quotes for the parameters.

[steeve123]

The procedure exist, the problem is with the interval i put. It works everywhere, we have that thing running on our database since 3 years.

All on the sudden i get those error in my alert file:


Tue Jan 02 10:55:23 2007
Errors in file D:\oracle\DATABASE\admin\larry\bdump\larrySNP0.TRC:
ORA-00604: error occurred at recursive SQL level 1
ORA-00942: table or view does not exist
ORA-12012: error on auto execute of job 2
ORA-00942: table or view does not exist

Tue Jan 02 10:55:26 2007
Errors in file D:\oracle\DATABASE\admin\larry\bdump\larrySNP5.TRC:
ORA-12012: error on auto execute of job 2
ORA-00942: table or view does not exist





So i dropped the job. i dont have those ora in my alert file anymore.

But when i want to re-create the job. It does not work.

The procedure is not the problem. i can run it manualy with no prob.

[chduarte]

Actually I ran this select (trunc(SYSDATE))+1 +(22/ 24) from dual and worked fine also.

Maybe enable a trace in your session may help.

[steeve123]

i did select from dual;

and the dual table those not exist in my schema, very weird.

so i connected with the sys and did the following:

create public synonym dual for dual;


problem solved. Thanks

[Bore]

Well, the database seems to have problems with the data dictionary
You probably should ask the sys to rerun catalog.sql and catproc.sql