ManagedData Access Core throws exception on Merge statement — oracle-tech

    Forum Stats

  • 3,716,000 Users
  • 2,242,928 Discussions
  • 7,845,734 Comments

Discussions

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

ManagedData Access Core throws exception on Merge statement

user2256623
user2256623 Member Posts: 3
edited March 2019 in ODP.NET

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

  • user2256623
    user2256623 Member Posts: 3
    edited March 2019 Accepted 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

  • Alex Keh-Oracle
    Alex Keh-Oracle Posts: 2,753 Employee
    edited March 2019

    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?

  • Molonator69
    Molonator69 Member Posts: 7
    edited March 2019

    Sorry for my english, but, can you test if connection is open before the statement?.

  • user2256623
    user2256623 Member Posts: 3
    edited March 2019

    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? 

  • user2256623
    user2256623 Member Posts: 3
    edited March 2019 Accepted 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.

Sign In or Register to comment.