DSXchange

Commands like xcopy will create the target directory if it doesn't exist. Also check for command line switches, move has a "/Y" to automatically answer prompts to overwrite with a "yes" for example.

How can anyone other that you and yours answer that question with anything other than "depends"? Ask whomever is responsible for the design of that table.

An unbound number in Oracle, one with no precision/scale, is stored in floating point. PX sees that and issues the alert, regardless of your metadata or the games you play in the SQL. I'm not sure there's any "solution" other than to demote that with a message handler. :? Happy to be prove...

What database? What stage? Try with an Array Size of 1 and see if that works in your design.

Right-click on "My Computer" and select "Properties", it should be listed right there on the main tab/page.

There was only one other post here that mentions that message and it went unanswered, so you may not have much luck. Perhaps no-one else has experienced this issue yet. :? All I can offer is standard advice. Make sure you're all patched up, the early versions of 8.x have a ton of patches available f...

Perhaps if you posted the actual errors you are seeing it would help. There's no fundamental problem, per se, other than all the normal reasons to not use one.

Still, same advice applies. Do it for every field that needs it, 4 or 400. Or perhaps back up in the source database instead, with something like NVL for Oracle. In any case, handle it appropriately regardless of the number.

Sure, that could be another option - forget the stage and build the tags "manually" in a transformer. Perfectly fine but ugly and perhaps dangerous, adding the <CR> and handling any data that need to be translated on the way out like & or < or >, for example.

It's not fixed-width. Declare it as a normal csv file that just happens to have a single column in it.

Thanks Vincent.

This may be because, even though the job is aborted, the query in OCI stage may be running in the Database. Nope. The compiler will have no clue nor care if there is any leftover query running in a database somewhere. When you run the job it may care, but not when you compile it. Now, normally when...

Search the forum for that name, it has been discussed here quite a number of times. Also, find the routine (in the sdk branch, I believe) and double-click on it. Vendor supplied routines are typically documented in the "Long Description" field and worst case you can work it out from the so...

You need to use the 32bit Oracle libraries in "lib32" with DataStage rather than the default 64bit ones. And by "use" I mean reference in your "shared library" environment variable in the dsenv file.

Why, yes it is. Since the question was about contrasting the two approaches, I kind of ignored the Server job type / posted forum part. Perhaps that explains the "didn't get anywhere" comment.