- 3,708,745 Users
- 2,241,117 Discussions
- 7,840,574 Comments
Forum Stats
Discussions
Categories
- 9 Data
- 362.2K Big Data Appliance
- 3 Data Science
- 1K Databases
- 322 General Database Discussions
- 3.7K Java and JavaScript in the Database
- 22 Multilingual Engine
- 479 MySQL Community Space
- 3 NoSQL Database
- 7.6K Oracle Database Express Edition (XE)
- 2.7K ORDS, SODA & JSON in the Database
- 408 SQLcl
- 32 SQL Developer Data Modeler
- 184.6K SQL & PL/SQL
- 20.9K SQL Developer
- 1.3K Development
- Developer Projects
- 31 Programming Languages
- 134.5K Development Tools
- 4 DevOps
- 3K QA/Testing
- 172 Java
- 3 Java Learning Subscription
- 6 Database Connectivity
- 64 Java Community Process
- Java 25
- 7 Java APIs
- 141.1K Java Development Tools
- 2 Java EE (Java Enterprise Edition)
- 153K Java Essentials
- 132 Java 8 Questions
- 86.1K Java Programming
- 270 Java Lambda MOOC
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 5 Java SE
- 13.8K Java Security
- 3 Java User Groups
- 22 JavaScript - Nashorn
- 18 Programs
- 80 LiveLabs
- 23 Workshops
- 7 Software
- 3 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 3 Deutsche Oracle Community
- 6 Español
- 1.9K Japanese
- 2 Portuguese
Exception when OracleConnection.ClientInfo contains Umlaut
We use OracleConnection.ClientInfo to set the CLIENT_INFO of the session. According to documentation, this value piggybacks with the next message to the Oracle server.
However, if ClientInfo contains any "Umlaut" characters (e.g. "ä", ö", "ü"), an exception is thrown whenever this next message to the server happens (e.g. on the next query).
We get an Oracle.ManagedDataAccess .Client.OracleConnection which has an inner exception of OracleInternal.Network.NetworkException which represents ORA-12537 Network Session: End Of File
var oracleConnection = new OracleConnection(connectionString);
oracleConnection.ClientInfo = "München"; // "Munich" would work
// next query gets an exception
CLIENT_INFO itself apparently supports Umlaut characters, because setting CLIENT_INFO in a stored procedure works and doesn't give an exception. This seems to be an issue inside the C# implementation.
I'm using the nuget "Oracle.ManagedDataAccess" 18.3.0
Thanks,
Markus
Answers
I was able to reproduce this issue in the latest managed ODP.NET 19.9. I filed bug 32016802 to track this issue and get it resolved. Thanks for reporting it.