DSXchange

Unable to create new process can also be caused by the process table being full, so that process IDs can not be issued. Another possibility is that your DataStage server was unable to contact the domain controller before a timeout expired, because the domain controllers or the network were too busy...

Well, if there's a line terminator, then there are too many characters in that line - your fixed width table definition specifies the width. When you're viewing the file using a UNIX utility, is line #32 longer than line #31? Does line #32 contain any other non-printing characters, such as a tab (^I)?

The queries you posted are "SQL" (Structured Query Language). Most databases use some form of SQL, hence the apparent familiarity. However it in no way means that a query executed in one database can access tables in another. There are products "out there" that facilitate such cross-database queries...

Then, what is the "load rule" in the OCI stage? Did your fast run load into an empty table and your slow run into a non-empty table? Try separating your load into "insert only" and "update only", or even bulk load if they are all supposed to be new rows.

A small correction. It is version 7.5x2 that runs on Windows platforms. Version 7.5.2 is a UNIX version.

INB Information Server with DataStage version 8.0 for Windows has allegedly been released.

Note that it's not just the .NET Framework; you must install Visual Studio .NET 2003 (at least the C++ compiler portion).

If you need help immediately buy premium service from your support provider. Learn the true cost of "urgent". DSXchange is an all-volunteer site. None of the posters is paid. They post as and when they can, unless they take offence at unreasonable demands and decide to impose a time penalty. Meanwh...

Of course not. How do you define a DSN? It points to ONE database.

Now read the error message again carefully and determine what's missing from DSN "WEITS702".

Add the missing line terminator to the last line of the file.

By definition duplicates are impossible in a primary key. Execute the following query in the source table:

If this returns any rows, castigate your DBA for failing to create a UNIQUE index on the primary key.

Set the timeout on a Wait For File activity to 01:00:00.

Don't know how "manually" in your subject gets involved in your actual question.

Thank you for sharing that. Personally I already knew it, but others may not have.

The hardware you have will support multi-instance server jobs with less demand for resources than parallel jobs. There's no way I can suggest figures without monitoring and measuring what's happening on your system. Some things are obvious: scratch space full means that you need to configure more sc...

If the business requires you to process sequentially, consider using lower impact server jobs.