DSXchange

This is the suggestion i got from IBM: InfoSphere DataStage: Problems when running multiple instances of a job from a job sequence, or from a script using dsjob Environment variable: DSWaitResetStartup When multiple instances of a job are run from a sequence, and one or more of the job instances are...

Check the data type for the ZIP column in the target table. Also verify what data you are feeding into this column? Is it integer, text, text with white spaces?

sAM

Andrea,

Where do we need to change these options? Can you be little more specific about this.

Sorry Craig.... Just going through the same issue.

Thanks
sAM

NOTFOUND works fine when performing lookup on Hashed Files but for the Table lookup it is always better to use the null check.

sAM

Vineet,

It can all be done by using a stage variable to store the previous value and populate this vale in the current Column.

But why would anyone like to modify the Amounts associated with Products in such a fashion unless this is some kinda fix.

sAM

It is quite hard to understand your requirement. Share some information on how your input data looks and what exactly are you expecting in your output.

Sample Data??

sAM

Why not transformer stage???

What is your source? In case if you are pulling the data from some database then you can perform this operation in your source SQL statement itself.

sAM

Hello Abha,

We went through the same Issue couple of days ago and found that there is bug fix (patch) available for this. Talk to you Serive Provider.

sAM

Nothing wrong here but change [%yyyy-%mm-%dd hh:nn:ss] to [%yyyy-%mm-%dd %hh:%nn:%ss] and try it.

Have you checked the function TimestampFromSecondsSince()???

I hope this will solve your issue..
sAM

There might be two seperate issues you are facing. ''OCI has fetched truncated data'' There might be some column in the source which is having column length greater than the one in the target. ''ORA-01002: fetch out of sequence '' I would recommend you to search the forum there had been few differen...

Simple solution will be to use stage variables. Try something like this.... Sort the data on your three columns. Initialize sVValue as 1 sVCurrent = COLA:COLB:COLC sVValue = If sVCurrent = sVPrevious then sVValue+1 else sVValue sVPrevious = sVCurrent And use sVValue in your column derivation of INT ...

Did you try using peek or flat file as output to test? I really doubt that there might be some tranformations which is causing this issue. Share you Job Design...

If your source already have it as decimal then what is stopping you to use aggregator for Summing those values??