DBMS_SCHEDULER.run_chain() only works when connected to DB as sys

Question

Database Version: 10.2.0.4.0
Hello,
I have a problem with DBMS_SCHEDULER.run_chain where the Chain to be run references an external Program.
The Chain runs correctly when run via SQLPLUS when you are connected to the database as SYS but fails to run when you are connected to the Database as the User who owns the Chain.
The complete steps to recreate the problem are below. Any thoughts or suggestions gratefully received.
Thanks,
Andy
STEP 1: Login with sys as sysdba and create a new user
CREATE USER chaintest IDENTIFIED BY password PROFILE DEFAULT ACCOUNT UNLOCK;
GRANT MGMT_USER TO chaintest;
GRANT CONNECT TO chaintest;
GRANT IMP_FULL_DATABASE TO chaintest;
GRANT SCHEDULER_ADMIN TO chaintest;
GRANT MANAGE SCHEDULER TO chaintest;
GRANT EXECUTE ANY CLASS TO chaintest;
GRANT CREATE ANY DIRECTORY TO chaintest;
GRANT CREATE ANY JOB TO chaintest;
GRANT CREATE TABLE TO chaintest;
GRANT EXECUTE ANY PROGRAM TO chaintest;
GRANT CREATE JOB TO chaintest;
GRANT CREATE EXTERNAL JOB TO chaintest;
STEP 2: Create a very simple batch file
Create a folder called c:\chaintest and create a text file in there whose entire contents
is "notepad.exe" followed by a carriage return. The idea is that if this batch file is
called a notepad Window will be opened so we can clearly see if the batch file has run.
STEP 3: Create a DBMS_SCHEDULER Program
BEGIN
DBMS_SCHEDULER.CREATE_PROGRAM (
program_name => 'CHAINTEST.CHAINTEST_PROGRAM',
program_type => 'EXECUTABLE',
program_action => 'C:\WINDOWS\SYSTEM32\CMD.EXE /q /c c:\chaintest\chaintest.bat',
number_of_arguments => 3,
enabled => false);
DBMS_SCHEDULER.define_program_argument(
program_name =>'CHAINTEST.CHAINTEST_PROGRAM',
argument_position => 1,
argument_type => 'VARCHAR2',
default_value => '/q');
DBMS_SCHEDULER.define_program_argument(
program_name =>'CHAINTEST.CHAINTEST_PROGRAM',
argument_position => 2,
argument_type => 'VARCHAR2',
default_value => '/c');
DBMS_SCHEDULER.define_program_argument(
program_name =>'CHAINTEST.CHAINTEST_PROGRAM',
argument_position => 3,
argument_type => 'VARCHAR2',
default_value => 'c:\chaintest\chaintest.bat');
DBMS_SCHEDULER.enable('CHAINTEST.CHAINTEST_PROGRAM');
END;
STEP 4: Create a chain
BEGIN
DBMS_SCHEDULER.CREATE_CHAIN (chain_name => 'CHAINTEST.CHAINTEST_CHAIN');
END;
STEP 5: Create the only Chain Step
BEGIN
DBMS_SCHEDULER.DEFINE_CHAIN_STEP(chain_name=>'CHAINTEST.CHAINTEST_CHAIN'
, step_name=>'STEPA'
, program_name=>'CHAINTEST.CHAINTEST_PROGRAM');
END;
STEP 6: Create Chain Rules
BEGIN
DBMS_SCHEDULER.DEFINE_CHAIN_RULE(
chain_name=>'CHAINTEST.CHAINTEST_CHAIN'
, condition=>'TRUE'
, action=>'START STEPA');
DBMS_SCHEDULER.DEFINE_CHAIN_RULE(
chain_name=>'CHAINTEST.CHAINTEST_CHAIN'
, condition=>'STEPA COMPLETED'
, action=>'END');
END;
STEP 7: Enable the Chain
BEGIN
DBMS_SCHEDULER.enable('CHAINTEST.CHAINTEST_CHAIN');
END;
STEP 8: Run the Chain whilst still connected as sys and observe that a Notepad window opens
confirming that the Batch file ran successfully.
BEGIN
DBMS_SCHEDULER.run_chain(
chain_name=>'CHAINTEST.CHAINTEST_CHAIN'
, start_steps=>NULL);
END;
STEP 9: Connect to the database as the CHAINTEST user and run the same command as in STEP 8 above.
Observe that even though you receive the message "PL/SQL procedure successfully completed." and do
not see any error messages that no Notepad Window is opened indicating that the Batch file was NOT run.
BEGIN
DBMS_SCHEDULER.run_chain(
chain_name=>'CHAINTEST.CHAINTEST_CHAIN'
, start_steps=>NULL);
END;

Answer 1

>
The Chain runs correctly when run via SQLPLUS when you are connected to the database as SYS but fails to run when you are connected to the Database as the User who owns the Chain.
>
Not true based on what you posted. The chain DOES RUN connected as SYS and when connected as the User who owns the chain.
You posted steps that show that SYS is the user that owns the program and thus the chain.
>
STEP 1: Login with sys as sysdba and create a new user
STEP 8: Run the Chain whilst still connected as sys and observe that a Notepad window opens
confirming that the Batch file ran successfully.
>
I don't see where you made any EXECUTE grant to user 'chaintest' that would allow that user to execute the program.
See the Usage Notes in the CREATE PROGRAM section of DBMS_SCHEDULER in the Database PL/SQL Packages and Types Reference
http://docs.oracle.com/cd/B28359_01/appdev.111/b28419/d_sched.htm#CIHEHDHA
>
For other users to use your programs, they must have EXECUTE privileges, therefore once a program has been created, you have to grant EXECUTE privileges on it.
>
Grant the EXECUTE privilege to user 'chaintest' and try it.