Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.misc -> Re: We can only schedule one job to run with Oracle 10g?
antonyliu2002_at_yahoo.com wrote:
> Mark D Powell wrote:
> > antonyliu2002_at_yahoo.com wrote:
> > > I have 2 questions concerning Oracle scheduler.
> > >
> > > 1. I was attempting to schedule multiple jobs to run from midnight to
> > > 7AM each day, but it looks like if I create a new job, any other
> > > scheduled job will be automatically disabled.
> > >
> > > Does this mean that we can only schedule one job at to run at a time?
> > >
> > > 2. Then I tried combining these separate jobs into one, but only to
> > > find that Oracle keeps complaining about a string being too long:
> > >
> > > SQL Error
> > >
> > > Failed to commit: ORA-16612: string value too long for attribute
> > > "job_action" ORA-06512: at "SYS.DBMS_ISCHED", line 814 ORA-06512: at
> > > "SYS.DBMS_SCHEDULER", line 1209 ORA-06512: at line 3
> > >
> > > What's the reason?
> >
> > The first message implies that you have an error in your attribute
> > list. How are you attempting to schedule the job, manually or via one
> > of the tools: dbconsole?.
> >
> > If manualy, how about posting the command in use to give someone
> > something to look at?
> >
> > If via a tool, what tool from which screen? Can you perform the same
> > task manually? What happens?
> >
> > HTH -- Mark D Powell --
>
> Thanks Mark.
>
> I forgot to mention that I was attempting to do that through Oracle Web
> service by logging into the DBA account from localhost:5500/em
>
> And then select administration, under scheduler, select jobs and then
> hit create, and then copy-paste the SQl script.
>
> You have an idea now?
>
> Thanks.
How about posting the paste? Doesn't the screen allow you to schedule a task by filling in blanks and marking check boxes? Unfortunately my 10g system had to be reused and I do not have it back yet so I cannot bring up the tool.
Have you tried to just use dbms_scheduler.create_job via SQL*Plus?
![]() |
![]() |