DSXchange

Roll your own... or use it in your Oracle source sql.

There's no such thing as Varchar(11,2). Strings don't have a scale.

If you need to trim something, it would make sense to use the trim() function for that, yes? It defaults to space but you can override that and you can also override the default behaviour of "all".

Well, it did say it was for the OCI stage, not the Connector. It's been a month - well past time to involve your official support provider, me thinks.

Don't recall ever seeing a negative number in this context. Suggest you get your official support provider involved and also make sure (if you haven't already) that you are current on your fixpacks.

In your version, your only option is a client-side export.

And?

I assume because it is being sent as Plain Text... your only option.

No, that Oracle variable does basically the opposite of this. You need to handle the null and explicitly convert it to a space before sending it to the target.

Try using a semi-colon at the end of each statement.

Run the job on one node.

Ah. :D

Seems like you need to sprinkle more 2>&1s in there.

A routine will be more... fragile... IMHO. But do-able if you've ever worked with command line sqlplus and can handle all of its idiosyncrasies.

I've read here that the isx format is basically a zipped dsx, you might want to see if you can unzip it and then see how 'dsx-like' the result is. Or isn't.

You can set the 'null string value' for each field individually, however that option is probably gone when using RCP. Hopefully, others who've been down this road can offer advice.