DSXchange

What are they supposed to do? Who the heck knows, it isn't something he engineered or attempted to 'cat' together. They are why it barfed and I was hoping you might have a clue at to why the unwanted substitution is happening.

reena123 wrote:"X" is actually a sever job. Would that make a difference.

Nope.

reena123 also wrote:Please suggest as i have unique invocation id's, but still am facing this issue

Seriously, you are facing the issue because you don't. Check the logged error messages more closely... make no assumptions of uniqueness.

And how can they be 'loaded into the xml file' and yet not be written? Or does that mean the 'expected number of records' were written to the XML Ouput stage?

Usually an XPath problem but it could be any number of things. Not even going to guess without more information from you. First thing to do is exactly what 'thebird' suggested - have you checked the job's log? Any messages there that may shed some light on the issue?

Daddy Doma wrote:Thanks for your help Craig. I eliminated bunnies as the cause pretty early on , but your reply prompted me to double check

Perhaps one of the 'Old Grumblers' can enlighten us both.

And if you know about the bunnies, don't forget the midgets.

Simple - that's not a hashed file, it's a 'plain text' file inside the directory.

So, use vi or your UNIX editor / file viewer of choice.

There's not much difference, client wise, in the 'requirements' of 6 versus 7. The only thing I recall is 6.x will function on Windows XP Home but that is no longer the case with 7.x - it requires XP Pro. Other than that, you should be fine. In my opinion - upgrade to 7.5.x now. The upgrade should b...

kumar_s wrote:Just curious to know, if its production, shouldn't it be prod_edw.....

I think we have a winner.

Why would a Teradata issue trigger a call to what is apparently an Oracle utility?

As a guess, I'd say you've stumbled on some sort of 'reserved word' thingy and it is automagically substituting "_JOB_NAME" with UtilityAbortToLog... are you using that somewhere? Rather than burn a lot of brain cells trying to figure out why right now, what if you just changed the name of your para...

Ok. They don't generally happen at the Oracle stage, per se - they happen inside your database and can be captured in the Oracle stage if you like. Any operation that results in an Oracle error - and Kumar noted there are many - like constraint violations (unique, value or FK), metadata mismatches (...

Details, man, details. Not knowing what you are doing makes it really hard to offer constructive help. All we know is they are not getting updated, so it sounds like you are inserting (instead? first?) and that is failing due to a unique constraint being violated more than likely. Post details of y...

Sometimes things seem rude when all you've got is text like this. We tend to read all kinds of things into in, like the fact that all caps is SHOUTING. I we could see each other's faces and body language, some of this wouldn't be a problem. Speaking of problems, the other thing we'd like people to d...

How can we help with so little information? Why are they getting rejected? Why are you doing user-defined? That way only leads to the Dark Side...

Just noticed this is in the wrong forum - please post in the appropriate forum (General or PX) next time. SEQ1.JobControl (@X): Controller problem: Error calling DSRunJob(X), code=-2 [Job is not in the right state (compiled and not running)] Job X is not in the 'right state' because it is currently...