DSXchange

Have you installed the PACKs for Oracle Applications and PeopleSoft?

Try the /B switch with COPY. This implements a binary copy and does not append an end of file mark.

It's a Word investigation that you're doing. There's something wrong with the classification table (xxxxxx.CLS) for the rule set that you are using. Could be a bug out of the box - check with your support provider. I'm assuming here that you have not yet applied any classification overrides.

Does the job only have an MNS stage, or are there other stages as well? Are your data sources fixed-width flat file? Are you executing in file mode or stream mode? Are you executing via the DataStage plugin, directly from QualityStage Designer or via a script? Answers to all of these might affect th...

In the database is usually better, because the join can leverage any indexes that may exist on the join keys.

In what stage type?

No.

However, if you call DataStage jobs using dsjob from a script, you can re-map the standard exit codes within that script.

The same rules apply in DataStage as in SQL. Can you effect the correlated subquery in your extraction SQL, thereby saving your brain the grief of reinventing a wheel that already exists?

Search can direct you in the right direction. I answered an NLS_LANG question earlier today.

Welcome aboard. :D

You need to design what you've just described. The easiest way is for all jobs to load a staging area, rather than the final target. Then, only if all jobs complete successfully do you move the data from the staging area to the final target.

All error codes of the form 81xxx arise from the DataStage RPC mechanism. However, the underlying cause could be anything. That "the connection is broken" means usually that the connected client's agent process on the server (either dsapi_server or dsapi_slave) has terminated the connection. For exa...

Just got mine.

Do you have other file systems with lots more space? Create a configuration file that uses these as your disk resource, possibly in addition to what you currently have specified.

Or even whether the job monitor application (JobMonApp) is running.

NULLs can appear in the stream if a lookup fails and the lookup failed rule is Continue. The Lookup stage is then effectively performing a left outer join.