rjamya wrote: > http://download-east.oracle.com/docs/cd/B14117_01/appdev.101/b10802/d_sched.htm#1010949 It works of course, but only for a job running program and not for a chain of programs Usage of procedure DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE ( job_name =>'J_EXP_IMP_TEST', -- running EXP_IMP_CHAIN argument_name =>'V_CONNECT_CREDENTIALS', argument_value=>'test/test@xxxxxxxxxxxxx'); doesn't help - setting variables by name returns error ORA-27475: "TEST.EXP_IMP_CHAIN" must be a program in this case Any other thoughts? Of course it is also possible that the scheduler fascility is not mature enough to provide comprehensive solution Remigiusz -- --------------------------------------- Remigiusz Sokolowski <rems@xxxxxxxx> WP/PTI/DIP/ZAB (+04858) 52 15 770 --------------------------------------- -- //www.freelists.org/webpage/oracle-l