Thanks!!
Darrell Landrum
Database Administrator
Zale Corporation
>>> [EMAIL PROTECTED] 03/14/03 12:44PM >>>
It takes 16 failures to mark the job as "broken".
Igor Neyman, OCP DBA
[EMAIL PROTECTED]
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sen
It takes 16 failures to mark the job as "broken".
Igor Neyman, OCP DBA
[EMAIL PROTECTED]
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Friday, March 14, 2003 11:24 AM
> Ben,
>
> If this problem has not been fixed, check something else.
> Run
Many thanks Jared,
Definitely I think this is only one away to resolve
my problem.
Have nice week end,
Ben
--- [EMAIL PROTECTED] wrote:
> You can't call a job every second via DBMS_JOB.
>
> I believe that at best the resolution is 1 minute.
>
> You could just open another session and run
>
You can't call a job every second via DBMS_JOB.
I believe that at best the resolution is 1 minute.
You could just open another session and run
something like this:
declare
fd varchar2(50) := '01/01/2010 00:00:00';
v_sql varchar2(200);
begin
loop
v_sql := 'alter system set fixed_da
Ben,
If this problem has not been fixed, check something else.
Run:
select job, what, broken, failures from dba_jobs;
I don't know how many, but after a certain number of failures, a job is marked as
broken and won't run automatically.
Darrell
>>> [EMAIL PROTECTED] 03/14/03 08:38AM >>>
Tha
Thanks Jacques,
Yes I did:
VARIABLE jobno number;
BEGIN
DBMS_JOB.SUBMIT(:jobno,
'fixed_date_proc.getSystemDate;',sysdate, 'sysdate',
true);
commit;
end;
/
Ben
--- Jacques Kilchoer <[EMAIL PROTECTED]>
wrote:
> After calling dbms_job.submit, did you issue a
> commit?
>
> > -Original Me
Thnks Michal for your input,
All seems right for me:
SQL> show parameter job
NAME TYPEVALUE
---
--
job_queue_interval integer 90
job_queue_processes integer
Hi,
1) check job_queue_processes and job_queue_interval parameters in your
init.ora file
2) have a commit after dbms_job.submit
3) if you want the procedure to be executed every second, then the next
date should be 'sysdate+1/86400' =>
dbms_job.submit(:job_num, 'myprocedure;',sysdate, 'sysdate+1
Title: RE: Fixed_date and dbms_job
After calling dbms_job.submit, did you issue a commit?
> -Original Message-
> From: Kader Ben [mailto:[EMAIL PROTECTED]]
>
> I'm simulating the date in future with fixed_date.
> I wrote procedure to be called every seconde t
