We have an application with several connections to the same database (under the same
user)
Database:
- 7.3.0.29 Linux i386
Our Problem:
- Sometimes 2 or more clients lock each other
- All connections are openen in Isolation Level "Read Committed"
Please tell me if I am right:
- Many many selects in Isolation Level "Read Committed" from several connections do
not permanently lock (sharelocks)
Rows. They lock the rows only during the execution of the selects
- After a select is executed, no rows will remain locked, even if I do not commit /
rollback.
- The only cause for a blocking connection in Isolationlevel "Read Committed" can be:
Devspace is Full
Log is Full
A Manipulation (Insert / Update / Delete) or explicit Lock (Lock table ....) is not
committed or rollbacked.
- Is it possible that a typical deadlock can happen?
(Client 1 waits for Client 2 to commit/rollback and Client 2 waits for Client 1 to
commit/rollback)
P.S.: It is possible that a "commit" is missing in our application, but I could not
find the problem on our side,
so it is very useful to get your answers.
Thank you very much in advance,
Greetings, Andre'
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
