Re: How to get the statment sql that caused the lock

From: Andy Sayer <andysayer_at_gmail.com>
Date: Mon, 29 Oct 2018 13:55:28 +0000
Message-ID: <CACj1VR7ynKpguCT8N+ChV_jELdGX1D8QKrdGKMjgoXCcCNztyg_at_mail.gmail.com>

“Oh yes, queries in the distributed queries do lock tables because it is not possible to ensure that the query will return only the data committed before the start of the query without a lock. You must have a join with a remote table, but yes, it does happen.”

Maybe the last time you tested this was in a very old version which suffered from this problem but this is simply not what happens now. Regular MVRC works fine over a DB link.

Or maybe the remote database was a different RDBMS.

If you have a test case then I’d be very interested in seeing it.

--
http://www.freelists.org/webpage/oracle-l

Received on Mon Oct 29 2018 - 14:55:28 CET

This message: [ Message body ]
Next message: Lothar Flatz: "Re: Suboptimal query plan with connect by"
Previous message: Radoulov, Dimitre: "Re: Suboptimal query plan with connect by"
In reply to: Mladen Gogala: "Re: How to get the statment sql that caused the lock"
Next in thread: Mladen Gogala: "Re: How to get the statment sql that caused the lock"
Reply: Mladen Gogala: "Re: How to get the statment sql that caused the lock"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message