Runtime-Error after deploying a mapping with the generated script

Question

For example a very easy scenario:
1. Create a table and a view in a DB-schema, witch ist registered as WB-target-schema with the following scripts:
create view v1(c1) as select 'a' c1 from dual;
create table t1(c1 varchar2(1));
2. Import the table and the view into a OWB-module
3. Create a mapping ‘m1’
4. Drag and drop view and table into the mapping
5. Draw an arrow from the view-column to the table-column
6. Save and close the mapping
7. Mark the mapping in the ‘Design Center’ and klick the ‘Generate’-Button
8. Save the generated script ‘M1.pls’ to file
9. Run the script in SQL*Plus, connected with the target-schema (without using the Control Center Manager)
=> very easy right now ;-)
10. Start the mapping with the following script will produce the following error
SQL> declare
2 v_status varchar2(100);
3 begin
4 m1.main(v_status);
5 end;
6 /
declare
ERROR at line 1:
ORA-01403: no data found
ORA-06512: at "OWB_OWN.WB_RT_MAPAUDIT_UTIL", line 1027
ORA-06512: at "SCOTT.M1", line 2048
ORA-06512: at line 4
If i delete or comment the four WB_RT_MAPAUDIT_UTIL-calls - it work´s fine!
But is this a good advise?
What exactly does the wrapped package ‘WB_RT_MAPAUDIT_UTIL do?
Thanks
jwehner

Answer 1

I just ran into the same problem myself. I used the same technique of saving the generated OWB script to file and then compiling it through sqlplus. When I used the "Deploy" option for the mapping, then the problem went away. So when OWB is deploying the code it seems to be setting something internally that doesn't get set when you simple compile the PL/SQL. I don't know of any workaround to this. I will need it eventually, since I don't want to use the UI to deploy to various test environments and production. Maybe the built-in scripting language is the way to go.