DSXchange

Vincent - I've done 3 8.7 installations so far and have found the same thing. While the documentation is available online, I only have a 4800 Baud connection at my flat so that isn't any help at all, by the time I've downloaded a single help page I could have taken a bus, then a train, then walked t...

It looks OK at first reading. What if you removed the first "(" to ")" group and recompile/re-run; does the error go away? Are the column names correct? Continue to remove elements in the where clause until the error goes away.

I'm not sure about the metadata workbench in this case; if your table names are not hardcoded but parameterized, then you could get the table names from the runtime job logs.

The programming on how many warnings to display at runtime is in each stage and I don't know of an environment setting that is read, I believe it is hard coded in each stage. This would be worth asking your support provider and I'd be interested in learning if there is a central setting somewhere. I...

Since table names can be parameters there isn't an easy generic way to do this. If you always use the same table column definitions then you can see where that has been used (but it won't tell you whether as source or target). I would think about doing an export of the project into either .dsx or .x...

Let's start the ball rolling with: StageVariable SvInteger INT(In.Col) StageVariable SvModulo MOD(SvInteger,5) Derivation: IF SvModulo < 3 THEN SvInteger-SvModulo ELSE SvInteger+(5-SvModulo) Addendum - oddly, I didn't see any of the other posts when I posted this and didn't realize that there had be...

Brad, first I would start and not partition the dataset "entire", just make sure that the reference to the lookup has "entire" specified, that makes it possible to use different APT_CONFIG files since the entire partitioning happens dynamically at runtime. I've found that often m...

From the Director utility "Data set management" or from the command line using "orchadmin rm <dataset>". Deleting the dataset descriptor file won't delete the data files but just cause them to be orphaned and use up disk space.

Try turning it off (kill the background process) and you'll see that deadlock in the DataStage locks will remain - at least until you start up the deadlock daemon...

Do you have the deadlock daemon running? You are in a fortunate situation, most of the time the trouble is getting rid of deadlocks, not generating them

So you need to change the date format from a string (your parameter) to another string (the SQL query) and that is why the DataStage job setting aren't affecting you.

In the SQL you should do a "TO_DATE(#DSJOBSTARTDATE#,"yyyy-mm-dd")"

How about doing a lookup on the dataset from your SalesForce data, using a "reject" output if the lookup isn't found. This "reject" does a "sparse" lookup to a database table. If that lookup fails, then write a new record to the same lookup table. Any subsequent lookups...

If row 100 isn't found and added to the dataset, can row 200 contain the "new" key or are these unique per run?

ujala,

I've marked my previous post as non-premium so that you can read it completely.

Dates and timestamps are stored in binary form during processing and have no format. It is only when importing or exporting that a conversion is made. Thus the question is at which point in processing are you converting from date to string? It is at that point that the system uses a conversion. Is t...