statement, which enables you to lock all tables in all databases. (This is a very convenient way to get backups if you have a file system such as Veritas that can take snapshots in time.) A table lock protects only against inappropriate reads or writes by other sessions. The table can be accessed freely by the session within which it was created, regardless of what other locking may be in effect.
If a transaction of this sort is going to change the data in the table, then it should use mode.) To avoid deadlocks, make sure all transactions acquire locks on the same objects in the same order, and if multiple lock modes are involved for a single object, then transactions should always acquire the most restrictive mode first.A session can acquire or release locks only for itself.One session cannot acquire locks for another session or release locks held by another session.More information about the lock modes and locking strategies can be found in Section 13.3.BEGIN WORK; LOCK TABLE films IN SHARE MODE; SELECT id FROM films WHERE name = 'Star Wars: Episode I - The Phantom Menace'; -- Do ROLLBACK if record was not returned INSERT INTO films_user_comments VALUES (_id_, 'GREAT! '); COMMIT WORK; If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.