DSXchange

The problem there is pretty obvious - compare the date example with the format noted in the message. They need to match.

You might want to open a case with your support provider, it may be more of a bug with the stage than any need to tweak the compiler options.

Your support provider, of course. That would be the official source for compatibility information like this. Keep in mind that Oracle ended their "Extended Support" for 8i at the end of 2006 so there's probably not a lot of guaranteed compatibility here.

You might want to explain what kind of ".fifo lock" issue you are having.

Split from this post.

I don't have much personal experience with 11g yet but I have been told that there are... architectural... changes in it. You've moved off into what I would consider DBA territory, do you have one there that is familiar with 11g and can help you understand what you are seeing? Otherwise, I'd suggest...

Missed the Windows part of all this. I'd still suggest trying the debug instructions if you can, they still might help clue you in to what's going on. Sure seems to be specific to the 11g client but not sure why that might be. Worst case you may need to ping your official support provider, see if th...

Let me repeat his question in full, emphasis mine:

ray.wurlod wrote:Where are the databases in relation to the DataStage engine machine?

Are either co-resident with the DataStage server?

Report that as a bug. I haven't used the latest versions of XML but from what I recall, all of my previous experience matches what Ernie noted and what it sounds like you were expecting: empty string = empty element, null = 'missing' element.

I'm not quite sure as I don't recall having to "register" anything ever. :? If you need to install optional plug-ins, you do that be repeating the installation of the server component. It will detect that you already have that version installed and default to maintenance mode, where one op...

Nice. Looking forward to the "longer posts", Vincent.

Sure... and by "integers" I just meant a brain-dead conversion to a YYYYMMDD formatted number.

Me, I would check with support on that one.

Double-check the NLS settings on both databases.

From what little I recall, you may need to convert the dates to integers and then back to dates afterwards...