ORA-00903: Invalid table name - running Set based mapping

Question

Hello,
Using OWB 10.2.04.36 and have created a mapping which reads data from Non-Oracle, ODBC source table, actually a worksheet in an Excel workbook which has been defined/set up using the Heterogeneous Service components.
I can view the data in the worksheet using the Design Center, Data Object Editor, Data Viewer tab so I know the data is accessible.
The mapping is performing a Loading Type: INSERT/UPDATE into a View which has an INSTEAD OF INSERT OR UPDATE OR DELETE ON view.
The mapping validates okay and is deployed successfully.
Yet when it is run in "Set based" Operating Mode from Control Center Manager the Execution Results show an "ORA-00903: Invalid table name" error is raised.
You cannot run the mapping in any Row based operating mode as Row based running fails with "ORA:22816: Unsupported feature with RETURNING clause" due to the generated code for the INSERT/UPDATE of the view using a RETURNING clause which is actioned on an INSTEAD OF trigger.
Looking at the generated package code I can strip out the SELECT statement from the MERGE statement for the alias "MERGE_SUBQUERY" and it runs and displays the expected result, however when the complete MERGE statement is taken and run I get the same ORA-00903 error that was reported in Control Center Manager.
Any ideas what the problem could be? I have another mapping that reads from the same source Excel workbook/worksheet and INSERT/UPDATE into a table without an INSTEAD OF trigger, this mapping deploys, runs successfully so the issue seems to be with the INSERT/UPDATE into the view. The views are what we require to be populated.
Thanks.

Answer 1

Hi,
But changing V_EMP_DEPT to EMP is not INSERTING/UPDATING to the view V_EMP_DEPT, what you propose is INSERTING/UPDATING into the table EMP. The code was only an example showing that the MERGE does not work when INSERTING/UPDATING into a view based on joining tables. For example say you wanted to INSERT/UPDATE the DNAME of V_EMP_DEPT then the MERGE statement generated by OWB PL/SQL mapping would use the code structure/template:-
MERGE INTO "V_EMP_DEPT" "V_EMP_DEPT"
   USING (SELECT 5369 "EMPNO",
                 'SMITH' "ENAME",
                 'CLERK' "JOB",
                 7902 "MGR",
                 To_Date('17/12/1980','DD/MM/YYYY') "HIREDATE",
                 800 "SAL",
                 'New Dept Name" "DNAME"
          FROM   Dual,
                 "DEPT" "DEPT"
          WHERE  ("DEPT"."DEPTNO" = 20)) "MERGE_SUBQUERY"
   ON (    "V_EMP_DEPT"."EMPNO" = "MERGE_SUBQUERY"."EMPNO")
   WHEN NOT MATCHED THEN
      INSERT("V_EMP_DEPT"."EMPNO",
             "V_EMP_DEPT"."ENAME",
             "V_EMP_DEPT"."JOB",
             "V_EMP_DEPT"."MGR",
             "V_EMP_DEPT"."HIREDATE",
             "V_EMP_DEPT"."SAL",
             "V_EMP_DEPT"."DNAME")
      VALUES("MERGE_SUBQUERY"."EMPNO",
             "MERGE_SUBQUERY"."ENAME",
             "MERGE_SUBQUERY"."JOB",
             "MERGE_SUBQUERY"."MGR",
             "MERGE_SUBQUERY"."HIREDATE",
             "MERGE_SUBQUERY"."SAL",
             "MERGE_SUBQUERY"."DNAME")
   WHEN MATCHED THEN
      UPDATE
         SET "ENAME" = "MERGE_SUBQUERY"."ENAME",
             "JOB" = "MERGE_SUBQUERY"."JOB",
             "MGR" = "MERGE_SUBQUERY"."MGR",
             "HIREDATE" = "MERGE_SUBQUERY"."HIREDATE",
             "SAL" = "MERGE_SUBQUERY"."SAL",
             "DNAME" = "MERGE_SUBQUERY"."DNAME";
{code}
This was only an example my target view has a lot more columns being MERGE'd into the view and joined tables.
Cheers,
Phil