DSXchange

From what I recall, you don't use the $ with that function.

Triggers are database objects so you'd need to talk to your DBA for specifics on that. All I'm saying is you could perhaps use an insert trigger to put your data into a work table (rather than a flat file) and then drive any further processing from that work table.

What version of Oracle are you loading into? I'm curious if you client version matches your server version and if there is an opportunity here to 'upgrade' the client to a slightly higher version.

How did you get into this situation? Did you move jobs from another project into one that does not have the OE stage installed?

I have no knowledge of this stage, but if you can't find an explicit 'clear/truncate' option for it, you could always use your original job concept to do that using an empty source and then running your new job.

Define precisely what "read in the transformer" means.

What is your target? If it's a database, define your 'default' there.

Sheesh. When you kept saying "master job" everyone here assumed a Sequence job. You need to do a better job of explaining what exactly you are doing and what exactly your issues are. We spend too much time going 'round and 'round otherwise. It would probably help if you explained why you b...

qutesanju wrote:i checked it's not deriving all parameters from master to child when run one by one in series........however it picks all default parameters only

Sorry, but I honestly have no idea what you are saying here.

Ram, I wouldn't hang your hat on that variable being a magic fix for you, nor would I immediately jump to blaming RAC for the problem as it really should be transparent to any application / client accessing your production database. As a guess, I would say it is more the production data / volume rev...

It only takes the default if you don't pass in another value. Double-check what you think is going on because it can't be based on what you've told us.

Of course it doesn't. A zero sum would be supported, but how can it count nothing? So rather than counting occurances of the key field, send in either a 0 or a 1 and then sum the field. Of course, then you'd have to arrange the job to always send a 'zero' record to it and then (optionally) as many '...

Sorry, didn't realize that.

Think about it, the query will have to generate rows to have anything to write out. Perhaps have a pre-built target with all zeroes and update any that have values. Or check the output link after-job and cat a 'zero count' record into the file. Or go complete after-job as Mike suggested all those da...

So... it's not the "Insert/Update" that is taking a long time but the reference lookup to Oracle. And when you assign a new surrogate key value in the inserts, you want to capture those values in a flat file for "further processing". Yes? How enamored are you of this database seq...