DSXchange

As mentioned earlier, Billing Date should be part of your Aggregation Key group. But technically, if you want to leave out one filed on the aggregation and want to join it later, you ll have to do it literally the same. You ll have to use the Join (or other Stages to join) the filed from the source ...

If you want to aggregate based on ZipCode and Sate, Its not right to partition based on ZipCode,Stage and City. Unless you planned to have one extra round of Aggregation. "- Does the order of the sorting keys matter, as long as the order match each others?" You are good if both links match...

You will not be able to understand anything from the .o file even if you view the file. You ll have to check the corresponding Source code to get your understanding. .o are just the executables of the soruce code.

Did you check the record # 129012 at the field WS054_AUD_ADJ_FLASH_IND_2 for any abnormality?

Did you try Convert('(e)-','',Input.Filed)

If you had saved the metadata in the repository, you can do the Usage Analysis based on the Table Defenition.

Yes, Datastage will drop the columns from the Lookup internally and will Keep the columns from Main stream to the output.

So define only those columns that you wish to assing as key and Values in the Change capture stage. And let the other columns to propagate.

Both would exit the Client and close the client connection.
So shouldnt really make any difference.
But did you find any?

You would need to try to ensure that the locations of your dataset descriptor does not match to the data file you are removing. You wouldn't want to delete data that someone is dependent upon. Most environments will have a handful of environmental vairables used to direct the location of the descri...

Doesn't the below lines give you more information? Take a look at the record 27 for the field "IP_PORTFOLIO", and see if that fits your metadata defenition. seq_src_PORTFOLIO_LKP,0: Delimiter for field "IP_PORTFOLIO" not found; input: {0d}, at offset: 0 seq_src_PORTFOLIO_LKP,0: I...

Are the underlying jobs multiple instance too?

As said earliar, check the bad records from ora.6032.14000d.0.log.bad or check the log file to see the exact error message.

Try adding a dummy column in the references. And you can use the dummy column to check the lookup condition. If you cant add the dummy column... Then, you may need three lookup stages. On failure of the first lookup, reject the recorcs to second. On failure of second lookup, reject the records to th...

You were trying to read a Dos file with Unix format.
Try to give DOS as Record Delimiter.

There error that you getting is from teh Sql Loader.
Check the log file specified.

ora.4728.827000.0.logora.4728.827000.0.log