DSXchange

I had to search on that one... and found "CentOS developers use Red Hat's source code to create a final product very similar to Red Hat Enterprise Linux." If your exact OS and hardware (system requirements) are not listed on the IBM web site then you can expect to have problems that no amo...

Since it sounds like you're moving data Oracle to Oracle without any transformations, another option is to setup, or have your DBA setup, an Oracle database link and move your large SQL outside of DataStage.

I found many years ago when truncating/loading into Oracle, it performs significantly better to fully land the data locally to disk in a first job, and perform the truncate/load separately in a second job. Try breaking your job into two, using a Data Set stage as job1 target and job2 source. If you'...

With the "Insert then Update" setting you would need to set the commit count (record count) to 1. You have it set to 5000 so that may be causing problems, unless the connector is smart enough to override that setting to 1 in the background w/o telling you, which it may or may not be doing....

Yes, you can add it. That setting is for the number of seconds the driver will wait to establish the database connection. The default is 15 seconds. It does not have anything to do with individual SQL statements timing out during an already established connection.

Not sure what you mean by my understanding of it. Like I said, if it's in quotes, it was quoted from product docs. Anyhow, I tested out the wildcard option in the URI so that after the path my filename wildcard was *test*.txt where I had 2 files matching the wildcard. Much to my surprise, it finishe...

I would leave every Peek stage's partitioning setting as (Auto), which is the default. Maybe my imagination is limited, but I would imagine that the only scenario in which to alter the Peek stage's partitioning setting, is for learning purposes to see inside each partition, as in how records could c...

Maybe it depends upon your weekend. :D

It should be possible with custom or generated SQL. With custom, try prefixing your columns after the equal signs with "ORCHESTRATE." so that DataStage can know substitute the column values in, as in: ... WHERE dq_ExceptionKey = ORCHESTRATE.del_ExceptionKey AND ... With generated, you will...

I guess when you removed unprintable characters, that included line terminator characters too, so your record delimiter was gone before the stage read the tr output.

Ray noted that the Checksum output data type is Char(32), and Chandra's example includes a few 's' characters which are not hex, so I'm not sure if that was typed in randomly or as a copy and paste of a real Checksum result. What's described (hex only) is the same as a Universally Unique Identifier ...

That sounds like a new topic to me. Did you try any of the above suggestions for this topic?

Details are in the Administration Guide. The script in the default path on Unix/Linux is:

/opt/IBM/InformationServer/ASBNode/bin/NodeAgents.sh

Options (from 8.7) are:

start|stop|restart|startLogging|stopAgent

What partition Datastage will choose for Peek Stage if it auto? Auto partitioning is a fine choice especially for the Peek stage. And by default Peek will write records to your job log per partition. If you explore the Peek stage options then you will find options to limit the Peek output to specif...

Some functions like Connector stages' View Data use connector services provided by the Node Agents, so if you've only recently updated dsenv and only restarted the DataStage Engine, then you still need to restart the Node Agents before everything will hum nicely. Have you restarted all server proces...