OVMS: Significant changes in ORAUSER.COM for Oracle release 10gR2 (Doc ID 391663.1)
Hi All!
IHAC that ran into a case sensitivity issue. In 9i, a batch run passed along a parameter value that was lower case.
However in 10g, the value got changed to upper case, and ended up being stored into the database as uppper case, but the customer
does not want that behavior. I referred them to the document 391663.1. However, they have come back and asked whether not making this
change will affect "other oracle processes, like SQLLDR", where the new behavior is desired. Not sure how to answer that question.
Seems like the just need to unset the 4 logicals for their batch run, maybe using a wrapper around it. They seem to want to have their cake