DSXchange

Please do us all a favor and edit your post - there's a button to allow you to do that. I'm assuming your original code is properly indented - wrap all of it in Code tags so that it displays properly here as well. Just makes it simpler all around. Also, are there job parameters or arguments involved...

Bump up the Tracing level in the FTP stage to something other than zero so you can get more information about the problem.

Two things: There are two places in the stage to do this. The values are additive - for example, to turn on 1 and 3 set the value to 4.

Now you need a little script or batch file to do the actual call to sqlldr. Have a chat with your DBA if you've never worked with it before, they can walk you through the syntax and best practices. Once you've got it working outside of DataStage, then you can add a call to the batch into the appropr...

You have yet to mention the actual error you are getting.

And the read only issue in our production system can be worked around using the multiple job compile Don't believe so. From what I recall, you'll go through all the motions and then every compile will fail because the jobs are read only. You need to repromote them. All. A question about the "Get De...

That works fine in your development project but can't be done outside of it if you are taking advantage of 'Read Only' jobs when you promote. The promotion process does recompile all jobs being promoted, so if you find yourself in the position of changing a shared container (re)promote all of the jo...

There are specific ones for Oracle:

http://www.dsxchange.com/viewtopic.php?t=86747

Seq() is the inverse of Char().

You can have as many as you like.... within reason.

Have your DBA kill the Oracle processes.

You are probably thinking of this - the DataStage Shell Integration Utility over on ADN. I thought it was cool for a moment or two, but the problems that I had with it far outweighed any utility I got from it, so it was uninstalled fairly quickly.

Ogmios should be along soon to let us all know how easy it is to decrypt things in DataStage.

You can delete the file. The first job will still create it, even when set to append.

CLEAR.FILE is for hash files, not sequential files. People have mentioned that more than once here. You can either open it in a BASIC routine and then WEOFSEQ - Write an End-Of-File mark - to it which will 'clear' it - or simply delete the file. I almost hate to ask - why do you feel you need to 'c...

As far as I know (not really all that familiar with Windows servers) you still need to supply all of the 'normal' connection information in the stage - SID, user, password. The difference between UNIX and Windows is the latter has no 'dsenv' file to tell it which Oracle client to use. I believe DS t...