Practical RMAN Restore Scenario For Linux on Different Server

Practical RMAN Restore Guide

Practical RMAN Restore Guide

This guide shows how to restore and relocate an Oracle database via RMAN. We’ll assume you want all datafiles in a new folder (/newpath instead of /oldpath), and possibly handle redo logs in a new location as well. Steps include restoring SPFILE, cataloging backups, restoring archived logs, and point-in-time recovery.

1. Copy RMAN Backups to the New Server

mkdir -p /u01/backup/test_restore cp /oldserver/backups/*.bkp /u01/backup/test_restore

Copy all backup pieces (datafiles, control file, SPFILE, archivelogs) to a directory the new server can access.

2. Create Required Oracle Directories

mkdir -p /u01/app/oracle/admin/MYDB/adump mkdir -p /u01/app/oracle/oradata/MYDB mkdir -p /u01/app/oracle/fast_recovery_area/MYDB mkdir -p /newpath/onlinelog

Ensure directories exist for diagnostic files (adump), datafiles, FRA, and redo logs before proceeding.

3. Startup NOMOUNT with a Minimal PFILE

sqlplus / as sysdba -- Create a basic init file with just DB_NAME and diagnostic_dest: STARTUP NOMOUNT PFILE='/u01/app/oracle/product/19.0.0/dbhome_1/dbs/initMYDB.ora';

A minimal PFILE is required to get the instance into NOMOUNT.

4. Restore the SPFILE (Optional but Recommended)

rman target / -- From autobackup: RESTORE SPFILE FROM AUTOBACKUP; -- Or from a known backup piece: RESTORE SPFILE TO '/u01/app/oracle/product/19.0.0/dbhome_1/dbs/spfileMYDB.ora' FROM '/u01/backup/test_restore/spfile_backup.bkp'; -- Restart with the restored SPFILE: SHUTDOWN IMMEDIATE; STARTUP NOMOUNT;

Restoring the SPFILE ensures the database uses the original initialization parameters.

5. Catalog Backup Pieces in RMAN

CATALOG START WITH '/u01/backup/test_restore' NOPROMPT;

Cataloging makes RMAN aware of the backup sets you copied.

6. Restore the Control File & Mount the Database

RESTORE CONTROLFILE FROM '/u01/backup/test_restore/controlfile_backup.bkp'; ALTER DATABASE MOUNT;

7. Redirect and Restore Datafiles

RUN { SET NEWNAME FOR DATABASE TO '/newpath/%b'; RESTORE DATABASE; SWITCH DATAFILE ALL; }

At this point datafiles are restored to the new path.

8. Restore Archived Logs (For Recovery)

RUN { ALLOCATE CHANNEL c1 DEVICE TYPE DISK; RESTORE ARCHIVELOG ALL; RELEASE CHANNEL c1; }

Archived logs are needed to roll forward your datafiles. You can restore all logs, or restrict by FROM TIME, FROM SEQUENCE, or SCN.

9. Recover Database (Point-in-Time if Needed)

Choose recovery type:

a) Full Recovery to Latest

RECOVER DATABASE;

b) Point-in-Time Recovery

-- Example: Recover until a specific time RUN { SET UNTIL TIME "to_date('2025-09-19 20:30:00','YYYY-MM-DD HH24:MI:SS')"; RESTORE DATABASE; RECOVER DATABASE; }

This allows you to roll forward only up to a certain time, SCN, or log sequence.

10. Handle Redo Logs in a New Location (Optional)

ALTER DATABASE RENAME FILE '/oldpath/onlinelog/o1_mf_3_abc.log' TO '/newpath/onlinelog/o1_mf_3_abc.log'; -- If needed: touch /newpath/onlinelog/o1_mf_3_abc.log

11. Open the Database with RESETLOGS

ALTER DATABASE OPEN RESETLOGS;

12. Verify Everything

SELECT name FROM v$datafile; SELECT group#, member FROM v$logfile;

Summary

  1. Copy backups to the new server.
  2. Create required folders (adump, datafiles, FRA, redo logs).
  3. Startup NOMOUNT with a minimal PFILE.
  4. Restore the SPFILE and restart NOMOUNT.
  5. Catalog backup files in RMAN.
  6. Restore the control file and MOUNT the database.
  7. Redirect and restore datafiles.
  8. Restore archived logs.
  9. Recover database (full or point-in-time).
  10. Handle redo logs if needed.
  11. Open with RESETLOGS.
  12. Verify datafile and log paths.

Comments

Post a Comment

Popular posts from this blog

Error when Installing Some Postgresql Packages (Perl IPC-Run)

Resolving PostgreSQL 17 Dependency Error on Oracle Linux 8 Fixing perl(IPC::Run) Dependency Error When Installing PostgreSQL 17 on Oracle Linux 8 Background While preparing a fresh Oracle Linux 8 server for a PostgreSQL 17 deployment, an attempt to install all PostgreSQL packages in one go failed with an unsatisfied dependency error: Problem 1: cannot install the best candidate for the job - nothing provides perl(IPC::Run) needed by postgresql17-devel-17.4-1PGDG.rhel8.x86_64 ... Root Cause The perl(IPC::Run) module (along with several tool‑chain libraries) resides in the CodeReady Builder repository, which is disabled by default on Oracle Linux 8. Because postgresql17-devel and postgresql17-test depend on that module, dnf / yum cannot resolve the full dependency tree unless the repository is enabled. CodeReady Builder hosts developer‑oriented packages—compilers, debuggers, Perl/Python modules—that ma...
Read more

Creating Jobs With Different Users via pg_cron in Azure Postgresql Flexible Server

PostgreSQL pg_cron: Scheduling Materialized View Refresh Across Databases PostgreSQL pg_cron: Scheduling Materialized View Refresh Across Databases In this tutorial, I’ll walk you through the process of scheduling a Materialized View refresh using the pg_cron extension in PostgreSQL. Specifically, we’ll cover how to execute a scheduled SQL command in a different database using cron.schedule_in_database . Step 1: Enable the pg_cron Extension in Azure Portal On Azure PostgreSQL Flexible Server, the pg_cron extension is managed directly through the Azure portal. Follow these steps: Go to the Azure portal and navigate to your PostgreSQL Flexible Server instance. Under the Server Parameters section, locate the azure.extensions parameter. Add PG_CRON to the list of allowed extensions (as shown in the screenshot). Once enabled, the extension is automatically installed in the default `postgres` database . If you need to schedule jobs in o...
Read more

Oracle 19c Dataguard Installation with DG Broker

Oracle 19c Data Guard – Standby Creation, Switchover & Failover Oracle 19c Physical Standby Creation & Management (RMAN Duplicate + Data Guard Broker) This article walks through building a physical standby using RMAN  DUPLICATE FROM ACTIVE DATABASE , then managing switchover / failover with the Data Guard Broker. The commands were tested on Oracle Linux 8 with Oracle Database 19c . Assumptions Two hosts ( oracle1.localdomain & oracle2.localdomain ) with Oracle 19c installed. Primary instance runs on oracle1 ; standby will be created on oracle2 . Listener port 1521 is reachable in both directions (check firewalls). Primary DB name MYDBPROD ; standby unique name MYDBDG . 1 – Primary Server Preparation 1.1 Switch to ARCHIVELOG & Force Logging -- Check mode SELECT log_mode FROM v$database; -- If NOARCHIVELOG: SHUTDOWN IMMEDIATE; STARTUP MOUNT; ALTER DATABASE ARCH...
Read more