- 3,723,928 Users
- 2,244,652 Discussions
- 7,850,760 Comments
Forum Stats
Discussions
Categories
- 16 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 2.1K Databases
- 618 General Database Discussions
- 3.7K Java and JavaScript in the Database
- 32 Multilingual Engine
- 497 MySQL Community Space
- 7 NoSQL Database
- 7.7K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 422 SQLcl
- 62 SQL Developer Data Modeler
- 185.1K SQL & PL/SQL
- 21.1K SQL Developer
- 2.4K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.6K Development Tools
- 14 DevOps
- 3K QA/Testing
- 337 Java
- 10 Java Learning Subscription
- 12 Database Connectivity
- 72 Java Community Process
- 2 Java 25
- 12 Java APIs
- 141.2K Java Development Tools
- 8 Java EE (Java Enterprise Edition)
- 153K Java Essentials
- 135 Java 8 Questions
- 86.2K Java Programming
- 270 Java Lambda MOOC
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 16 Java SE
- 13.8K Java Security
- 4 Java User Groups
- 22 JavaScript - Nashorn
- 18 Programs
- 147 LiveLabs
- 34 Workshops
- 10 Software
- 4 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 4 Deutsche Oracle Community
- 16 Español
- 1.9K Japanese
- 3 Portuguese
ManagedData Access Core throws exception on Merge statement
Having an issue with ManagedData Access for .Net Core driver.
if I use a MERGE statement, the action happens, but then the driver also throws a Oracle exception 12537 (ORA number).
since the merge seems to work, i'm catching this error and swallowing it, but it does seem like something we shouldn't have to do. Any thoughts?
Is there anything special about how a merge statement should be called that's different from inserts or updates that seem to work fine?
Best Answer
-
just updated to the latest .net core driver from a few days ago and seems to be fixed.
we had previously found a thread stating that .net core drivers were having an issue with stored procedures and returning similar errors, so we figured it was related to that.
Answers
-
We haven't seen this before. Is there a secondary ORA error, such as in an inner exception alongside the ORA-12537? Also, what is the ORA-12537 error message itself, which can point to the likely problem source?
-
Sorry for my english, but, can you test if connection is open before the statement?.
-
yes, the connection is definitely open, as mentioned in the OP, the merge statement actually works and does what it's supposed to in the DB. could it be a problem in the way it returns the RowsAffected that's different from regular Insert/update statements?
-
just updated to the latest .net core driver from a few days ago and seems to be fixed.
we had previously found a thread stating that .net core drivers were having an issue with stored procedures and returning similar errors, so we figured it was related to that.