In my job there is change capture stage.The i/p is two source file.Now the there are 2 targets. One target captures the new records and the other one captures the same records.
Now in the change capture stage the option Change Mode="Explicit Keys & Values" has been set and the change column name in Change Values option has not been mentioned explicitly as it is not capturing the updated records.
The warning I am getting in log is When checking operator: Defaulting "ACCOUNT_ID" in transfer from "beforeRec" to "outputRec"."
All the columns names except the key columns are coming in the log.
Now the job is getting aborted as no of warnings is more than 50 in project level which I can't change.
I can't change the job design also as i don't have access to do that.
So how can I eliminate this warning?
Please suggest.
Thanks
Shaonli
Warning due to Change Capture Stage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 467
- Joined: Tue Mar 20, 2007 6:36 am
- Location: Chennai
- Contact:
Re: Warning due to Change Capture Stage
From what you have posted I assume that you just one to get the new records(when a record with a new key value is added) and the old records(even if they have been updated).shaonli wrote:In my job there is change capture stage.The i/p is two source file.Now the there are 2 targets. One target captures the new records and the other one captures the same records.
Now in the change capture stage the option Change Mode="Explicit Keys & Values" has been set and the change column name in Change Values option has not been mentioned explicitly as it is not capturing the updated records.
The warning I am getting in log is When checking operator: Defaulting "ACCOUNT_ID" in transfer from "beforeRec" to "outputRec"."
All the columns names except the key columns are coming in the log.
Now the job is getting aborted as no of warnings is more than 50 in project level which I can't change.
I can't change the job design also as i don't have access to do that.
So how can I eliminate this warning?
Please suggest.
Thanks
Shaonli
For this you can use either the explicity keys and values like you are using. But if you do that you need to <b>explicitly</b> define the keys and values(Even when you don't want to track updates) which you are not doing.
So, you have two options now. Either set the Change mode to Explicit Keys All Values, or add all the value columns to the Change capture stage like you've done for keys. If you can't change the design, the only option you have is to suppress the warning. But, you'll still have bad data in the output.
Minhajuddin
<a href="http://feeds.feedburner.com/~r/MyExperi ... ~6/2"><img src="http://feeds.feedburner.com/MyExperienc ... lrow.3.gif" alt="My experiences with this DLROW" border="0"></a>
<a href="http://feeds.feedburner.com/~r/MyExperi ... ~6/2"><img src="http://feeds.feedburner.com/MyExperienc ... lrow.3.gif" alt="My experiences with this DLROW" border="0"></a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: