DSXchange

You can change properties to force the Parallel job or its stages to run sequentially or override the config file setting to use a single node config file as Craig suggested or you could use a Server job instead of a Parallel job.

I think you would need to use Information Services Director for that.

Maybe it has to do with tracing? Tracing usually generates large files. Is there tracing enabled at any level?

I have that folder on 8.7 but it's empty.

Did anyone alter the DataStage.properties file in the parent folder?

Oh.

Maybe skp just needs to log in?

As a DataStage Developer, I always prefer to generate unique numbers directly within DataStage itself.

Any time you reach out to a database for whatever reason, it:

• - creates extra database I/O operations
  - adds complexity
  - slows down performance

Each option has pros and cons... That last option creates a potential ongoing maintenance headache and it wouldn't pass any sort of security audit but it would perform well and may give you just what you need.

I think it can be done in this way: - Ensuring database logging is at the level you need to capture all the SQL - Ensuring database privileges allow you to query the database log/audit tables - Create an extract job to query the database log/audit tables Exact details will vary with each database sy...

The IBM Support Portal has a number of technotes with that error. In case you did not already search on it, here are a few links... Is xmeta filling up? http://www-01.ibm.com/support/docview.wss?uid=swg21580174 Version 9.1 on non-English locale? http://www-01.ibm.com/support/docview.wss?uid=swg1JR46...

See this post also, in case you are interested:

ETL Statistics

I actually ran across an IBM technote for version 4, just today! Version 6 is definitely unsupported unless possibly someone has paid big $$ to extend a support contract since then.

It's possible. If you create a new test job from scratch, what is the result? Here are a few technotes you may be interested in, although I doubt either one is an exact match: Float data incorrect or corrupt in a DataStage job http://www-01.ibm.com/support/docview.wss?uid=swg21515626 Parallel jobs: ...

I tested that in 8.7 and got a result of 3.98.

What changed?

Run the same SQL outside of DataStage but on the DataStage Server itself manually via the command line, such as by using the Oracle sqlplus utility, and compare the times. Check if the SQL is doing any joins or using any WHERE clause that may be inefficient or causing full table scans due to lack of...