title: Oracle deadlock without explicit locking and read committed isolation level, why?
body: <p>I get this error <code>Message: ORA-00060: deadlock detected while waiting for resource</code> even though I am not using any explicit table locking and my isolation level is set to <code>READ COMMITTED</code>.</p>
  
  <p>I use multiple threads over the Spring <code>TransactionTemplate</code> with default propagation. In my business logic the data is separated so that two transaction will never have the same set of data. Therefor I don't need <code>SERIALIZABLE</code></p>
  
  <p>Why can Oracle detect a deadlock? Deadlocks are impossible in this constellation, or am I missing something? If I'm not missing anything then my separation algorithm must be wrong, right? Or could there be some other explaination?</p>