DSXchange

kennyapril wrote:so to get the rejected rows....Is it continue for the two conditions?

it should be continue for 'Lookup Failure' dropdown. anyway if you haven't given any condition in lookup link other dropdown 'Condition not met' value won't matter.

Use a reject link from the Sequential File stage that reads this file. Rows will be rejected if they don't contain the correct number of field delimiter characters. ... Ray's solution should resolve the issue. Could you please provide some sample record which is not getting rejected as per your exp...

use copy stage between reference source and lookup stage and have 7 output links from copy stage for lookup purpose.

I would go for join option and also would first extract the reference data in datasets in separate jobs.

execute below command on UNIX box Please change the dsenv path as per your folder structure.

After that you should be able to use dsexport command for unix session.

PhilHibbs wrote:I did that early on, but now I always put each lookup in a separate stage, so I can separate out the reject links and get clearer error messages.

that seems logical as well

not sure, but most probably this is coming due to the use of datastage functions on nullable field in transformer stage derivation. And you are not handling those null values coming from source. Let us know in case you have some other design.

You can also use only one Lookup stage with two reference links, having BUY data in one link and SELL in another.

you need to make the column nullable while reading data from source itself. Could you please check nullability of the column in source stage?

extract from designer guide:

To control the block size for key ranges, add the File Block Size property to the Options group, set this property to User specified, and specify a value for the block size

Are you trying to insert values in identity column? Could you please check your table's ddl script.

how are you getting these 4 new columns in your job? Are these columns being added after Join. If yes, then after join your input data might get replicated because of duplicate records coming from secondary source. but it all depends upon your answer of my first question.

In datastage 8x version, we can delete datasets(descriptor and their corresponding data files) using orchadmin del <dataset_name> ...not sure about version 7x...but u can give a shot...

Thanks
Nitin

Hi Subrat,

If record is already present in your target table, then in anyway, table integrity constraints won't allow you to insert same record again in that table and you should get integrity constraint violation error in you job.

Thanks
Nitin

Hi Aditya, I guess, you are trying to find the max value of date column after the join operation. This is what, being depicted by SQL query as well. Use Rdup stage after filter stage with data sorted on Date column key as secondory key(business key being primary, previous join key in your case). Reg...