Problems scheduling process flow

Question

Using OWB I have create a number of mappings and also a process flow using the defined mappings. All the mappings and the process flow are successfully deployed and can be executed without problems from Deployment Manager. I can even successfully execute my process from OS command line using the sqlplus_exec_template.sql file :
sqlplus vlad_proiect/vlad@proiect @F:\Oracle\OraWB92\owb\rtp\sql\sqlplus_exec_template.sql vlad_runtime ORACLE_WORK_FLOW PROCESS INCARC "," ","
where :
vlad_proiect/vlad my user name and passwd
proiect my database SID
vlad_runtime is the Runtime Repository owner
ORACLE_WORK_FLOW is the location of the process flow
INCARC is the process name.
I tried to do the same thing using OEM. I followed the example
http://otn.oracle.com/products/warehouse/htdocs/oem_scheduling_viewlet_swf.html
and the indication from WB User guide chapter Scheduling Mappings and Process Flows (13-19) but the scheduled job fails with the following reason :
VNI-2015 : The Node preferred credentials for the target node are either invalid or do not have sufficient privileges to complete the operation.
On Windows platforms, the Node credentials specified for the Windows target should have the "Logon as a batch job" privilege.
I have created the job as follows:
Tab General
 Job name: TEST
Selected target: Proiect
Tab Tasks
Tasks: Run SQL*Plus script
Tab Parameters
Parameters: vlad_runtime ORACLE_WORK_FLOW PROCESS INCARC "," ","
Override preferred credentials: checked
User name: vlad_runtime_acc the Runtime Repository access user
Password: vlad the Runtime Repository acc user passwd
I have imported the script oem_exec_template.sql
And in the Preferred credentials (from Configuration->Preferences->Administrator preferences) I set :
Database : Proiect with user vlad_proiect and my passwd.
Node : localhost with user vlad_runtime and his passwd.
Somewhere something is wrong set (or not set at all?) or …?

Answer 1

Razvan,
When OEM executes a scheduled job, it will logon to the node (i.e. your machine) as the user that is specified in the preferred credentials of OEM. That user (provided there is one... which is not necessarily default) is an operating system user and must have the 'logon as batch job' privilege. You can set this option (on Windows 2000) by going into control panel, administrative tools, local security policy, local policies, user rights assignment. Look for 'logon as batch job' and make sure the user being used to logon to the node has the privilege.
This setup is actually provided in the installation guide as well.
Hope this helps,
Mark.