Repository Table Empty after mapping procedures

Question

I'm using OWB 11g and simply trying to do a 'test case' where I create a simple mapping from a single (oracle) source table to a target table and then generate and populate a repository table. All 3 tables have the exact same structure. The problem is that when I generate the Repository table it has no data in it.
I'm religiously following all the directions:
1) Create & Bind on the target table
2) Synchronize on the target table
3) Validate Mapping
4) Generate mapping
Go to Design center
5) Validate, Generate, Deploy the repository table
6) Validate, Generate, Deploy and 'Start' the repository mapping.
But when I finally select 'data' for the Repository Table the Data Viewer shows me the structure but no data beneath it.
Just to cover the basics, I've set up a Staging Area module for all of this and I'm sure my source table has data in it.
Any ideas on why this is happening?
Thanks
Message was edited by:
John W

Answer 1

David,
I found the table that is generating the[b] table of view does not exist error- but I'm stumped as to why this is. I have 2 tables in my source module (dw_user) which are the EVENTS and PRIZES tables. They are both accessible from the staging schema and the repository schema in sql. But the PRIZES table is getting the table of view does not exist error and the EVENTS table is not. Also, all columns referred to in the script are all valid.
The line that is generating the error is line 17 in the script below which I've bolded. Note that Line 16 accessing the EVENTS table is not generating an error. Here are some points:
1) When I try to 'deploy' either the EVENTS table or the PRIZES table, as you suggested, I get a msg saying that these are source tables and cannot be 'deployed'. I am validating, generating and deploying the target table and the mapping however.
2) One difference I did find in my initial error was that I just happened to have a copy of the EVENTS table in the stage schema (dw_stg) but did not have a copy of the PRIZES table there. This should not matter since the schema being accessed in the sql is obviously the source schema (dw_user) and not the stage schema (dw_stg). Nonetheless, just as an experiment I also put a copy of the PRIZES table in the stage schema (dw_stg) but the error remained.
Any other ideas as to why the EVENTS table is accessible in the sql but the PRIZES table is not?
Here's the script with the error on line 17:
1) CREATE OR REPLACE PACKAGE BODY ""MAP3"" AS
2)
3)
4)
5)
6)
7) -- Procedure "JOINER_p" is the entry point for map "JOINER_p"
8)
9) PROCEDURE "JOINER_p"
10) IS
11)
12) -- Row by row processing
13) "PRZ_EVT_ld" BOOLEAN;
14) CURSOR "JOINER_c" IS
15) SELECT
16) "EVENTS"."EVENTNAME" "EVENTNAME",
[17) "PRIZES"."PRIZEPLACE" "PRIZEPLACE",
18) "PRIZES"."PRIZEAMOUNT" "PRIZEAMOUNT"
19) FROM
20) "DW_USER"."EVENTS" "EVENTS",
21) "DW_USER"."PRIZES" "PRIZES"
22) WHERE
23) ( "EVENTS"."EVENTID" = "PRIZES"."EVENTID" );
Thanks for your continued help.
Cheers,
John