DSXchange

Much like Arnd, I suspect that the definition of the unique index changed when the four columns were added. Or it could be a data issue, one where you never had duplicate values before and do now. But I would verify the fields that make up the index first so you know what to look for.

That's a bit... confusing... and seems to be at odds with what you posted originally. :? So... can you post some specific examples? I know you already have, but now show us actual data - more than one record. Match that up with specific examples of what the end result would need to look like for eac...

What settings have you specified in the stage?

Talk to your DBA. That or stop trying to insert explicit values into the IDENTITY column.

This is Ray's hand-rolled function, not the PX one so I don't believe that advice would be applicable here. However, don't have access to that particular code at the moment, so can neither confirm nor deny with any authority.

I seem to recall the fact that there was some sort of internal change that made it so you couldn't go straight to 7.x from a version that old. Perhaps a first stop at 5.x and then the jump to 7.x was possible? :? And yes, there are a slew of new stuff that you're missing, Sequence jobs being the big...

Of whom do you speak?

allavivek wrote:so you are telling that in oracle null and empty string (both are having length 0) are same...

I was saying that Oracle considers them equivalent, converting one to the other - DataStage does not, however.

In Oracle, an empty string is converted to a null... they are equivalent. And an empty string would test 'true' as a null, so test for both.

That's a known, documented behaviour of those functions. Ray has posted a Server IsValid() routine that will validate dates, amongst other things. Perhaps he'll post it here, or if I can turn it up later I'll add it.

DBF is DBase, so there should be ODBC drivers for that. No clue what a "tot" file is. You'll need to ask whomever is giving them to you.

Or define it as a string in the file and convert it inside the job.

IS? So this is an 8.x installation, not a 7.x one as you posted?

That just means it aborted. What was in the log before you reset it that wasn't tagged green?

Then you don't have a generic "tnsnames" problem but rather something specific to the proc. So... how are you calling it? Are you certain of the tns entry you are using there?