DSXchange

Thanks Ray!! we are going with required changes in 8.x

Hi, Recently we have migrated to 8.x version from 7.5 and one Parallel job got aborted with the following error message while extracting Data From DB2- Connector Stage and surprisingly it didnt thrown any error while Viewing the data from the stage itself. Fatal Error: Attempt to setIsNull() on the ...

Hi,

the posted info insufficient for the analysis, can u place some more info on abort message or logs.

thanks

just keep the filter/constraint in the base query itself.

hi, look like table got locked..please verify that..

hi ,

please use tr -d command in the sequential file stage..that could resolve the problem.. for the verification check the same command in unix using the following command.

tr -d '\r' <oldfile> newfile.

thanks..

Hi, while reading the return file use "tr -d" command on sequential file stage, for the confirmation just try the same on unix... you will get it done..

Hi, We need to extract data from SAP through BAPI based on multiple import parameter values, how to pass these multiple parameter values in BAPI stage? we have tried out by passing the parameters through a file, but its not fetching any results, is there any specfic way to pass the parameter values....

Saving the file in CSV format--open the XLS file and Goto FILE tab and then select Save As and then change the SAVE AS TYPE from XLS to CSV.

Reading the CSV file: Just mention the delimeter as ","

Sainath.Srinivasan,

I didnt have 7.X and I'm working on 8.0

Stages which involves Trasformations then called Active stages which are not called passive stage.

Ex: Active-- Transformer, Filter, Sort
Passive-- Load and Extract stages

Earlier I have used only name, but just now i cheched out with both name and IP, both were working.

Why do we need to mention Literal in Standardization stage, eventhough that we are working against specific rulesets?

Join: Sort and hashed the data on the join keys, if you are using the same key for the next level of joining then use SAME else clear the partion and resort the data on new join keys

It has to work, check the data just before the comparision.