Difference Between Redo and Undo in Oracle Database

 



Difference Between Redo and Undo in Oracle Database

In Oracle Database, redo and undo are two critical components that help maintain data integrity and support recovery and transaction control.
Redo

Redo refers to a set of logs that record all changes made to the database, including inserts, updates, and deletes. These changes are written to the redo log buffer and then to the redo log files, ensuring that Oracle can recover committed transactions in the event of a system failure.

Undo

On the other hand, undo is used to reverse the effects of uncommitted transactions. When a transaction is rolled back, the undo data allows Oracle to restore the original data values. Undo is also essential for providing consistent reads to other users by preserving a snapshot of the data before changes were made.

Comments

Post a Comment

Popular posts from this blog

Azure Data Architecture Patterns for Scalable Data Solutions

Image
  In the modern data-driven world, businesses rely on Azure Data Architecture Patterns that are built for scale, speed, and flexibility. Microsoft Azure provides a wide range of powerful cloud-native services that enable data teams to design robust systems for analytics, real-time processing, and storage across hybrid and multi-cloud environments. These Azure Data Architecture Patterns empower organizations to handle diverse workloads—whether it's streaming IoT data or managing enterprise-wide reporting pipelines. 1. Lambda Architecture – Unified Batch and Real-Time Processing When to Use: Ideal for systems needing both historical and real-time data analysis. Key Azure Services: Real-Time: Azure Stream Analytics, Azure Event Hubs Batch: Azure Data Factory, Azure Data Lake Storage, Azure Synapse Analytics How It Works: Speed Layer: Handles real-time data for immediate insights. Batch Layer: Processes large volumes of historical data. Serving Layer: Merges both to present a un...
Read more

VACUUM, ANALYZE, and VACUUM FULL command in PostgreSQL DBA

Image
In PostgreSQL, VACUUM , ANALYZE , and VACUUM FULL are essential maintenance operations that help optimize performance and manage database storage. Here's a concise explanation with examples tailored for a PostgreSQL DBA: What is MVCC in PostgreSQL? MVCC stands for Multi-Version Concurrency Control. It's a core concept in PostgreSQL that allows multiple users to read and write to the database at the same time—without locking each other out. MVCC enables concurrent access to the database while maintaining data consistency and isolation as defined by the ACID properties. Instead of locking rows when a user accesses them, PostgreSQL: Keeps multiple versions of a row (called tuples ) in the database. Each row has hidden metadata:             xmin = ID of the transaction that created the row             xmax = ID of the transaction that deleted or updated the row PostgreSQL uses MVCC (Multi-Version Concurrency Control) to ...
Read more

REINDEX and REINDEX CONCURRENTLY in PostgrSQL DBA

Image
REINDEX and REINDEX CONCURRENTLY In PostgreSQL,  REINDEX  and  REINDEX CONCURRENTLY  are used to rebuild corrupt or bloated indexes. They are essential tools for database maintenance and performance tuning. REINDEX: In practice indexes can become corrupted due to software bugs or hardware failures.  REINDEX  provides a recovery method. REINDEX  provides a way to reduce the space consumption of the index by writing a new version of the index without the dead pages. REINDEX   rebuilds indexes  from scratch. It's commonly used when: Indexes are bloated (due to many  UPDATE / DELETE  operations). Index corruption is suspected. After a major PostgreSQL version upgrade (especially via  pg_upgrade ). To improve performance of certain queries. Parameters REINDEX INDEX index_name; REINDEX TABLE table_name; REINDEX DATABASE db_name; REINDEX SYSTEM db_name; REINDEX CONCURRENTLY: REINDEX CONCURRENTLY  was introduced in  Postgre...
Read more