Oracle 10G Database Control and Scheduling OWB Process Flow

Question

Does anyone know how to go about scheduling an OWB Process Flow from
Oracle 10G Data Base Control. I knew how to do this with Oracle Enterprise Manager 9.2 but we recently upgraded to Oracle Db 10G and the interface has changed significantly.
Now the interface seems to require a PL/SQL stored procedure to be executed.
Is there a template procedure that is installed with 10G Data Base Control as there was for 9.2 i.e. oem_exec_template.sql?
Thanks! Deadline approaching fast...
Marion

Answer 1

I've used the oem_exec_template.sql successfully with OWB 10.1 and Oracle 10G Database Control, with a little trial and error at first.
I'm assuming that your job execution environment is set up correctly, ie. that you can properly execute jobs via the host agent.
1. Log on to Database Control as SYSTEM, select Jobs from the links at the bottom of the page
2. In the Results section, Create Job, select "SQL Script" and press Go
3. In the General section, enter Job Name, and as SQL Script enter e.g.:
@/u01/app/oracle/owb_oracle_home/owb/rtp/sql/oem_exec_template.sql owb_runtime WF_LOC PROCESS MY_PROCESS , ,
4. In the Databases section, add your target database
5. In the Credentials section, I select "Override Preferred Credentials" and use the agent account (oracle on my Linux system) and db user owb_access (OWB Runtime Access user)
6. Review Schedule tab and submit
Comments on step 3:
- the oem_exec_template.sql script must be installed according to the path specified in step 3, on the database host where the OWB Runtime Repository is located
- owb_runtime is the owner of my OWB Runtime Repository
- WF_LOC is the name of my Workflow Location as seen in OWB Deployment Manager
- MY_PROCESS is the name of a deployed Workflow Process
- the commas indicate that I don't supply any system or custom parameters.
- step 3 is actually a shell command line that is interpreted by eg. /bin/sh on Unix or cmd on Windows, and must obey proper quoting rules. On windows, I had to specify the empty commas as "\," (including dblquotes)
Regards, Hans Henrik