OraEasy

Introduction Point-in-Time Recovery (PITR) is an Oracle RMAN recovery technique used to recover a database to a specific point in time, SCN, or log sequence. It is particularly useful when unwanted changes, accidental data deletion, or logical corruption occurs and the database needs to be restored to a known consistent state before the incident. In this article, we will demonstrate how to perform an RMAN Point-in-Time Recovery using database backups, incremental backups, archived redo logs, and the control file. We will restore the database to a specific point in time and verify the database after recovery. PITR Scenario For this demonstration, we have an Oracle database named CDBORCL . We will first take an RMAN Level 0 backup followed by Level 1 incremental backups, archived redo log backups, and control file backups. After taking the required backups, we will perform additional INSERT and UPDATE operations on a sample table. We will then identify a specific recovery point...

Introduction A Cascaded Standby Database is an Oracle Data Guard configuration in which a standby database receives redo from another standby database instead of directly from the primary database. The intermediate standby acts as a relay, receiving redo from the primary and forwarding it to one or more downstream standby databases. A Cascaded Standby helps scale Oracle Data Guard environments by allowing one standby database to distribute redo to downstream standbys. This reduces the number of direct redo connections from the primary database. This setup builds directly on the standby configuration methods we've covered before, specifically RMAN backup and restore , RMAN Duplicate , and restoring from the primary's service . Here we use RMAN Duplicate twice in sequence, once from the primary to build the intermediate standby, and again from that intermediate standby to build the downstream one, so it's worth being familiar with that method first if you haven't set ...