- 3,716,136 Users
- 2,242,961 Discussions
- 7,845,842 Comments
Forum Stats
Discussions
Categories
- 17 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 1.6K Databases
- 479 General Database Discussions
- 3.7K Java and JavaScript in the Database
- 22 Multilingual Engine
- 487 MySQL Community Space
- 5 NoSQL Database
- 7.6K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 417 SQLcl
- 42 SQL Developer Data Modeler
- 184.9K SQL & PL/SQL
- 21K SQL Developer
- 1.9K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.1K Development Tools
- 9 DevOps
- 3K QA/Testing
- 259 Java
- 6 Java Learning Subscription
- 11 Database Connectivity
- 67 Java Community Process
- 1 Java 25
- 9 Java APIs
- 141.1K Java Development Tools
- 6 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
- 10 Java SE
- 13.8K Java Security
- 3 Java User Groups
- 22 JavaScript - Nashorn
- 18 Programs
- 125 LiveLabs
- 31 Workshops
- 9 Software
- 3 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 4 Deutsche Oracle Community
- 11 Español
- 1.9K Japanese
- 2 Portuguese
BUG: DbUpdateConcurrencyException when updating and inserting multiple records
When updating and adding multiple rows I am getting a DbConcurrency exception. Note no table has more than 10 rows in it. This only occurs when multiple rows are updated AND inserted within the same SaveChanges() operation.
Microsoft.EntityFrameworkCore.DbUpdateConcurrencyException: 'Database operation expected to affect 1 row(s) but actually affected 2858 row(s).
The sample code is located here: https://github.com/inferno31/oefc-concurrency-issue
Reproduction instructions here: https://github.com/inferno31/oefc-concurrency-issue/blob/master/WFConcurrencyIssue/Readme.md
Answers
-
This bug (30452644) has been reported previously. The Oracle EF Core dev team is working on identifying the root cause and fixing the issue.
-
Are these defects tracked publicly? When can we expect a fix?
-
The bug info is public, but requires a My Oracle Support account to access. In general, the DBA has access to a MOS account.
Currently, we're working on simplifying the test case to remove external dependencies to identify the root cause.
-
We have an enterprise agreement with Oracle, where can I view these bugs? Having visibility to them would have saved me 3 days of troubleshooting. Plus I need to plan my release around these fixes.
-
I believe you should be able to sign in with your Oracle account that you use for these forums. However, your account needs to associated with a customer identifier so that you have the privileges to view bugs and can open service requests.
The bug is not fixed yet. When it is fixed and you need a patch ASAP, you can request a one-off patch. Oracle normally bundles accumulated fixes together every few weeks in a bundled patch. We only create one-off patches for customers needing a specific fix ahead of the next planned bundle patch.
-
Bug 30452644 has been fixed and is available in NuGet Gallery as part of ODP.NET EF Core 19.6.