Hello ,
I have a Job Performing CDC .The out of this job is 3 data sets as usual first one Insert , Second Update and the last one is delete.I want to do only 3 Generic jobs using Run Time Column Propagation to handle Insert , Update and Delete.I did the insert one and it finished successfully.Unfortunately for Update And Delete I couldn't Because I have to Specify the Key Column explicitly.I did all work around and all failed:
1- Make A generic KEY_COLUMN With Checking Key Check Box then use Modify Stage to Rename the attribute but also after renaming and using RCP Key info was dropped :
Modify Specification : BRANCHID:int32= KEY_COLUMN
2- I Used Environment Variable OSH_PRINT_SCHEMAS to Print Schema Definition for all sources and Destinations ,But unfortunately Schema Contains only Column Name , DataType , Length , Nullable. Key is not included at the schema definition.
3 - I found this thread at dsxchange define the Key Column using {Key} but it doesn't work.
Is there are any Ideas To Make Update and delete generic jobs ?
Generic CDC Update and Delete Jobs
Moderators: chulett, rschirm, roy
Generic CDC Update and Delete Jobs
Bassem Hafez
Hello Craig,
Ya I have 2 servers 8.1 and 8.5 .My post was after applying all of these trials at 8.1.
After that I tried to do the same at 8.5 and it worked but I discovered that it was my fault I added the key column to the metadata with Key check box checked and rest of columns were propagated which is invalid.I need a generic solution by making also the key propagated.After removing the key from metadata and make it propagated same result as 8.1 Job aborted with the following.
No key fields defined in the design schema.
Ya I have 2 servers 8.1 and 8.5 .My post was after applying all of these trials at 8.1.
After that I tried to do the same at 8.5 and it worked but I discovered that it was my fault I added the key column to the metadata with Key check box checked and rest of columns were propagated which is invalid.I need a generic solution by making also the key propagated.After removing the key from metadata and make it propagated same result as 8.1 Job aborted with the following.
No key fields defined in the design schema.
Bassem Hafez
-
ray.wurlod
- Participant
- Posts: 54595
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
