DSXchange

Fine... however, you still have the issue of trying to fit a 39 digit number into 38 digits, hence the "is out of range for the decimal with precision 38" error. Have you corrected that yet?

Sorry, no idea what's going on. I work pretty much above ground. You're going to have to wait for one of the Grognards to come along.

Wow... didn't even know there was a VOC entry for that. All I can tell you is this:


If that helps at all...

Interesting... haven't had a need to use it at all yet, so wasn't aware it could pull that little trick on a person. Good to know.

I understand your issue. Never having had the pleasure of working on a Windows-based DataStage server, I've stated I don't know the gory details on how it all works. My understanding from hanging out here is that registry entries and environment variables control all there. Which home does your ORAC...

I don't know of any mechanism - outside of something deliberate - that would quote strings like that. Usually it takes a miss-configured stage, like a Sequential stage, to do so. Meaning, data is written out with 'normal' quots around the character fields and then the file is read back in either wit...

No, not just Designer - I mean actually shutdown and restart DataStage itself. If you were on a UNIX server, I could walk you through it, but Windows? The service? Services? [shrug]

Worst case, yes - ensure no-one else is connected and then reboot the whole dang box.

Not familiar with Windows Servers, but did you stop and restart DataStage after switching Oracle homes?

I'm curious how you 'compared the data between the source sequential file and hash file'. Are you saying that you actually see double-qoutes in the data fields when you click View Data in the hashed file stage? Or did you do something else to compare the two?

Not generating any rows may be exactly what you want. I typically do that for either zero rows with an @FALSE constraint or for one row with @OUTROWNUM=1 constraint. The former might be used to clear a hashed file or truncate a table, for instance - the latter to trigger something 'special' in an OC...

I doubt you need to switch to user-defined sql just to 'reference multiple tables'.

Too Much Information.

If I remove the to_char() in the query and read it as decimal in the source stage, the job aborts with the error: Fatal Error: APT_Decimal::assignFromString: the source string (265801360696340669727895557154445859481 265801360696340669727895557154445859481 265801360696340669727895557154445859481 26...

Yah, and I don't mean the bread.

We've found you need to take a 'least common denominator' path and that you should be using an 8i client if your lowest db version that you need to access is 8i.