DSXchange

Our POC on pushing referential integrity checks on the database doesn't seems to be working So are you saying that you are allowing the database to police your RI constraint issues without you making any attempt to ensure you are not violating them before the actual database operation? Bad Idea. As...

Excatly... without a complete explanation of how exactly you are trying to run sqlldr and what errors you are seeing, we can't help much.

In other words, they are not ignored but are used for the run. And the Sequence will log a warning if they are found to be different when restarting from a failure checkpoint. If you reset the job so that it starts over from the beginning, it won't bother with this check.

Do you belive the subtle difference in version could be causing this problem ? Yes, indeedy, that is your primary suspect right now in my mind. I've been down this path before, 9.2.0.1 is notoriously buggy. It can work fine for the vast majority of your jobs and then find one certain something in a...

They don't have one.

You don't need admin rights to unlock if you can log on as the user that holds the lock... can you?

No, the 'access violation' has nothing to do with the database per se or any lock on the table, that would generate a normal ORA error. It's typically a code issue, a bug in the Oracle drivers / client code or DataStage. Let's start with Oracle. What Oracle versions are at work here - the database i...

No... I did not suggest you do anything with a custom stylesheet except to confirm that you were, in fact, not using it. And you cannot load your 'XML file' there and expect it to work. If you aren't familiar with writing XSLT then stay very far away from this option. You generally don't need to wo...

Same session, yes - but you've got no way to pass any information between the two portions. You'll need two jobs.

I get the impression they are trying to read it and failing. Can you do it in two jobs / passes - one for each TRANS types?

You would only have problems with 'custom stylesheet information' if you specifically added that in the stage. Did you? Is there such a thing under the Output / Advanced tabe - 'Use Custom Stylesheet' is checked and you can see one there? If not, then you've got a plain old mismatch between your XPa...

kaps wrote:Does it work differently in DataStage ?

Just to emphasize the point - no.

WISD... formerly RTI, formerly SOA... you can expose a job as a web service.

Reset the aborted job and let us know the contents of any 'From previous run...' log entry.

Odd, I do that here under 7.x. Try:


and see if that works.