DSXchange

With the installer you also get a utility that automatically converts your Enterprise stage types to equivalent Connector stages.

To specify a values file use

Anywhere that (a) has enough space and (b) is not on the root file system. Avoid /tmp too.

or depending on the result you want.

This is the raison d'etre of the Dynamic RDBMS stage. One of its properties is "database type".

^Z is the DOS end-of-file marker - it has no particular meaning in UNIX.
Although you should not need to, Convert(@TM,Char(10),TheString) will do the trick.

No, the @FM character is automatically converted to UNIX linefeed by the DataStage internals. Check the file with a non-DataStage text viewer. Also make sure that your metadata contain just a single VarChar field when writing.

You tried to do too much. Try:

This is from memory, but there's probably a shortcut to the appropriate Oracle library directory that may need to be pointed to the correct one. Check, too, that the Oracle environment variables such as ORACLE_HOME are correctly set.

Which, in turn, means that you have probably specified the wrong delimiter. Did you import the table definition for the file and load that into your job design (including Load on the Format tab)?

DataStage has no limit, but most database servers do. If you import the table definition it will give you the correct data type, whether it's VarChar or LongVarChar.

sqlplus has not returned an exit status of 0, which means it has had a problem. Try redirecting stderr from the sqlplus command to a file that you can inspect subsequently.

Complex Flat File stage.

Your log has become corrupted because it has attempted to exceed 2GiB in size. Clear the log file and try not to generate so many events.

Comma.

CSV = "comma separated values"