DSXchange

Could THIS be your solution?

On what basis did you check if there are duplicates? Is it not possible that there are multiple records for the same value of your lookup keys?

Never mind. I got the answer here. FastTrack is the way to go!

Hi,

I know that FastTrack can create DataStage jobs from mapping specifications. I was wondering if there is a way to generate mapping specification from DataStage jobs. I cannot see any direct solution in FastTrack but please let me know if there is some work-around to achieve this. Thanks

I think the job is functioning as expected. The sequential file did not get created because you flagged the job to abort after 5 db rejects. If there were less than 5 rejects(in which case the job wouldn't abort), the file would get created. You may want to set the abort after rows property to 0 to ...

Thanks Ernie. That explanation was way better than all the documentation I went through. Will try my hand at it and get back.

The sorting is not meant for you to view everything in sorted order. It's meant for certain functionalities to execute correctly in an efficient way (e.g. Aggregations, Joins, etc)
If you want to view sorted data, you should consider collecting data from all the partitions and sorting it sequentially.

If you're using the 4 node config file for the job, both flows will run on all 4 nodes unless of course you are applying node pool constraints.
Just think of 2 different jobs with the same configuration running at the same time!

Bulk loading is a database specific concept. Datasets reside on the same server as Infosphere. Whatever data is available is written to the dataset's data files.

Wouldn't the convert function solve your problem?

Yes Ray. It's just that the solution proposed earlier stated the need to generate a new column in the modify stage (TempKeycol) which did not work. When however we used the same name via a parameter (as you can see above), the solution worked. We played around with what you had earlier stated. So th...

Is it possible that there are conditions mentioned in the constraints section of the transformer?

Faced a somewhat similar quandary while trying to get a key to perform a generic delete. Reading through this might help. In the end, the solution to my problem was rather simple.

DELETE FROM #SCHEMA_NAME#.#TABLE_NAME# WHERE #KEY_COLUMN#= ORCHESTRATE.TempKeyCol My colleague came up with a rather simple solution just slightly tweaking the solution involving the modify stage. Instead of generating a new TempKeycol, this is what he did in the modify stage Specification=#KEY_COL...

I am also inclined towards a possible deadlock at the database (assuming of course that she's extracting/loading relational tables) due to open/abandoned connections. But unless she gives more data, it would be hard to put a finger on any solution.