Discussions
Categories
- 196.9K All Categories
- 2.2K Data
- 239 Big Data Appliance
- 1.9K Data Science
- 450.3K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 545 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.6K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 441 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
ManagedDataAccess and NChar Literal Replace option

Hey all,
I have noticed a bug/difference in behavior between the unmanaged and managed ODP assemblies. Using the unmanaged assemblies, string literals marked with 'N' and containing unicode data save fine, at least with the "ORA_NCHAR_LITERAL_REPLACE" environment option set to TRUE. However, with the managed assemblies, there does not seem to be any way to force Oracle to treat these string literals as unicode data. The environment variable seems to have zero impact. The only way that I can see the unicode data not being corrupted currently is by explicitly using bind parameters with the NVarchar2 data type and, in many cases, this really isn't an option, especially not for large systems and batch operations.
Does anyone else see this issue? This is of critical importance to my group. Is there a different workaround in these cases with the introduction of the managed provider or is this a legitimate bug?
Thanks!
Adam.g