Oracle itself doesn't need double-quotes for "special characters" but you need to use them to break the rules for what is allowed where. For example, you can use a # anywhere in the password except as the first character without needing to quote it. However, if you want to use the # as the first character you'll need to always quote the password for it to work.
I'm thinking this is a DataStage specific issue as those hash signs have special meaning. I'd wager that any other special character would work there, just not that one. Any chance you can test that?
-craig
"You can never have too many knives" -- Logan Nine Fingers
chulett wrote:Oracle itself doesn't need double-quotes for "special characters" but you need to use them to break the rules for what is allowed where. For example, you can use a # anywhere in the password except as the first character without needing to quote it. However, if you want to use the # as the first character you'll need to always quote the password for it to work.
I'm thinking this is a DataStage specific issue as those hash signs have special meaning. I'd wager that any other special character would work there, just not that one. Any chance you can test that? ...
Good to know, thanks for posting the link. Pretty much just wanted to say that Oracle itself has no such need, so it must be something specific to the way the stage is implemented.
-craig
"You can never have too many knives" -- Logan Nine Fingers
