Oem_exec_template

Env
OWB 9.2.0.2.8
Oracle DB 9.2.0.1
OEM 9.0.1
I have a SQL*Loader map that executes successfully using sqlplus_exec_template as below:
sqlplus owbrt_user/password@revdmd @sqlplus_exec_template.sql owb92_rt PlatformSchema SQL_LOADER COPY_OF_MAP_SLDR_INSTALL "," ","
But, when I tried running it as a job in OEM by importing the oem_exec_template and applying the same parameters as above, I get:
Session altered.
Role set.
Stage 1: Decoding Parameters
| location_name=PlaformSchema
| task_type=SQLLoader
| task_name=COPY_OF_MAP_SLDR_INSTALL
Stage 2: Opening Task
declare
ERROR at line 1:
ORA-20001: Task not found - Please check the Task Type, Name and Location are
correct.
ORA-06512: at line 261
child process exited abnormally
nms-915: The Job failed, error code=
I override preferred credentials with owbrt_user (runtime access user).
What am I doing wrong?
TIA
Hong

Hong,
There is a viewlet on OWB-OEM integration which describes the procedure step-by-step. Please take a look and let me know if you need further assistance:
http://otn.oracle.com/products/warehouse/htdocs/oem_scheduling_viewlet_swf.html
Regards:
Igor

Similar Messages

Pass customer parameter to oem_exec_template.sql

Hello
i have created on process flow using OWB9.2.0.8. This process flow is having an external activity that calls one MS-Dos batch file for the renaming of flat files
i am passing the SYDATE to this process flow so that the batch file receives this value and renames the files accordingly.
i have set a parameter at START and bind that parameter with the External activity.
When i execute this process flow using deployment manager i can see the prompt window for that parameter. Passing the parameter value is working perfectly fine.
but how can i pass the value to this process flow when i register this process flow through OEM.
i am passing the following parameters for scheduling thorough OEM to oem_exec_template.sql
RUNTIME_REP WF_LOC PROCESS SAMPLE_PF param1 ,

I can see the topic is raised here, but......what's the answer? ( I have the same problem )
I have a mapping input parameter, use the oem_exec_template.sql to run the mapping, but fail to see where to enter the mapping input parameter. The documentation I read through doesn't refer to this possibility whatsoever.
Anyone? :-)

Oem_exec_template in 10G

Where upgrading from 9i to 10g which involves rdbms, owb & oem.
We had successfull execution of OWB Process Flows in 9i using the oem_exec_template.sql script as an sql*plus script from OEM.
However when we try and create an OEM job in the new 10g OEM using the oem_exec_template.sql (both the 10g and 9i versions) OEM complains that "Inserted value is too long for variable".
Any ideas?

When I try to create a location for the Process Flow to be deployed I only get the option of Oracle Workflow and not OEM in OWB.
What software actually needed to be able to deploy Process Flows and schedule them from OEM? Is Oracle Management Server needed on the TARGET NODE or just an Oracle Agent would suffice? We have an OMS in the network on a different node than the target of loading, cant we leverage that?
If its not much of a problem can you please share the step by step procedure for scheduling the OWB Process in OEM with screen shots that you mentioned in the previous reply. It would help a lot.
I have Oracle 10g Warehouse Builder, OMS 9.2, Oracle Target Database 10g.
My email: [email protected]
Many thanks.

Oem_exec_template.sql

I am planning to schedule mappings using OEM and referred this:
http://www.oracle.com/technology/products/warehouse/htdocs/oem_scheduling_viewlet_swf.html
But I cannot find oem_exec_template.sql script in the mentioned directory.....I am using OWB 11g

or here is the script:
rem SYNOPSYS
rem
rem @oem_exec_template.sql rt_owner location_name {PLSQL | SQL_LOADER | PROCESS} task_name system_params custom_params
rem
rem NAME
rem
rem oem_exec_template.sql - OEM Execution Template
rem
rem USAGE
rem
rem rt_owner := e.g. MY_RUNTIME - Name of the Runtime Repository Owner
rem
rem location_name :- e.g. MY_WAREHOUSE - Physical Name of the Location to which this task was deployed
rem (i.e. a DB Location or a Process Location or the Platform Schema)
rem Note: Always use "PlaformSchema" for SQL_LOADER types.
rem
rem task_type :- PLSQL - OWB PL/SQL Mapping
rem | SQL_LOADER - OWB SQL*Loader Mapping
rem | PROCESS - OWB ProcessFlow
rem
rem task_name :- e.g. MY_MAPPING - Physical Name of the Deployed Object
rem
rem custom_params :- { , | (name = value [, name = value]...)}
rem e.g. ","
rem or MY_PARAM=1,YOUR_PARAM=true
rem
rem system_params :- { , | (name = value [, name = value]...)}
rem e.g. ","
rem or MY_PARAM=1,YOUR_PARAM=true
rem
rem RETURNS
rem
rem 0 if task reports SUCCESS or WARNING, otherwise >0
rem
rem
rem DESCRIPTION
rem
rem This SQL*Plus script can be pasted into a user-defined OEM SQL*Plus Job. This job
rem can be then used with OEM's 'Create Like' functionality to either create new
rem parameterized jobs or to submit new jobs for immediate execution.
rem
rem This script is design to be run from a Runtime User, not the Runtime Repository Owner.
rem The Runtime Repository Owner is nominated to the parameters.
rem
rem In its unchanged form the script takes the three keys required to identify
rem the executable task.
rem
rem The task is executed with the default parameters configured prior to deployment.
rem
rem The custom_params and system_params values override the default input parameters
rem of the task.
rem
rem Note: The comma character can be escaped using the backslash character; likewise the backslash
rem character can be escaped by itself.
rem
rem A list of the valid System Parameters for each task type can be obtained from the OWB
rem documentation, but generally the deployed defaults are sufficient. The Custom Parameters
rem are defined on the object in the OWB Designer.
rem
rem EXAMPLE
rem
rem @oem_exec_template.sql MY_RUNTIME MY_WAREHOUSE PLSQL MY_MAPPING "," ","
rem @oem_exec_template.sql MY_RUNTIME PlatformSchema SQL_LOADER MY_LOAD "," ","
rem @oem_exec_template.sql MY_RUNTIME MY_WORKFLOW PROCESS MY_PROCESS "," ","
rem
rem Note: @oem_exec_template.sql must not included in the OEM parameter field as is added
rem automatically by OEM.
define OEM_FRIENDLY=true
set serveroutput on
set verify off
whenever sqlerror exit failure;
define REPOS_OWNER=&1
define LOCATION_NAME=&2
define TASK_TYPE=&3
define TASK_NAME=&4
define SYSTEM_PARAMS=&5
define CUSTOM_PARAMS=&6
alter session set current_schema = &REPOS_OWNER;
set role wb_r_&REPOS_OWNER, wb_u_&REPOS_OWNER;
variable exec_return_code number;
declare
l_oem_style boolean := &OEM_FRIENDLY;
l_audit_execution_id number; -- Audit Execution Id
l_audit_result number := wb_rt_api_exec.RESULT_FAILURE; -- Result Code
l_audit_result_disp varchar2(64) := 'FAILURE'; -- Result Display Code
l_task_type_name varchar2(64); -- Task Type Name
l_task_type varchar2(64); -- Task Type
l_task_name varchar2(64); -- Task Name
l_location_name varchar2(64); -- Location Name
procedure override_input_parameter
p_audit_execution_id in number,
p_parameter_name in varchar2,
p_value in varchar2,
p_parameter_kind in number
is
l_parameter_kind varchar2(64);
begin
if p_parameter_kind = wb_rt_api_exec.PARAMETER_KIND_SYSTEM
then
l_parameter_kind := 'SYSTEM';
else
l_parameter_kind := 'CUSTOM';
end if;
dbms_output.put_line('| ' || p_parameter_name || '%' || l_parameter_kind || '=' || '''' || p_value || '''');
wb_rt_api_exec.override_input_parameter
p_audit_execution_id,
p_parameter_name,
p_value,
p_parameter_kind
end;
procedure override_input_parameters
p_audit_execution_id in number,
p_parameters varchar2,
p_parameter_kind in number
is
l_anchor_offset number := 1;
l_start_offset number := 1;
l_equals_offset number;
l_comma_offset number;
l_value_offset number;
l_esc_offset number;
l_esc_count number;
l_esc_char varchar2(4);
l_parameter_name varchar2(4000);
l_parameter_value varchar2(4000);
function strip_escape
p_escapedString varchar2
return varchar2
is
l_strippedString varchar2(4000);
l_a_char varchar2(4);
l_b_char varchar2(4);
l_strip_offset number := 1;
begin
loop
exit when p_escapedString is null or l_strip_offset > length(p_escapedString);
l_a_char := SUBSTR(p_escapedString, l_strip_offset, 1);
if l_strip_offset = length(p_escapedString)
then
l_strippedString := l_strippedString || l_a_char;
exit;
else
if l_a_char = '\'
then
l_b_char := SUBSTR(p_escapedString, l_strip_offset + 1, 1);
if l_b_char = '\' or l_b_char = ','
then
l_strippedString := l_strippedString || l_b_char;
l_strip_offset := l_strip_offset + 1;
end if;
else
l_strippedString := l_strippedString || l_a_char;
end if;
end if;
l_strip_offset := l_strip_offset + 1;
end loop;
return l_strippedString;
end;
begin
loop
l_equals_offset := INSTR(p_parameters, '=', l_start_offset);
exit when l_equals_offset = 0;
l_start_offset := l_equals_offset + 1;
loop
l_comma_offset := INSTR(p_parameters, ',', l_start_offset);
if l_comma_offset = 0
then
l_comma_offset := length(p_parameters) + 1;
exit;
else
l_esc_count := 0;
l_esc_offset := l_comma_offset - 1;
loop
l_esc_char := SUBSTR(p_parameters, l_esc_offset, 1);
exit when l_esc_char != '\';
l_esc_count := l_esc_count + 1;
l_esc_offset := l_esc_offset - 1;
end loop;
if MOD(l_esc_count, 2) != 0
then
l_start_offset := l_comma_offset + 1;
else
exit;
end if;
end if;
end loop;
l_parameter_name := LTRIM(RTRIM(SUBSTR(p_parameters, l_anchor_offset, l_equals_offset - l_anchor_offset)));
l_parameter_value := strip_escape(SUBSTR(p_parameters, l_equals_offset + 1, l_comma_offset - (l_equals_offset + 1)));
-- Override Input Parameter
override_input_parameter(p_audit_execution_id, l_parameter_name, l_parameter_value, p_parameter_kind);
exit when l_comma_offset >= length(p_parameters)-1;
l_start_offset := l_comma_offset + 1;
l_anchor_offset := l_start_offset;
end loop;
end;
procedure override_custom_input_params
p_audit_execution_id in number,
p_parameters varchar2
is
l_parameter_kind number := wb_rt_api_exec.PARAMETER_KIND_CUSTOM;
begin
override_input_parameters(p_audit_execution_id, p_parameters, l_parameter_kind);
null;
end;
procedure override_system_input_params
p_audit_execution_id in number,
p_parameters varchar2
is
l_parameter_kind number := wb_rt_api_exec.PARAMETER_KIND_SYSTEM;
begin
override_input_parameters(p_audit_execution_id, p_parameters, l_parameter_kind);
null;
end;
begin
-- Initialize Return Code
:exec_return_code := wb_rt_api_exec.RESULT_FAILURE;
-- Import Parameters
dbms_output.put_line('Stage 1: Decoding Parameters');
l_task_type_name := '&TASK_TYPE';
if UPPER(l_task_type_name) = 'PLSQL'
then
l_task_type := 'PLSQL';
elsif UPPER(l_task_type_name) = 'SQL_LOADER'
then
l_task_type := 'SQLLoader';
elsif UPPER(l_task_type_name) = 'PROCESS'
then
l_task_type := 'ProcessFlow';
else
l_task_type := l_task_type_name;
end if;
l_task_name := '&TASK_NAME';
l_location_name := '&LOCATION_NAME';
dbms_output.put_line('| location_name=' || l_location_name);
dbms_output.put_line('| task_type=' || l_task_type);
dbms_output.put_line('| task_name=' || l_task_name);
-- Decode Parameters
begin
-- Prepare Execution
dbms_output.put_line('Stage 2: Opening Task');
l_audit_execution_id := wb_rt_api_exec.open(l_task_type, l_task_name, l_location_name);
dbms_output.put_line('| l_audit_execution_id=' || to_char(l_audit_execution_id));
commit;
-- Override Parameters
dbms_output.put_line('Stage 3: Overriding Parameters');
override_system_input_params(l_audit_execution_id, '&SYSTEM_PARAMS');
override_custom_input_params(l_audit_execution_id, '&CUSTOM_PARAMS');
-- Execute
dbms_output.put_line('Stage 4: Executing Task');
l_audit_result := wb_rt_api_exec.execute(l_audit_execution_id);
if l_audit_result = wb_rt_api_exec.RESULT_SUCCESS
then
l_audit_result_disp := 'SUCCESS';
elsif l_audit_result = wb_rt_api_exec.RESULT_WARNING
then
l_audit_result_disp := 'WARNING';
elsif l_audit_result = wb_rt_api_exec.RESULT_FAILURE
then
l_audit_result_disp := 'FAILURE';
else
l_audit_result_disp := 'UNKNOWN';
end if;
dbms_output.put_line('| l_audit_result=' || to_char(l_audit_result) || ' (' || l_audit_result_disp || ')');
-- Finish Execution
dbms_output.put_line('Stage 5: Closing Task');
wb_rt_api_exec.close(l_audit_execution_id);
commit;
dbms_output.put_line('Stage 6: Processing Result');
if l_oem_style
then
if l_audit_result = wb_rt_api_exec.RESULT_SUCCESS
then
:exec_return_code := 0;
elsif l_audit_result = wb_rt_api_exec.RESULT_WARNING
then
:exec_return_code := 0;
else
:exec_return_code := l_audit_result;
end if;
else
:exec_return_code := l_audit_result;
end if;
dbms_output.put_line('| exit=' || to_char(:exec_return_code));
exception
when no_data_found
then
raise_application_error(-20001, 'Task not found - Please check the Task Type, Name and Location are correct.');
end;
end;
exit :exec_return_code;
;

How to use the oem_exec_template.sql

hi,guys
Env
OWB 9.2.0.2.8
Oracle DB 9.2.0.1
OEM 9.0.1
I've deployed a mapping SRC_TO_TAR. And I've successfully run this mapping in owb.
But when I try to use the oem_exec_template.sql to invoke in sqlplus, the script always tells me 'Taks not found'.
I use the following command to invoke the oem_exec_template.sql:
sqlplus owb_runtime_access/dw@dwdb @oem_exec_template.sql owb_runtime owb_target PLSQL SRC_TO_TAR "," ","
the result is
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Session altered.
Role set.
Stage 1: Decoding Parameters
| location_name=owb_target
| task_type=PLSQL
| task_name=SRC_TO_TAR
Stage 2: Opening Task
declare
ERROR at line 1:
ORA-20001: Task not found - Please check the Task Type, Name and Location are
correct.
ORA-06512: at line 261
Could any one here tell me how to correctly use the oem_exec_tempalte.sql?
thanks very much.
Frank

I login in as runtime owner and runtime access user and run the sql:
select * from all_objects where owner = 'OWB_TARGET'
I can't find the mapping that I have already deployed.
is this the reason why it always retrun "Task not found"
who knows?
urgent
thanks
Frank

How can I execute a OWB ProcessFlow without OEM?

I have created the "process flow" in the OWB,and I want execute it in my applicaton,not through OEM,how can I do it?

In order to use OWF without OEM, you can start the script owb/rtp/sql/oem_exec_template.sql in a sql session.
(Do the same as needed in OEM):
The mandatory parameters for the script are as follows:
- Runtime Repository Owner
- Target location
- Target Type: either one of the PL/SQL, SQL_LOADER, or PROCESS.
- Task name (name of the mapping/or process flow)
- System parameters (comma separated, enclosed by double quotes; comma and \ can be escaped by \)
- Custom parameters (see system parameters)
Example :
@oem_exec_template.sql MY_RUNTIME MY_WORKFLOW PROCESS MY_PROCESS "," ","
If you need more information, please refer to the user documentation : Scheduling Mappings and Process Flows

Wb_rt_api_exec problem in 10G OEM

I'm trying to schedule a process in 10G OEM built in OWB. All validation, generation, deployment is fine. I can't find the docs to guide me in this process. The docs deal with the oem_exec_template.sql - which says to use wb_rt_api_exec.run_task for 10G OEM. Any idea what to do for scheduling in 10G OEM??
Based on examples in Metalink forum this is what I'm putting into the SQL script job in OEM. Errors included as well.
declare
ret number;
begin
ret:=runtime_owner.wb_rt_api_exec.run_task('RUNTIME', 'EASYDW', 'PROCESS', 'F4211LOAD','','',1);
end;
Copyright (c) 1982, 2004, Oracle. All rights reserved.
SQL> SQL> SQL> SQL> Connected.
SQL> SQL> 2 3 4 5 6 ret:=runtime_owner.wb_rt_api_exec.run_task('RUNTIME', 'EASYDW', 'PROCESS', 'F4211LOAD','','',1);
ERROR at line 4:
ORA-06550: line 4, column 6:
PLS-00306: wrong number or types of arguments in call to 'RUN_TASK'
ORA-06550: line 4, column 1:
PL/SQL: Statement ignored
declare
ret number;
begin
ret:=runtime_owner.wb_rt_api_exec.run_task('RUNTIME', 'EASYDW', 'PROCESS', 'F4211LOAD','','');
end;
ERROR at line 1:
ORA-20001: Task not found - Please check the Task Type, Name and Location are
correct.
ORA-06512: at "RUNTIME_OWNER.WB_RT_API_EXEC", line 620
ORA-06512: at line 4

Thanks guys. You were both right - wrong process name and too many parameters. And I realized I used the database locations value - not the Process flows locations.
This worked =
runtime_owner.wb_rt_api_exec.run_task('process flows locations', 'PROCESS', 'process name','','',1);
declare
ret number;
begin
ret:=runtime_owner.wb_rt_api_exec.run_task('DWDEST', 'PROCESS', 'PROC','','',1);
end;
/

Unable to find OEM registration infos in preferences wizard

I'd like to register OEM configuration informations in OWB (9.2.0.2.8) running on Solaris 2.8 and 9.2.0.3 Database.
I have no tab dedicated to OEM registration in my preferences wizard...how to fix it ?
+ is there any way to export job scheduling and tasks informations
THANKS A LOT FOR HELP

Pierre,
In 9.2 we do not have a similar registration like we used to have in 9.0.3 and earlier. There is a script oem_exec_template.sql that you should use to register a job in OEM. Please check the viewlet http://otn.oracle.com/products/warehouse/htdocs/oem_scheduling_viewlet_swf.html to see how to do that.
Thanks,
Mark.

How to use OEM location in OWB?

What is a purpose of oem location in owb 9.2 (9.0.4)?
This location doesn't use in any module and integration with oem realize through oem_exec_template.sql script that manually register in oem.
How to use this location?

Dmitry,
This location would be used in the process flow configuration of an individual activity. The location enables you to perform remote node execution. For example, if you wanted to execute SQL loader on a remote node (not the actual target machine) then this would happen via the OEM location. The use of the OEM location would require an Oracle Management Server (OMS) set up and OEM agents locally.
Mark.

Scheduling process flows and mappings

Hello
I have created many process flows. Now i want to schedule it. I know i can use OEM, but i need to log in as DBA. i also know that you can use owb scheduler module to schedule a process flow. but i want to schedule it using sql plus. i found a link on scheduling process flow in sql plus for older versions of OWB. Can we use the same script for OWB 10.2? here is the link - http://www.dba-oracle.com/oracle_news/2005_7_7_Scheduling_an_OWB.htm
Please let me know how to schedule a process flow in OWB 10.2 in sql plus. It would be great if you could post the sql script required to schedule OWB 10.2 process flows.
Thank You

Hi,
the web server named by the link is down, so a general answer.
You can use the scripts sqlplus_exec_template.sql and oem_exec_template.sql from the directory <OWBHOME>/owb/rtp/sql and schedule it with cron or at or scheduler or ...
Regards
Detlef

Scheduling Mappings and Process Flows

Can you please tell me how to schedule mappings and process flows in a little detail, if any one has done that. I think OEM can be used for this but dont have any clear cut idea of doing it. Can the mappings/process flows be scheduled without using OEM console ?
Waiting for you suggestions.
rgds
-AP

Hi
You can schedule your mapping and process flows with OEM or database job.
You will find script templates in the OWB HOME/owb/rtp/sql directory
and you can scheldule them.
If you want to do it in OEM use the oem_exec_template.sql file createing an OEM job. Read the OWB documentation about it. If you have any question about it ask it, I have done this procedure many times.
Ott Karesz
http://www.trendo-kft.hu

Capturing errors when you run mappings.

Hi all,
Your help is appreciated. Thanks in advance.
My questions are.
1. How do you run mappings using sqlplus and run these mappings as a Batch in windows.
2. How do i capture errors without stopping the batch process. If there are any errors it should write to the error table and go on.
3. I am not using any process flow So i need to now how to call all the mappings one by one and writing the errors to the error table.
4. Does warehouse builder has a built in error table to use. If so how do you use it and what is the table name.
5. If i have to schedule these mappings how do i do it.
6. what is the difference between oem_exec_template.sql and sql_exec_template.sql
I am using owb 10.2 version. Anyone out Please help me out. I really appreciate your help. If you have any sample code too that will help.
Thanks
Danny
Edited by: vdanakon on Sep 19, 2008 10:55 AM

Check these two scripts: sqlplus_exec_background_template.sql and sqlplus_exec_template.sql
They are in OWB_HOME\owb\rtp\sql
About DML Error Logging check http://www.rittmanmead.com/2008/01/31/owb11g-dml-error-logging-and-data-rules/

Please help me in scheduling jobs...urgent

Hi,
I am able to run the oem_exec_template successfully. I am able to run the Process_flow successfully using the oem_exec_template. But, I am still not able to schedule it. It gives me the same old error
"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 logged on as local administrator.
-I have given the privilege "Log on as a batch job"
-I checked that the user is not in "deny log on as a batch job"
-I have given the preferred credentials for target database(MART.ps0156) as sys userid and password.
-I have given the preferred credentials for node as administrator userid and password.
-In parameters tab while creating job I have gave the same parameters which I gave when I successfully executed the oem_exec_template.sql.
-Have also checked override preferred credentials and gave runtime useraccess userid and password.
STILL IT DOESNT WORK!!!!!!!!

Rajagopal,
What you would have to do, is overwrite the preferred credential for the script execution. You would set this to the runtime access user.
Mark.

How to stop OWB Process Flow job

I have a problem.
For scheduling OWB Process Flows I use EM (create Job - SQL Script) in which I schedule jobs with script @/home/oracle/scripts/oem_exec_template.sql.
Sometimes it happens, that the job doesn't finish and I also can't expedite it through Workflow manager because it is not listed there. So next executions for this job doesn't fire, because it is still active (it is shown in EM as Running …..and also I can't stop it there).
I also can't find the session for this job and also in dictionary I can't find the job, I went through these views, but nowhere I can't find any of my scheduled jobs, and of course also not the ones that are still running.
DBA_SCHEDULER_JOBS
DBA_SCHEDULER_RUNNING_JOBS
DBA_SCHEDULER_JOB_RUN_DETAILS
Where in dictionary can I find my jobs?
How can I kill my running jobs?
OS: Red Hat Linux 3
DB: 10.1.0.3.0
OWB: 10.1.0.2.0
I'm quite desperate about this isue,
Thank you,
Gorazd

Gorazd,
the best way to identify problem with processflow execution - using OWB Runtime Audit Browser.
Other variant - using public OWB runtime view, for example for reporting executions of you process run this select under OWB repository owner or any OWB user:
select created_on,elapse_time,return_result from all_rt_audit_executions
where object_name='<your processflow name in uppercase>' order by created_on;
RETURN_RESULT must be equal 'OK' and ELAPSE_TIME (in seconds) greater then 0.
If this query returns rows with null RETURN_RESULT or RETURN_RESULT<>'OK' or with zero elapse_time and this cases match (by date) with EM problems then you need analyze process executions in more detail with Runtime Audit Browser.
Alternatively use select from view ALL_RT_AUDIT_EXEC_MESSAGES / ALL_RT_AUDIT_MAP_RUN_ERRORS / ALL_RT_AUDIT_PROC_RUN_ERRORS.
Oleg

Error when running the OWB process flow from the shell script

Hi,
I am able to deploy the process flow succesfully but when I execute the process flow from the shell script,I am getting the following error.Previously it worked fine.
I had to make some chnage in the IP address,so i had to deploy again.
Connected.
SQL> @/oracle/product/owb92028/owb/rtp/sql/oem_exec_template.sql OWB_RTR LOC_P_REL PROCESS P_W_SOURCE "," ","
Elapsed: 00:00:00.00
Elapsed: 00:00:00.01
Stage 1: Decoding Parameters
| location_name=LOC_P_REL
| task_type=ProcessFlow
| task_name=P_W_SOURCE
Stage 2: Opening Task
declare
ERROR at line 1:
ORA-01422: exact fetch returns more than requested number of rows
ORA-06512: at "OWB_RTR.WB_RT_API_EXEC", line 17
ORA-06512: at "OWB_RTR.WB_RT_API_EXEC", line 137
ORA-06512: at "OWB_RTR.WB_RT_API_EXEC", line 164
ORA-06512: at line 205
Thanks in advance.
Vinay

Hi Kamal and kanakam kolla,
This is just to let you know that,I solved my problem little differently by creating a new location and deployed the process flow.Now my process flow is working fine when i call from the shell script.What i see is that, it does not update properly when we update and redeploy the process flow.So far this is the work arround i could think off and i succesfully tested this.
Thank you Kamal and kanakam kolla,for giving a thought towards my problem.
Thanks
Vinay

Oem_exec_template

Similar Messages

Maybe you are looking for