DSXchange

Or simply set the 'Update action' to 'Truncate then insert' if the clearing of the table can wait until just as the job starts.

Andy, you might want to check out this thread on setting the debug option on 'dsrpcd', it may help you figure out what's going on when it doesn't start.

Too bad.

Did you look at the other thread? Any chance of trying the 'CALL' statement as custom SQL or in a 'before' tab? Seems like you could add a bogus select to the actual stage, select 'sysdate' or something out to the flat-file so that DataStage is happy.

Perhaps you can make use of a 'trick' people have been using with Oracle and stored procedures? It's detailed (amongst other places in the forum) here. You could always take the logic from the stored procedure and build a DataStage job to accomplish the same thing, I would think. That would put the ...

It works just fine... as long as it is the only process writing to the file.

If you are building these two outputs simultaneously, then you must write them to two distinct filenames. After the job completes you can combine them however you please.

denzilsyb wrote:In the sequential file stage, use the 'Append' option, instead of the overwrite option.

Only if two jobs or steps are involved!

Yes, a second file can be appended to the end of an existing file, but people that haven't faced this issue before shouldn't think they can do this all at once.

How are you doing the 'concatenation'? Hopefully, not with two output links both trying to write to the same sequential file at the same time. That simply cannot be done. Write to two different sequential files and then (in the After Job arena) either concatenate one onto the end of the other or the...

I ALWAYS use a transformer between passive stages -- > BEST PRACTICE. I couldn't agree more. It is not only a Best Practice, but there are known issues in certain situations where passive stages - when directly linked together without a transformer - do not work correctly. Always use a Transformer,...

Post your Oconv logic. I'd also suggest defining it as a Timestamp in the OCI stage and consistently handling them that way.

Up to my knowledge I know that "we have to set Array size of a ORACLE stage to 1 in order to get the rejected records." -PLZ correct me if the above statement is wrong. Right and wrong. You'll still get rejected rows with an Array Size of something other than 1, the problem is it won't always log t...

kcbland wrote:DS started as an individual product at 3.5, and evolved into a suite by 7.1.

Wasn't it actually 3.1? That was the first version I saw... unless it was still something other than an 'individual product' at that point.

No idea, but I'd be shocked if it can't be done... unless one or the other is "proprietary". Any idea what database is under the covers of them?

Or he's actually (gasp! shock! horror! x2) actually working?



Either that or he's entered the Witness Protection Program and posting under an alias. Like Kim said - it's ok, we won't tell Teej. Join Us.

I am updating/inserting in a table with a single server Job (There are two target stages for the same table) - one with an update on one condition and another with insert with another condition. Both constraints result in two different targets. But the table(not job) gets locked. Hence the job hang...

But are you saying the table definitions change from load to load? I'm curious why you would need to 'import table definitions' each time?