Re: Passing Arguments to Scheduler Chains
- From: Uwe Küchler <uwe@xxxxxxxxxxxx>
- To: "oracle-l" <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 21 Jun 2011 11:33:54 +0200 (CEST)
Well, to finally answer myself (hoping this might be useful to someone else):
There is no simple way to pass arguments to steps in a chain like there is
for stand-alone jobs.
What can be passed to chain steps though, is job metadata like "job_name"
and "job_subname", which uniquely identify a job. Thus, one could create a
table containing this metadata as the primary key and the arguments as
additional columns.
This was discussed on OTN here:
http://forums.oracle.com/forums/message.jspa?messageID=9664831#9664831
And I also found a similar question with sample code on MOS (Doc ID
1272728.1).
Cheers,
Uwe
Am Mi, 15.06.2011, 19:58, schrieb Uwe Küchler:
> Dear oracle-l'ers,
>
> I am stuck in chains here... ;-)
>
> What already works is calling a program from a job, passing an argument to
> the program. So far, so good.
> What I'm *trying* to do is to run a Scheduler Chain, where one of its
> steps start the said program.
> Now, when I create a job to run the chain, I cannot add an argument value
> anymore with
>
> DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE
>
> because this throws an ora-27475.
> Any ideas, anyone?
>
> I'm on 11.2.0.2, but this question was asked before for 10g and never
> answered:
> //www.freelists.org/post/oracle-l/parametrized-programs-in-chains-in-10g,2
--
//www.freelists.org/webpage/oracle-l
Other related posts:
