Re: Passing Arguments to Scheduler Chains

From: Uwe Küchler <>
Date: Tue, 21 Jun 2011 11:33:54 +0200 (CEST)
Message-ID: <>

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: And I also found a similar question with sample code on MOS (Doc ID 1272728.1).


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
> because this throws an ora-27475.
> Any ideas, anyone?
> I'm on, but this question was asked before for 10g and never
> answered:

Received on Tue Jun 21 2011 - 04:33:54 CDT

Original text of this message