DSXchange

No, the installer puts everything in place, and then you have to run a script (LicensingServerAdmin) to tell it what you're actually entitled to. The script is not available until you've installed fix pack 1.

Yes, that concurs with my experience.

Thank you. I guess had you mentioned that "minor fact" in your original post we may have gotten to the solution sooner.

Why not be more patient? Column analysis can take a long time, particularly if there are many rows to process. I have had column analyses run for most of a weekend. Is there anything in the logs, including the DataStage Director log in ANALYZERPROJECT project, to indicate that the process was experi...

Does the job log show the actual SQL statement that is being executed (or attempted to be executed)? In particular, was the parameter reference resolved?

Moderator: please move to Enterprise Edition (parallel) forum

Once it's there we will provide an answer. Meanwhile do some research on the restrictions of writing to Sequential files from DataStage and how parallel jobs are executed (particularly contrasted to server jobs).

The after-stage routine can certainly read a file. Research in the DataStage BASIC manual for the OpenSeq, ReadSeq and CloseSeq statements.

That's good, but you can't use stage variables in an after-stage subroutine. They're out of scope by then.

Please supply the exact error message. The one you have given does not look like an Information Server error message. Do you have other security mechanisms - even Windows ones - in place?

INSERTs are always slower than bulk loading - the former carry the whole transactional overhead that the latter don't.

Things like checksums can be (are) best done in DataStage rather than QualityStage. The two can, of course, be combined.

In 8.0/8.1 it uses xalan parser which requires the entire XML document to be loaded into memory, so that you're limited by the amount of available memory. In 8.5 it uses a really clever streaming approach (not certain which parser, probably a purpose-built one). And the new XML Transformer stage is ...

A closer reading of the error message would have told me that.

Not possible. Use a message handler to demote the warning to informational. Or stop using unbounded VarChar data types.

You've run out of (virtual) memory. Try using a lower array size.