DSXchange

... and is listed in one of the manuals.

I am assuming they are saying they want to bind all of the columns in the stage to the insert DML but only a few to the update DML. From what I recall that wouldn't fly in the older Oracle stages as they want all columns bound all the time. ODBC didn't care but native OCI did.

How about sharing your error?

zulfi123786 wrote:are these overriden by values provided in the ODBC stage when it actually connects?

Yes.

Thanks... you might also want to edit your 'from' database.

You posted in the Server forum and marked your job type as Parallel. Which is it?

Simple enough to test that yourself and see.

I for one have no clue. However... is your C++ version actually "too recent"? In the last month have you involved your official support provider?

bala_135 wrote:My approach:I am changing the write mode from insert to upsert in my oracle connector stage .Writing an update query that will only update the audit columns as to updating all the columns.

Is this even valid? In older Oracle stages it would not be, hence my question about the Connector.

Open the parameter helper in the Job Activity stage for that field, one of the options it will show you is the output from the Routine Activity stage.

Why are you piping "mv" and "sftp" together? The former won't move anything between servers and the latter needs more information to work. Use "mv" if you just need to move it to a new directory on the same server, use "sftp" to move it to another server.

With no Access installed this would have never worked. Did you ever do the google search I suggested?

Not sure what you downloaded but it wasn't trang-20030619.zip which is all you need... and it contains a local copy of the HTML manual.

15 fields? With only five commas in what you posted? Color me confused.

OK.

What's next? Will you be posting one that does relate? If not, I'm just going to stick my "use a lookup" response from earlier.