Page 1 of 1

warning in Chage detection

Posted: Mon Aug 22, 2005 9:21 am
by kumar_s
Hi,
Iam using chage detection, and iam getting warning for all the column as follows.

Code: Select all

CHD030: When checking operator: Defaulting "CPRFBRN" in transfer from "beforeRec" to "outputRec".
here CHD030 is name of change capture stage, "CPRFBRN" is column name.

is there any way to get rid of this warning..

(I also setting defalult value in some columns, still it gives this warnings)

regards
kumar

Posted: Mon Aug 22, 2005 4:33 pm
by ray.wurlod
Setting a default value explicitly for this column should cause the warning to disappear.

Posted: Mon Aug 22, 2005 8:37 pm
by vmcburney
The Change Capture stage provides endless entertaining warning messages for the whole family. It works best when the column list on the After (primary) stream exactly matches the Before (reference) stream. If you have a column on the After stream that is not on the Before stream then you need to choose Explicit Values, when you leave this column out of the Key and Values list then you will get a warning for that column. It is a completely valid action, you are simply passing a value through the stage without using it as a key or value column, but you cannot avoid the warning. Filter out the warning using a message handler.

If you think you have the CPRFBRN on both the Before and After links then check that the spelling and data type of the column matches on both links and that it comes up when you choose Explicit values and try to add it as a value column.

Posted: Tue Aug 23, 2005 8:09 am
by kumar_s
vmcburney wrote:
If you think you have the CPRFBRN on both the Before and After links then check that the spelling and data type of the column matches on both links and that it comes up when you choose Explicit values and try to add it as a value column.
Hi vincent,
it is not only for one column, i just place a sample, but it gives for all the columns. And fortunately, both are of same layout....

Ray,
As i told i had given defaluts....(no need to loose points, coz i still need your help :P )

regards
kumar

Posted: Tue Aug 23, 2005 8:50 am
by thebird
Hi,

This topic has been discussed earlier in this forum.

Please go through the link below to find one of the postings on the same topic.

Regards,

The Bird.

Posted: Wed Aug 24, 2005 5:10 am
by kumar_s
thebird wrote:Hi,

This topic has been discussed earlier in this forum.

Please go through the link below to find one of the postings on the same topic.

Regards,

The Bird.
link :?: :?: :?: :?:

regards
kumar

Posted: Fri Aug 26, 2005 2:05 am
by thebird
Hi,

For some reasons, the link that I had put here just didnt show up.

Sending this again.

viewtopic.php?t=89244&highlight=change+capture

Regards,

The Bird.

Posted: Sun Sep 11, 2005 10:23 am
by kumar_s
Hi,
Mine is huge data, hence the suggestion povided (change capture for only the key and the value and by pass rest of the values to join) may not be much helpful.
Is there any other way to get rid of this warnings.
(right now just for this single stage i have replace a full outer join and transformer to give the codes and funnel to collect back, Excepting a smart solution...)

regards
kumar

Posted: Sun Sep 11, 2005 10:59 am
by roy
Hi,
I'm currently facing a similar situation.
In my case 2 DataSets are prepared with Identical scheme and passing them to CC stage in another job causes warnings as mentioned in the original post.
I'll try to post my findings sd they develop.

To be continued ...

My problem was resolved after rebuilding the CC stage a new.
Kinda reminds me of the merge stage in server :roll:

IHTH,

Posted: Wed Sep 14, 2005 9:16 am
by kumar_s
roy wrote:Hi,
My problem was resolved after rebuilding the CC stage a new.
Kinda reminds me of the merge stage in server :roll:

IHTH,
Hi,
do u mean to say that the warning vanishes if the CC stage is rebuilt?1?!?! :roll:

regards
kumar