Practical RMAN Restore Scenario For Linux on Different Server

Practical RMAN Restore Guide

Practical RMAN Restore Guide

This quick 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.

1. Copy RMAN Backups to the New Server

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

Explanation: Make sure you copy all backup pieces (datafiles, control file, SPFILE, archivelogs) to a directory the new server can access.

2. Start with a Minimal PFILE in NOMOUNT

sqlplus / as sysdba -- Create or use a small init file: STARTUP NOMOUNT PFILE='/u01/app/oracle/product/19.0.0/dbhome_1/dbs/initMYDB.ora';

Explanation: You can’t restore the control file or SPFILE unless the instance is NOMOUNT.

3. Restore the Control File & Mount the Database

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

Explanation: Once the control file is restored, we can mount the database so RMAN knows the datafile structure.

4. Use SET NEWNAME FOR DATABASE TO '/newpath/%b'

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

Explanation:

  • SET NEWNAME FOR DATABASE TO '/newpath/%b': This redirects all datafiles to /newpath, using the original base filename (%b).
  • RESTORE DATABASE: Copies datafiles from backup to /newpath.
  • SWITCH DATAFILE ALL: Updates the control file so Oracle knows the new datafile locations.
  • RECOVER DATABASE: Applies archive logs to bring datafiles up to date.

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

If Oracle still expects redo logs under /oldpath (and you can't drop or clear them easily), rename or recreate them in /newpath.

a) Rename the Logs

ALTER DATABASE RENAME FILE '/oldpath/onlinelog/o1_mf_3_abc.log' TO '/newpath/onlinelog/o1_mf_3_abc.log';

Explanation: Tells Oracle the redo log group now resides in /newpath.

b) touch Zero-Byte Files if Needed

mkdir -p /newpath/onlinelog touch /newpath/onlinelog/o1_mf_3_abc.log

Explanation: If Oracle complains it can’t find the file, creating a blank placeholder sometimes helps so CLEAR LOGFILE GROUP x or OPEN RESETLOGS can succeed.

6. Open the Database with RESETLOGS

ALTER DATABASE OPEN RESETLOGS;

Explanation: Finalizes the restore, discards old redo logs, and starts a fresh set.

7. Verify Everything

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

Explanation: Confirm all datafiles and redo logs now point to /newpath (instead of /oldpath).

Summary

  1. Copy backups to the new server.
  2. Startup NOMOUNT with a minimal PFILE.
  3. Restore the control file and MOUNT the database.
  4. SET NEWNAME FOR DATABASE and restore/recover datafiles.
  5. Rename or recreate any redo logs if needed.
  6. Open the database with RESETLOGS.
  7. Check your datafile/redo log paths.

That’s it! You’ve relocated and restored an Oracle database to a new path with minimal fuss.

Comments

Post a Comment

Popular posts from this blog

Oracle Database Upgrade With OPatch Tool (RHEL/Centos/OEL)

Follow these steps to upgrade an Oracle Database using the OPatch tool: 1. Download and Prepare Files Download the patch you want to install along with the latest OPatch tool from Oracle's website. Transfer all downloaded files to the /tmp/ directory, and unzip them. Ensure the correct permissions and ownership are set: chown -R oracle:oinstall p26710464_122010_Linux-x86-64.zip chown -R oracle:oinstall p6880880_122010_Linux-x86-64.zip unzip p26710464_122010_Linux-x86-64.zip unzip p6880880_122010_Linux-x86-64.zip 2. Replace the OPatch Folder Replace the current OPatch folder inside the Oracle database files with the new one: cd $ORACLE_HOME cp -R OPatch OPatch_yedek # Backup current OPatch folder. rm -rf OPatch cp -R /tmp/Opatch . Verify the OPatch version and list applied patches: cd OPatch ./opatch lspatches 3. Check for Conflicts Navigate to the patch folder and run the following command to check for conflicts before starting the upgrade: cd /tmp/26710464/ $O...
Read more

POSTGRESQL UPGRADE WITH PG_UPGRADE UTILITY IN RHEL/CENTOS/OEL

Upgrading PostgreSQL can be a smooth process if you follow the necessary steps carefully. Below is a comprehensive guide to help you through the upgrade. Table of Contents Prerequisites Install the New PostgreSQL Version Set Up New Directories and Permissions Initialize the New Database Configure PostgreSQL Settings Stop and Disable Old PostgreSQL Services Run the Upgrade Process Finalize the Upgrade Post-Upgrade Tasks Prerequisites Before initiating the upgrade, ensure the following prerequisites are met: Internet Connection: Required for downloading packages. PostgreSQL RPM Packages: Necessary for installation. Free Disk Space: Ensure you have more free space than the current database size. Compatibility Checks: Verify PostgreSQL extension compatibility. Crontab Jobs: Identify any cron jobs related to PostgreSQL. Note: Skipping these checks may result in errors during the upgrade process. Install the New PostgreSQL Versio...
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