Transform Map is not working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2016 06:39 AM
Hi All,
I have created one Data source of JDBC type, which is able to load data into Import set table using "Test load 20 Record".
My problem is the transform map is not working properly , I can see the data source is populating data to import set table but the data is not populating in my target table.
I have tried with direct field mapping also I have tried with transform script , both are not working, I used some log and found out error as source and target is undefined but in my transform map both source_table and target_table has proper table name.
please share your idea.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2016 12:36 AM
Hi Mohammed Lais,
Yes u_citicus_qa_db is an import set table and there is no create write delete read acl present explicitly.
I want to mention one more thing after load 20 record test I perform transform and found there is no insert, update, ignored, skipped or error in the Import set.
Thanks.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2016 12:42 AM
Check if there are any data policies on the target table which are preventing the data load.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2016 01:56 AM
Hi All,
There is no data policy present on the target table.
If I create record manually in the import set table then the transform map is working and it is populating data in the target table.
But when Data source is populating data the transform map is not working.
I just want to mention is there any system property or something that is required for JDBC type data source !
Thanks.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2016 03:18 AM
Did you create a new import set table for this data table or used an existing table?
I think it has something to do with the data encoding of the source records.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2016 03:30 AM
Hi Mujtaba,
The Import set table has been created during the data source creation not existing table.