DSXchange

This sounds suspicious to me. Since jobs that connect to DB's and spool to sequential files should have very little load on the DS server cpu, as all the job has to do is spool output to a file, it seems strange to me. Now, you have a design of passive-->passive, which is a bad idea. You should stic...

I shall reserve my comments for private communications. However, your term featuritis is what I call "shiny objects". They dazzle the eye and distract the beholder. Wow! Auto-column derivation wizard! Cool!

After a few years you sometimes just wonder why you even bother programming it via DataStage. Now I did not even come close to suggesting this. I think a perspective must be kept and that not everything has to be inside the tool. Your toolbelt should have as many tools in it and your judgement shou...

Shawn, let's be quite clear to everyone out there that DataStage does not bulk load data. Its bulk loader stages either invoke the respective database bulk loader command to perform the load, or write the necessary control files to use with the command line bulk loader. In either case, DataStage spo...

Because the DS bulk loader stages have performance issues in that they re-verify the data content while spooling the load file. The stages are meant to make life simple for those not experienced with bulk loaders. If you have the skill to insure a proper load file, then skip using the Stage and just...

If what you are saying is that you have no power to change the hash reference lookups, then make your own! Take the faulty hash lookups and create a corrected set for your job at runtime.

Any logic that prepares the hash file has to first get the primary key value into the right condition. In the jobs that load the reference data into the hash file put onto the primary key column derivation the necessary logic to standardize/homogenize the data. Then, you have no need to do in the tr...

How is the job designed? Is the stored procedure being called in an OCI stage, or are you talking about a Sequencer job that is executing a Command stage that executes a stored procedure? Are you sure that the stored procedure has not begun execution? Still highly confused as we do not have the nece...

If you have the means to detect deltas in the source system via an last update timestamp then by all means use it. It allows you to extract only the row necessary for processing, thus reducing network and pipeline traffic. Your issue is if you need to pull the parent again. Since your delta detectio...

We need a lot more information. What kind of jobs are hanging? Are they having database connections? Can you describe the condition of hanging? Are you finding that the job is running, and never finishes? That the link statistics stop changing? That the underlying unix processes disappear? Are the j...

Okay, but we're limited on this forum by the ability to show graphical design flows. You need to look at the job designs in the manuals and online help, they show how to construct graphical designs. It also shows how to fill out connection information, as well as the join expressions.

Search this forum, it's been covered in depth how this stage works. In a nutshell, it writes a data file (very slowly) and a control file. You will need to execute sqlldr and give it the control file, credentials, etc. to load the table. One good suggestion is a generic script that accepts a control...

Have you been thru training? If not, have you looked into the tutorial? If not, have you read the online documentation available under the Start button? I'm sure you can find examples in all of the documentation and manuals that show and describe how to do all of what you want. If you have specific ...

What do you want to know? Have you read your documentation available under the client software on your Start button?

If you wish to stay within a single job, you might consider a fixed output file name and use an after-job routine call to execute a script to do the database fetch and copy/move the file under the variable name.