DSXchange

Please start your own post.

No. Not sure anything will actually "be replaced" but Connectors are new and will (I assume) be the preferred connection object going forward, once they get all the kinks out of 'em that is.

Don't see why not either. Go for it.

D'oh! Missed that in all the OCI talkie talkie. [face palm]

Still, advice applies.

That would be true if the 'extra' pesky <CR> was part of the record terminator, however they were allegedly 'at the end of a few fields' so a different solution was required it seems.

No, it probably just means the older version let you get away with the problem without busting you and the new one doesn't.

Two bind variables means you need to have two columns marked as key columns in the stage. Do you?

More of a scale than precision issue.

Yes, you should always include the credentials needed IMHO. Sure, there may be times or installs where it "works" without them but I think it's a bad practice to not "mention" them, doing so makes sure you have full control over all aspects of the process. And once you move up to...

Possible, sure. As I said, it really depends on the nature of your data and if a FLOAT/REAL is the appropriate way to store it (something you would have to tell us) then you'll need to find some way to deal with it. I'm not aware of any 'tricks' to keep those floating point issues from biting you in...

What kind of data are you storing? You said the scale can be "more than 2"... how much more? How about a NUMBER(x,y) with appropriate X and Y values?

Contact your official support provider. Me, I would never use a FLOAT for something like this precisely because of the issues that you are seeing that they can cause.

ICE wrote:If it is possible, please ask for me.

Sorry, not possible. You'll have to do that yourself.

We've changed "dsenv" file and the ".profile". I pointed them to the new oracle_home, mainly. We also tried that work around concerning the path to the oralib and oralib32 but it did not work. Hmmm... wondering about the "mainly" part and what "work around" y...

1) I would assume you missed something in your attempt to modify "all the config files". Can you detail out what DataStage changes you made to point it to the 10g client rather than the 9i client? Any reason you don't want to keep using the 9i client software? It should work fine for you, ...

Not sure what all possibilities might be but someone else is asking the same questions today, perhaps this would help:

viewtopic.php?t=132545