RE: Multiple Concurrent DML operation contention

From: Mark W. Farnham <>
Date: Fri, 22 Dec 2017 14:05:58 -0500
Message-ID: <11a201d37b57$e82275a0$b86760e0$>

With only that information the answer is NO.  

There are many strategies and within each strategy many tactics to minimize the concurrency footprint of transactions, some of which involve object storage.  

One strawman, if you have the capacity to execute all the DML on some particular table on exactly one node is to set up a service on a single node (presumably with another node for failover only if the primary node is not available) and see if the DML concurrency (by avoiding gcc concurrency) is reduced to a tolerable level.  

Of course that only works if in fact a single node can handle the DML load (and perhaps you further proceed with this load asymmetry by NOT allowing lots of other things to routinely run on that node by having other services.)  

Other particular situations would involve other strategies and tactics.  


From: [] On Behalf Of Sanjay Mishra (Redacted sender "smishra_97" for DMARC) Sent: Friday, December 22, 2017 1:52 PM
To: Oracle-L Freelists
Subject: Multiple Concurrent DML operation contention  


Can someone tell what are the changes to be done on Object level including tablespace for table where more than 100 session are concurrently doing DML on RAC environmen ? It is Oracle 12c R1  


Received on Fri Dec 22 2017 - 20:05:58 CET

Original text of this message