Page 1 of 1

Incomplete column value??

Posted: Wed Aug 25, 2010 4:28 am
by sweety123
Hi all,

I have a server job having a sequential file as source. This file has a field DC_ID with 'Incomplete column' value set to 'Error'.
This field is being mapped to another sequential file in same format. But on compilation I get the follwoing error:

The Incomplete column value of Column DC_ID must have values in ascending order

Can anybody tell me the meaning and reason for this error??

Thanks in advance.

Re: Incomplete column value??

Posted: Wed Aug 25, 2010 5:02 am
by HariK
Could you post your job design and the complete error message. ie., the stage where you are getting the error, you can identify it by clicking show error or more buttons on compile window.

Posted: Wed Aug 25, 2010 6:21 am
by chulett
It means that any 'Incomplete Column' handling must be done from whatever column you start with to the end. In other words, you can't have 10 columns and set this on 7 only, you have to set it for 7-10.

Posted: Wed Aug 25, 2010 6:03 pm
by ray.wurlod
Click Help while you are in the Columns grid. The explanation there is quite good.

Posted: Wed Aug 25, 2010 11:32 pm
by sweety123
Ray,

Thanks for your response. I understood the different options for 'incomplete column' from DataStage help. However, I still have a query...

In my job, the DC_ID is 10th out of 15 columns in the input file. Incomplete column value is set to Error for it. While mapping to an intermediate file, I make it the last column of the file. In doing so, DataStage does not accept any value for 'incomplete column' rule other than Replace.....What can be the possible reason for this behavior?

Posted: Wed Aug 25, 2010 11:44 pm
by ray.wurlod
You have to set column#15 first, then column #14, and so on till you get to column #10. And higher-numbered columns must always have "weaker" rules than lower-numbered columns.

Posted: Wed Aug 25, 2010 11:50 pm
by sweety123
Thanks a lot Ray and everybody. This is a big help :)