...
The job executes PL/SQL code.
How is the PL/SQL script defined?
- The script can be PL/SQL code be
saved to a separate file i.e. get_order.sql , and subsiquently sql file
can be referred as the value of the job parameter "command"
Code Block language sql <param name="command" value="config/live/commn/sqls/get_order.sql"/>
it can be specified as the value of the parameter command.
Code Block language sql <param name="command" value=" DECLARE v_order_date DATE := SYSDATE; BEGIN SELECT SYSDATE INTO v_order_date FROM DUAL; DBMS_OUTPUT.PUT_LINE(' +++ +++'); DBMS_OUTPUT.PUT_LINE('SET order_date IS '|| v_order_date); DBMS_OUTPUT.PUT_LINE(' +++ +++'); END; "/>
- Before the script is executed, the script will be analyzed by the job.
- Should JobScheduler parameter names be containted in that script then they are substituted by their current value.
- The following notations are supported: %parameter_name%, ${SCHEDULER_PARAM_parameter_name}
...