DSXchange

Are you supplying any values to the stage that contain "special characters"? If not, please provide details as to how you have it configured in the job. I'd also be curious if this is the first attempt at using that stage in your environment or other jobs have used it successfully and just...

Basically, a continuation of the conversation attempt started here that you haven't responded to.

It needs a client and the client leverages the tnsnames.ora file. And 'SID' in your case really means the TNS alias entry. From the thin client docs: B. Configuring an Oracle DSN The Oracle ODBC driver configuration has changed slightly with each newer version of the ODBC driver, but there are only ...

I'm going to guess you're in need of a patch - are you up to date on fix packs? It could also be an issue with your specific 11g client version but you'd need to contact your support provider to see if that is true.

Let's start by getting you in the proper forum, the FAQ Discussion forum is for something else entirely. Secondly, why do you think these are "special" characters and they need to be converted to "normal" characters? They're part of your customer's data and should be loaded intac...

You seem to be missing the closing } for 'node02'.

How can we say if it is 'correct' or not? Check the explain plan. Run it. Check the results. Then you'll know if it is correct or not. A join is still a join no matter if it is left, right, inner or outer, regardless of the number of columns you are joining and it will may need indexes on the join c...

Check with your DBA, that error just indicates a problem with your tnsnames.ora entry.

Of course, just having some fun with your long standing aversion to jobs that purposefully abort themselves.

Me, I would never trust anything like this to an implicit conversion... explicit all the way, please. That or look to see if you can use math to effect a solution so no conversion is needed.

That or tell us what "not happening" means in greater detail.

Also understand that if your export is in XML format that you'll need to WAIT for the importer to first convert the entire thing to a dsx before it can perform the import. Unless that's no longer the case?

Ray's jobs don't abort.

That's good to know... that was how we always handled things back in the day on the Server side - an All or Nothing load with a transaction size of zero. DBAs weren't always fond of it, however and from what I recall it wasn't supported initially on the Parallel canvas. You only had the two Oracle A...

You'd have to test it to ensure you'd get the behaviour you are looking for. I'm afraid the Connector will still be issuing intermediate commits and thus your ROLLBACK would only be a small portion of the processed records. And the job may still abort...

Your problem is going to be the fact that using the Oracle Connector, the job must abort to effect the rollback - and that only of any uncomitted records. If you want full / atomic level control over when commits and rollbacks happen, AFAIK you need to use ODBC. That stage allows you to issue specif...