Latches are low-level serialization mechanisms used to protect in-memory shared data structures in the SGA. Think of a latch as a very fast, short-duration lock used internally by Oracle.

- Lightweight and in-memory Lightweight and in-memory - Very fast (microseconds) Very fast (microseconds) - Not transactional Not transactional - Held for a very short time Held for a very short time - Protect shared memory structures (e.g., library cache, buffer cache) Protect shared memory structures (e.g., library cache, buffer cache)

When multiple sessions try to read or write from the buffer cache , Oracle uses buffer cache latches to avoid corruption.

- High CPU usage High CPU usage - Library Cache: Pin or Lock latch waits Library Cache: Pin or Lock latch waits - Query execution delays Query execution delays

Latches = Speed + Protection (not related to user transactions)

Locks are used to control access to data in the database and maintain transaction isolation . These are DML locks that ensure two users don’t change the same data at the same time.

- Protect rows, tables, and objects Protect rows, tables, and objects - Held for the duration of a transaction Held for the duration of a transaction - Enforce data consistency Enforce data consistency - Acquired automatically by Oracle Acquired automatically by Oracle

Session A updates a row: Session B tries to update the same row → row lock wait .

- Row-level locks (TX) Row-level locks (TX) - Table locks (TM) Table locks (TM) - DDL locks DDL locks - Internal locks Internal locks

Locks = Protecting data during transactions

Enqueues are more advanced, flexible locking mechanisms that follow a queue structure — hence the name “enqueue”. They are used for transactional locks, schema locks, and inter-instance coordination (RAC).

- Follow a queue mechanism Follow a queue mechanism - Can be held in different modes (NULL, Share, Exclusive, etc.) Can be held in different modes (NULL, Share, Exclusive, etc.) - Can persist for longer periods Can persist for longer periods - Protects multiple database resources Protects multiple database resources

- When a session updates a row → TX enqueue When a session updates a row → TX enqueue - When a session executes DDL → TM enqueue When a session executes DDL → TM enqueue

Enqueues = Structured, queued locks for multiple resource types Simple Explanation: - Latches → Protect RAM Latches → Protect RAM - Locks → Protect Data Locks → Protect Data - Enqueues → Protect Resources Enqueues → Protect Resources

- -

- -

- - -

Understanding the difference between latches, locks, and enqueues is essential for any Oracle DBA. They help keep the database consistent , stable , and performant , even when thousands of sessions are running concurrently. Explore more with Learnomate Technologies! Want to see how we teach? Head over to our YouTube channel for insights, tutorials, and tech breakdowns: www.youtube.com/@learnomate To know more about our courses, offerings, and team: Visit our official website: www.learnomate.org Interested in mastering Oracle Database Administration? Check out our comprehensive Oracle DBA Training program here: https://learnomate.org/oracle-dba-training/ Want to explore more tech topics? Check out our detailed blog posts here: https://learnomate.org/blogs/ And hey, I’d love to stay connected with you personally! Let’s connect on LinkedIn: Ankush Thavali 😎