DSXchange

i think you have tried to play with the .dsx file of the job and tried ot change the stages etc ? you need to examine the links carefully

run time column propogation................... RPC or use schema files to input metadata definition to the jobs. it worked for me :D

A segmentation fault occurs when a program attempts to access a memory location that it is not allowed to access, or attempts to access a memory location in a way that is not allowed (for example, attempting to write to a read-only location, or to overwrite part of the operating system) try to disa...

Well if its not dropping any rows should not be a problem. i would either suppress the warning from the director or write a shell script to replace these values.

p.s have u set the ulimit limits to unlimited for the same user as in the DS enviornment settings ?

did run the pre-prod job with the same date file as in the prod ?

How many records should be coming through if you run a SQL for it ? are they 153,027,176 or 153,027,180? how about debugging it by putting a remove duplicate stage after the source and then inserting it ?

What is your job design? any aggregations or joins?

Even though the target table is multiset the work table from which the data is select inserted into the target table is set table(This is a bug in stage). So my guess is that rest of the data is being dropped due to duplicate rows. Post the stats from the log file against this stage. it gives you th...

The dataset stores information pertaining to a configuration file and if that is changed the dataset will be corrupted so my guess to that would be a NO to all three.

The dataset stores information pertaining to a configuration file and if that is changed the dataset will be corrupted so my guess to that would be a NO to all three.

Trying searching "DSJ.LINKROWCOUNT"

which database are you using

Well there is no issue in TD when it comes to updating the UPI or PI. it wil do it and just redistribute the table. I think its the problem with the what is being specified in the update script by him which is giving an error. Are you generating the script or trying to use a custom one?

Check the "Generate Insert column names" option under the script tab and run the job again. should work fine.