DSXchange

I believe in Oracle Enterprise stage we can not use case statement Why would you believe that? You can use any valid SQL syntax. As to your issue, select the fields you need from tabl1 and then do the transformations inside the job. For example, your source SQL could be something like: select a, b,...

We'll need a better explanation than that. Can you provide an example of your 'columns' and what the output of your 'random sampling' might look like?

What have you tried so far? Which part do you need help with?

What happens to fields TB & TC when the counter is 2,3 or 4?

There may not be much specific experience in that regard here, why not take this issue to your official support provider?

Any news on this?

As opposed to what? Me, I don't really see taking this path and never have. That notification is the responsibility of the "job control", whatever is running your jobs or batches of jobs, be it a wrapper script or home grown job control code or your Enterprise Scheduler. IMHO. Save the &qu...

<cough> hitchhiker </cough>

Exactly.

Less overhead. You've already got a handle to the current job and you save forking a new process to spawn a shell.

Stick with the API and a BASIC routine there rather than shell out to the O/S.

Actually you can, that's one of the many things the "After Job" section of a job is for. When anything there triggers, all processes on the canvas have completed but if you checked the status of the job from there it would still show as still "running". However, a check of the JO...

Yes, he does. Open either one up and you'll see.

You would also need to migrate any custom (user written) Server routines for them to become available. That message implies that you did not do so.

Right... it's not something you'll ever "see", but rather something you must do an explicit check for. There is an equivalent in UNIX where the exit status of the last command is in $?

D'oh! Thanks for the catch... always thinking in hex for that kind of thing, it seems.