DSXchange

Conflated, then.

Look in the log for the event that contains the output from your Execute Command activity. Report back the error message that you see there.

I believe that patch is only needed if you use LDAP authentication. If you are using TD2 authentication you should be fine.

Two issues are being confused here. One is the performance of ONE Transformer stage, which was a problem in earlier versions but isn't any more. The other is the performance of TOO MANY stages (of whatever type). Every stage (ignoring operator combination) will generate an additional process; too ma...

What are you using to view the contents of the DB2 table? Do not rely upon DataStage's data browser (View Data) - it is notoriously bad when the language is anything but Amurrican. Try some other tool - even the db2 command itself.

Try forcing the Oracle SELECT stage to execute in sequential mode.

Named licences are not currently supported for DataStage/QualityStage Designer client.

Depending on which SFTP tool you are using, it may allow an "after" command that can be executed on the source site; if so, you could use an appropriate command (such as COPY or MOVE) to move the file to an archive folder.

You can resize the RT_LOGxxx table to use 64-bit addressing if this is going to become a real issue. That, and design jobs that log as few entries as possible - for example switch off progress reporting in Sequential File and Connector stages.

Make sure that all necessary ports are open in the firewall.

BI reports are created in a BI tool, and imported into Metadata Repository using bridges or metabrokers, for example using Metadata Asset Manager.

If you're sure (for example from the log) that the job has finished, clearing its status file from Director will clear the Running status.

Sounds like an ideal candidate for looping in a Transformer stage. Search for the next nn:nn:nn pattern, which signals the start of the next line. Or maybe search for the next colon character and parse around that.

This message usually stems from the fact that the Connector checks metadata in the job (design time information) against actual metadata (in the database), and alerts you to the fact that there are some columns not being selected.

Please note, too, that sometimes you have to specify nullable, for example when the input link is the outer side of an outer join or if you are effecting a full outer join.