DSXchange

Well, that was helpful. And the 'whole project' comment is untrue. I've been using it exclusively since the 4.x days of DataStage and have yet to see this behaviour... or at least I would have said that until a couple of weeks ago. Now I have to amend the statement to say that it has never happened ...

roy wrote:(In Oracle plugin there is a column comment check box but I have yet to find a table with comments for the columns)

There is? Now there's something *I* have yet to find!

Nope... only a single file at a time. For what you are contemplating, use plain old command line ftp.

Remove the 'Call' statements from your code where you assign the output to a variable. For example, the first one should look like this:

Am I incorrect in the way that I am trying to use a sequential file as a table ? Totally. As far as I know, only Oracle has the ability to treat a flat file as an 'external' table. In any case, they aren't close to being the same thing. If I am then how can I use a sequential file as an input table...

Yup, this one as a matter of fact. Please don't double-post, go back to your original post and continue the 'conversation' there.

DATAPATH,SYSTEMNME,JOBNAME are the parameters to pass inside the shell script ,I had set their values as STAGE VARIABLE inside transformer. This is the crux of the problem. Stage Variables are (as their name implies) local to the stage in which they are defined and used. Outside of that stage - or ...

I doubt the second would continue on its merry way if it thought it had a problem creating the hash. You'll need to be very careful with hash lookups in Multiple Invocation jobs. If all of the Invocations need to share one common hash lookup, then you would be better off to create it in a seperate j...

If you just enable that check box and don't change any of the 'Options', then no - there is no difference. What it does give you the ability to do is two-fold:

1) Delete and recreate the hash file each run.
2) Change the default values used to create the hash file.

Narasimha works with me, hence my ability to somehow magically figure out what was going on. Turns out to look like a bug in our version of DataStage. All we had was a Column Generated query in a source OCI that joined target to staging to build an appropriate subset of the existing keys for a hash....

Show him what's he's won, Johnny! [applause]

Mike wrote:I think you might need to install the Oracle 9i client on your linux machine. I don't think the 10g client is supported yet.

10g is supported in 7.5 (which the OP has) so that "shouldn't" be the problem.

Can any one tell me how to release multiple jobs. if i give the sequence to be relased, the job name given inside the seqeunce is not atomatically changing to the released version of the job. can any one suggest me a proper way how to release the jobs... Ray noted that you need to select all the jo...

And set the job to Abort after X number of Warnings... with X being a number significantly smaller than 27,000.

And Ken, since two warnings are logged for each pk constraint error, that's more like 54,000 warnings to the log.