DSXchange

Sort of. Make sure you understand that NULL and an empty string are not the same thing. Have you tried using either the IsNull or IsNotNull functions as appropriate?

Out of curiosity, are you trying to check for "empty" columns and if so, what exactly does empty equate to in whatever you are checking? I'm wondering if you are looking for an empty string when they are (or can be) NULL instead... which are not equivalent.

ffsw13 - did you get this worked out?

So... how exactly are you attempting to change the format? Does it involve an actual timestamp field, perhaps one that doesn't have microseconds enabled?

Exactly... an Oracle NUMBER with no precision or scale is stored internally as a FLOAT.

I hear you. I spend more years than I'd care to mention doing COBOL on minis and then many after that dealing with MF files, EBCDIC, packed fields, etc. Survived Y2K with the goofy "packed dates" we had to fix everywhere... trying to recall the specifics but years ago they had decided to s...

Gently it is, Franklin.

For a timestamp column, you don't need "steps 2 and 3", they are all about a string as the target. You need to look at the StringToTimestamp function.

So... do you actually need to convert it to a timestamp or to a string, an external representation of the timestamp's value using the format mask you posted?

Okay, good piece of information to know. Then as noted, your project (or projects?) have some level of corruption in them. Let us know if the tech note helps or not...

wpkalsow wrote:I view the "in the documentation" as a total waste of everyone's time.

Really? Okay. Not really sure what you were expecting then after making your "source code" comment. And good to know my statement wasn't all that helpful or informative to you.

I am wondering if the CC_OraPartitionedTableHelper.cpp at line 1887 is attempting to select from a system table or view that I may not have access to. No access to the source code... That was my first thought as well. No need for any "source code", from what I recall the grants needed are...

Guessing your client install is corrupted unless this happens to anyone else as well. If it's just you, I would suggest a re-install of the client.

There's no reason to import the whole dang thing. Cut the size down, create a new file with just a single set of properties, a single example of the data and then import that.

FWIW, Oracle does.