Restore Rman Backups On A Different Node When The Directory Are Diff_419137.1
In this Document
Goal |
Fix |
References |
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review. |
Applies to:
Oracle Server - Enterprise Edition - Version 10.1.0.2 and laterInformation in this document applies to any platform.
***Checked for relevance on 16-Nov-2012***
Goal
Restoring Rman backup on a different node with different backup directory structures and different database directory structures .
++ The database has to be has to be restored from the Rman backup on NODE 2.
++ The directory structures for the backups and the database files are different on NODE 2.
++ The Rman backups have to put in new directory structure on NODE 2 unlike as they were on NODE 1.
++ Also the database has to be restored to a different directory structure on NODE 2.
Fix
ASSUMPTIONS
-----------------------
++ The database files on NODE 1 are in '/node1/database/prod'
++ The backups on NODE 2 will be in location '/node2/database/backup'
++ The database files on NODE 2 will be restored to '/node2/database/prod
Steps to acheive the goal:
1) Connect to the target database using rman and backup the database ---> ON NODE 1
Recovery Manager: Release 10.2.0.1.0 - Production on Tue Feb 13 00:29:33 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ORA10G (DBID=3932056136)
RMAN> backup database plus archivelog;
Starting backup at 13-FEB-07
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=143 recid=109 stamp=614392105
channel ORA_DISK_1: starting piece 1 at 13-FEB-07
channel ORA_DISK_1: finished piece 1 at 13-FEB-07
piece handle=/node1/database/backup/o1_mf_annnn_TAG20070213T002825_2x21kbds
_.bkp tag=TAG20070213T002825 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 13-FEB-07
Starting backup at 13-FEB-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00003 name=/node1/database/prod/sysaux01.dbf
input datafile fno=00001 name=/node1/database/prod/system01.dbf
input datafile fno=00002 name=/node1/database/prod/undotbs01.dbf
input datafile fno=00004 name=/node1/database/prod/users01.dbf
input datafile fno=00005 name=/node1/database/prod/1.dbf
input datafile fno=00006 name=/node1/database/prod/sysaux02.dbf
input datafile fno=00007 name=/node1/database/prod/undotbs02.dbf
channel ORA_DISK_1: starting piece 1 at 13-FEB-07
channel ORA_DISK_1: finished piece 1 at 13-FEB-07
piece handle=/node1/database/backup/o1_mf_nnndf_TAG20070213T002827_2x21kd12
_.bkp tag=TAG20070213T002827 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:55
Finished backup at 13-FEB-07
Starting backup at 13-FEB-07
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=144 recid=110 stamp=614392165
channel ORA_DISK_1: starting piece 1 at 13-FEB-07
channel ORA_DISK_1: finished piece 1 at 13-FEB-07
piece handle=/node1/database/backup/o1_mf_annnn_TAG20070213T002925_2x21m6ty
_.bkp tag=TAG20070213T002925 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 13-FEB-07
Starting Control File and SPFILE Autobackup at 13-FEB-07
piece handle=/u01/oracle/product/ora10g/dbs/c-3932056136-20070213-02 comment=NONE
Finished Control File and SPFILE Autobackup at 13-FEB-07
RMAN> exit
2) Move the following files to the NODE 2:
+ Controlfile backup piece to the location '/node2/database/backup'
+ The parameter file i.e init.ora file to the default location i.e $ORACLE_HOME/dbs
3) Edit the PFILE on NODE 2 to change the environment specific parameters like .
background_dump_dest =
control_files =
4) Once the PFILE is suitably modified invoke Rman on the NODE 2 after setting the Oracle environment variables and start the database in nomount mode:
[oracle@test-br test]$ export ORACLE_HOME=/u01/oracle/product/ora10g
[oracle@test-br test]$ export ORACLE_SID=ora10g
[oracle@test-br test]$ export PATH=$ORACLE_HOME/bin:$PATH
[oracle@test-br test]$ rman target /
Recovery Manager: Release 10.2.0.1.0 - Production on Tue Feb 13 00:36:55 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount
Oracle instance started
Total System Global Area 205520896 bytes
Fixed Size 1218508 bytes
Variable Size 75499572 bytes
Database Buffers 121634816 bytes
Redo Buffers 7168000 bytes
5) Restore the controlfile from the backup piece.
Starting restore at 13-FEB-07
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=155 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete,
elapsed time: 00:00:02
output filename=/node2/database/prod/control01.ctl
Finished restore at 13-FEB-07
6) Mount the database
7) Now catalog the backup pieces that were shipped from NODE 1
RMAN> catalog backuppiece '/node2/database/backup/o1_mf_annnn_TAG20070213T002825_2x21kbds_.bkp';
RMAN> catalog backuppiece '/node2/database/backup/o1_mf_nnndf_TAG20070213T002827_2x21kd12_.bkp';
8) Get to know the last sequence available in the archivelog backup using the following command.This will help us in recovering the database till that archivelog.
RMAN > list backup of archivelog all;
Let us assume the last sequence of last archivelog in the backup is 50.
9) Rename the Redologfiles,so that they can be created in new locations when opened the database is opened in resetlogs
SQL> alter database rename file '/node1/database/prod/redo01.log' to '/node2/database/prod/redo01.log'; ...... ...... ......
10) Now restore the datafiles to new locations and recover. Since we are recovering the database here till the archivelog sequence 50 the sequence number in the SET UNTIL SEQUENCE clause should be 50 (+1)
RMAN> run { set until sequence 51; set newname for datafile 1 to '/node2/database/prod/sys01.dbf'; set newname for datafile 2 to '/node2/database/prod/undotbs01.dbf'; set newname for datafile 3 to '/node2/database/prod/sysaux01.dbf'; set newname for datafile 4 to '/node2/database/prod/users01.dbf'; set newname for datafile 5 to '/node2/database/prod/1.dbf'; set newname for datafile 6 to '/node2/database/prod/sysaux02.dbf'; set newname for datafile 7 to '/node2/database/prod/undotbs02.dbf'; restore database; switch datafile all; recover database; alter database open resetlogs; }
The below article gives the information of various media manager Environment Variables.
NOTE.312737.1 RMAN and Specific Media Managers Environment Variables.
References
NOTE:228257.1 - RMAN 'Duplicate Database' Feature in Oracle9i / 10G and 11.1NOTE:73974.1 - RMAN: Restoring an RMAN Backup to Another Node
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/17252115/viewspace-1063084/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- HowTo Restore RMAN Disk backups of RAC Database to Single Instance On Another NoRESTDatabase
- guarantee restore points-Flashback after RMAN restoreREST
- RMAN restore validate database報ORA-19693RESTDatabase
- rman 還原歸檔日誌(restore archivelogRESTHive
- RMAN restore fails with ORA-01180: can not create datafile 1 (文件 ID 1265151.1)RESTAI
- RMAN之環境配置(二)---Backups to a Media Manager備份到介質管理器
- Using mysqldump for backupsMySql
- 3.5 Different
- canvas restore()CanvasREST
- different random numbers generatorrandom
- 2.3.3.3.2 Applications at Different VersionsAPP
- 11.23 Two Different Worlds
- CF1408F Two Different
- canvas save()和restore()CanvasREST
- DOCKER特性 - LIVE RESTOREDockerREST
- Script of Narrative Writing from different point of viewView
- 【12c】12c RMAN新特性之通過網路遠端恢復資料庫(RESTORE/Recover from Service)資料庫REST
- 【RMAN】RMAN備份至ASMASM
- DBMS_BACKUP_RESTORE.DBMS_BACKUP_RESTORE用於特殊情況下的恢復REST
- Oracle 11G RAC複製備庫RMAN-03002 RMAN-05501 RMAN-03015 RMAN-03009 RMAN-10038Oracle
- case when 語句
- 【RMAN】RMAN的備份保留策略
- [LeetCode] 93. Restore IP AddressesLeetCodeREST
- git操作之二:git restoreGitREST
- provider for back&restore app datyaIDERESTAPP
- ORACLE rman與RMAN-00054&ORA-09945Oracle
- [20190706]Same dog, different leash – functions in SQL.txtFunctionSQL
- RMAN(轉)
- python leetcode 93. Restore IP AddressesPythonLeetCodeREST
- [20190228]Backup Restore Throttle sleep.txtREST
- git restore極簡使用記錄GitREST
- Crunchy PostgreSQL database restore via pgo commandSQLDatabaseRESTGo
- Reboot Restore Rx Pro中文版bootREST
- 【RMAN】Oracle rman 常用命令參考Oracle
- RMAN恢復之RMAN-06555處理
- [ERROR] InnoDB: ibdata1 different size (rounded down to MB)Error
- Bad magic number for central directory
- Flume - [02] Spooling Directory Source
- The directory xx is registered as a Git rootGit