Deployment of a OWB Map-ORA-06550

Question

I created a map that uses two source modules that
point to two different Oracle schemas and instances.
The two tables from which data is imported are PAT_RESULTS and PATIENT tables. Both tables are in the schema CCDBA. One table
STAFF_ALT_ID is in the schema CCDEV.
The target data for the map is a UNIX file.
The File connector from the target to the CCDEV schema
is FILE_CONNECTOR.
The file connector from the target to the CCDBA schema
is FILE_CONNECTOR_ODOULS.
When I deploy the map I get ORA-06550, the Deployment
Manager cannot find the PAT_REULTS table.
When I look at the package body, the file connector referenced for the PAT_RESULTS table is a different
connector than the PATIENT table even though they live in the same schema, i.e. CCDBA.
(See PL/SQL select statement below).
Why can't the deployment manager "see" this table?
Why does PAT_RESULTS have a different file connector?
The meta-data imported for the table,PAT_RESULTS is the same DBlink as the deployment operation.
Any help would be appreciated.
PL/SQL select below
SELECT
"PAT_RESULTS_FILE_CON266982"."FACILITY_ID" "FACILITY_ID",
"PATIENT_FILE_CONNECTOR_ODOULS"."PATIENT_ID" "PATIENT_ID",
"PAT_RESULTS_FILE_CON266982"."RESULT_SEQ" "RESULT_SEQ",
"PAT_RESULTS_FILE_CON266982"."RESULT_VALUE" "RESULT_VALUE",
(TODATE("PAT_RESULTS_FILE_CON266982"."PERFORM_DDT")) "PERFORM_DATE",
"STAFF_ALT_ID_FILE_CONNECTOR"."ALT_STAFF_ID" "ALT_STAFF_ID",
"STAFF_ALT_ID_FILE_CONNECTOR"."SOURCE_SYSTEM" "SOURCE_SYSTEM",
"PAT_RESULTS_FILE_CON266982"."ABNORMAL_FL" "ABNORMAL_FL"
FROM "STAFF_ALT_ID" "STAFF_ALT_ID_FILE_CONNECTOR",
"PATIENT" "PATIENT_FILE_CONNECTOR_ODOULS",
"PAT_RESULTS" "PAT_RESULTS_FILE_CON266982" WHERE ( "STAFF_ALT_ID_FILE_CONNECTOR"."STAFF_ID" = "PAT_RESULTS_FILE_CON266982"."CHART_ID" ) AND
( "PATIENT_FILE_CONNECTOR_ODOULS"."PAT_SEQ" = "PAT_RESULTS_FILE_CON266982"."PAT_SEQ" ) AND
( "PAT_RESULTS_FILE_CON266982"."LABEL_SEQ" IN ( 1013 , 1014 , 1015 , 1016 ) );

Answer 1

Hi,
You ca n do it by changing the load type of target table.
As you said, the conditions will be different for each load type insert, update and delete.
The flow will be in the following way.
Source ---> splitter (Here you need to define the conditions and separate the insert rows, delete rows, and update rows.) ---> Now drag the target table 3 times and give the name as table_insert_mode, table_delete_mode and table_update_mode.
Now link the records from splitter with insert logic to table_insert_mode. and make sure the load type of target table as insert.
Now do this for remaining modes, that are delete and update. And make sure that, the load types will be delete and update.
Now, the mapping will do three types of opeations can be possible on each row according to the defined logic.
Hope this helps you.
Thank you,
Regards,
Gowtham Sen.