一、rman 資料庫遷移--從檔案系統到檔案系統用預設的備份路徑

haozg_oracle發表於2012-05-23

一、用rman遷移資料庫，恢復到指定的日誌序列號 sequence#

1、 rman 備份源端資料庫過程

[oracle@haozg backup]$
[oracle@haozg backup]$ rman target /

Recovery Manager: Release 11.2.0.1.0 - Production on Mon May 14 18:29:45 2012

connected to target database: ORA11G (DBID=4179426506)

RMAN> run{
allocate channel c1 type disk maxpiecesize=500m;
backup current controlfile format '/u01/app/flash_recovery_area/backup/ctl_%d_%s';
backup full database format '/u01/app/flash_recovery_area/backup/db_%d_%s_%p_%t';
sql 'alter system archive log current';
release channel c1;
}2> 3> 4> 5> 6> 7>

using target database control file instead of recovery catalog
allocated channel: c1
channel c1: SID=35 device type=DISK

Starting backup at 14-MAY-12
channel c1: starting full datafile backup set
channel c1: specifying datafile(s) in backup set
including current control file in backup set
channel c1: starting piece 1 at 14-MAY-12
channel c1: finished piece 1 at 14-MAY-12
piece handle=/u01/app/flash_recovery_area/backup/ctl_ORA11G_1 tag=TAG20120514T182951 comment=NONE
channel c1: backup set complete, elapsed time: 00:00:01
Finished backup at 14-MAY-12

Starting backup at 14-MAY-12
channel c1: starting full datafile backup set
channel c1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oradata/system01.dbf
input datafile file number=00004 name=/u01/app/oradata/user01.dbf
input datafile file number=00002 name=/u01/app/oradata/sysaux01.dbf
input datafile file number=00003 name=/u01/app/oradata/undo01.dbf
channel c1: starting piece 1 at 14-MAY-12

channel c1: finished piece 1 at 14-MAY-12
piece handle=/u01/app/flash_recovery_area/backup/db_ORA11G_2_1_783282593 tag=TAG20120514T182953 comment=NONE
channel c1: backup set complete, elapsed time: 00:04:05
channel c1: starting full datafile backup set
channel c1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel c1: starting piece 1 at 14-MAY-12
channel c1: finished piece 1 at 14-MAY-12
piece handle=/u01/app/flash_recovery_area/backup/db_ORA11G_3_1_783282839 tag=TAG20120514T182953 comment=NONE
channel c1: backup set complete, elapsed time: 00:00:01
Finished backup at 14-MAY-12

sql statement: alter system archive log current

released channel: c1
RMAN>

2、把spfile檔案和rman備份集複製到目標端的對應目錄下，然後在目標端啟動例項。過程如下：

[oracle@haozg dbs]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Wed May 16 13:48:47 2012

Connected to an idle instance.

SQL> startup nomout;
SP2-0714: invalid combination of STARTUP options
SQL> startup nomount
ORACLE instance started.

Total System Global Area 146472960 bytes
Fixed Size                  1335080 bytes
Variable Size              92274904 bytes
Database Buffers           50331648 bytes
Redo Buffers                2531328 bytes
SQL>
SQL>
SQL> create pfile from spfile;

File created.

SQL> exi
SP2-0042: unknown command "exi" - rest of line ignored.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options
[oracle@haozg dbs]$ ls
hc_ora11g.dat init.ora.bak peshm_ora11g_0
initora11g.ora lkORA11G spfileora11g.ora
[oracle@haozg dbs]$

3、檢視目標端資料庫的dbid

[oracle@haozg backup]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Mon May 14 19:24:13 2012

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options

SQL> select dbid from v$database;

DBID
----------
4179426506

4、rman到目標資料庫，指定dbid

[oracle@haozg dbs]$ rman target /

Recovery Manager: Release 11.2.0.1.0 - Production on Wed May 16 13:57:22 2012

connected to target database: ORA11G (not mounted)

RMAN> set dbid=4179426506

executing command: SET DBID

RMAN>

5、在目標端，從指定備份集中恢復控制檔案

RMAN> restore controlfile from '/u01/app/flash_recovery_area/backup/ctl_ORA11G_1';

Starting restore at 16-MAY-12
using channel ORA_DISK_1

channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/u01/app/oradata/control1.ctl
output file name=/u01/app/oradata/control2.ctl
Finished restore at 16-MAY-12

RMAN>

----檢視恢復的控制檔案
[oracle@haozg oradata]$ ls -al
total 19048
drwxr-xr-x. 2 oracle oinstall 4096 May 16 14:09 .
drwxrwxr-x. 9 oracle oinstall 4096 May 16 09:44 ..
-rw-r-----. 1 oracle oinstall 9748480 May 16 14:11 control1.ctl
-rw-r-----. 1 oracle oinstall 9748480 May 16 14:11 control2.ctl

6、啟動資料庫到muout狀態

RMAN> startup mount;

database is already started
database mounted
released channel: ORA_DISK_1

RMAN>

7、轉儲資料檔案
RMAN> restore database;

Starting restore at 16-MAY-12
Starting implicit crosscheck backup at 16-MAY-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK
Finished implicit crosscheck backup at 16-MAY-12

Starting implicit crosscheck copy at 16-MAY-12
using channel ORA_DISK_1
Finished implicit crosscheck copy at 16-MAY-12

searching for all files in the recovery area
cataloging files...
no files cataloged

using channel ORA_DISK_1

creating datafile file number=1 name=/u01/app/oradata/system01.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 05/16/2012 14:15:21
ORA-01180: can not create datafile 1
ORA-01110: data file 1: '/u01/app/oradata/system01.dbf'

RMAN>

出現上面的錯誤，處理方法如下：

RMAN> catalog start with '/u01/app/flash_recovery_area/backup';

searching for all files that match the pattern /u01/app/flash_recovery_area/backup

List of Files Unknown to the Database
=====================================
File Name: /u01/app/flash_recovery_area/backup/db_ORA11G_2_1_783282593
File Name: /u01/app/flash_recovery_area/backup/db_ORA11G_3_1_783282839
File Name: /u01/app/flash_recovery_area/backup/ctl_ORA11G_1

Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
cataloging done

List of Cataloged Files
=======================
File Name: /u01/app/flash_recovery_area/backup/db_ORA11G_2_1_783282593
File Name: /u01/app/flash_recovery_area/backup/db_ORA11G_3_1_783282839
File Name: /u01/app/flash_recovery_area/backup/ctl_ORA11G_1

RMAN>

繼續轉儲資料檔案

RMAN> restore database;

Starting restore at 16-MAY-12
using channel ORA_DISK_1

channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oradata/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oradata/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oradata/undo01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oradata/user01.dbf
channel ORA_DISK_1: reading from backup piece /u01/app/flash_recovery_area/backup/db_ORA11G_2_1_783282593
channel ORA_DISK_1: piece handle=/u01/app/flash_recovery_area/backup/db_ORA11G_2_1_783282593 tag=TAG20120514T182953
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:45
Finished restore at 16-MAY-12

RMAN>

8、恢復資料庫，恢復到指定的日誌sequence#，做不完全恢復。

在源端進行日誌切換 alter system switch logfile; 把生成的歸檔日誌拷貝到目標端的對應目錄下，我把sequenc#為16、17、18的
歸檔日誌都拷貝到了目標端。

recover database until sequence 15 thread 1;
datafile 1 must be restored from backup older than SCN 221707

recover database until sequence 16 thread 1;
RMAN-06556: datafile 1 must be restored from backup older than SCN 248060

recover database until sequence 17 thread 1;

提示找不到sequence# 為16的歸檔日誌。

原因是我用系統預設的歸檔路徑儲存歸檔日誌，生成的歸檔日誌檔名是系統自動命名的，和引數
log_archive_format string %t_%s_%r.dbf
的格式不一樣，在用歸檔日誌恢復的時候要按照引數指定的格式尋找對應的歸檔日誌，但是這個格式和系統自動生成的歸檔日誌格式
不一樣導致找不到歸檔日誌檔案。
所以在rman做備份恢復的時候要指定歸檔路徑log_archive_dest_1，可以避免上面的錯誤發生。

但是如果遇到上面的問題處理方法如下：執行下面的命令：

catalog archivelog '/u01/app/flash_recovery_area/ORA11G/archivelog/2012_05_14/o1_mf_1_16_7v1qwz45_.arc';
catalog archivelog '/u01/app/flash_recovery_area/ORA11G/archivelog/2012_05_14/o1_mf_1_17_7v1xt9f9_.arc';
catalog archivelog '/u01/app/flash_recovery_area/ORA11G/archivelog/2012_05_14/o1_mf_1_18_7v1ysry3_.arc';

過程如下：
RMAN> catalog archivelog '/u01/app/flash_recovery_area/ORA11G/archivelog/2012_05_14/o1_mf_1_16_7v1qwz45_.arc';
catalog archivelog '/u01/app/flash_recovery_area/ORA11G/archivelog/2012_05_14/o1_mf_1_17_7v1xt9f9_.arc';
catalog archivelog '/u01/app/flash_recovery_area/ORA11G/archivelog/2012_05_14/o1_mf_1_18_7v1ysry3_.arc';
cataloged archived log
archived log file name=/u01/app/flash_recovery_area/ORA11G/archivelog/2012_05_14/o1_mf_1_16_7v1qwz45_.arc RECID=2 STAMP=783444095

RMAN>
cataloged archived log
archived log file name=/u01/app/flash_recovery_area/ORA11G/archivelog/2012_05_14/o1_mf_1_17_7v1xt9f9_.arc RECID=3 STAMP=783444096

RMAN>

cataloged archived log
archived log file name=/u01/app/flash_recovery_area/ORA11G/archivelog/2012_05_14/o1_mf_1_18_7v1ysry3_.arc RECID=4 STAMP=783444097

RMAN>

RMAN> list archivelog all;

List of Archived Log Copies for database with db_unique_name ORA11G
=====================================================================

Key     Thrd Seq     S Low Time
------- ---- ------- - ---------
2       1    16      A 14-MAY-12
        Name: /u01/app/flash_recovery_area/ORA11G/archivelog/2012_05_14/o1_mf_1_16_7v1qwz45_.arc

3 1 17 A 14-MAY-12
Name: /u01/app/flash_recovery_area/ORA11G/archivelog/2012_05_14/o1_mf_1_17_7v1xt9f9_.arc

4 1 18 A 14-MAY-12
Name: /u01/app/flash_recovery_area/ORA11G/archivelog/2012_05_14/o1_mf_1_18_7v1ysry3_.arc

RMAN> recover database until sequence 17 thread 1;

Starting recover at 16-MAY-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=22 device type=DISK

starting media recovery

archived log for thread 1 with sequence 16 is already on disk as file /u01/app/flash_recovery_area/ORA11G/archivelog/2012_05_14/o1_mf_1_16_7v1qwz45_.arc
archived log file name=/u01/app/flash_recovery_area/ORA11G/archivelog/2012_05_14/o1_mf_1_16_7v1qwz45_.arc thread=1 sequence=16
media recovery complete, elapsed time: 00:00:01
Finished recover at 16-MAY-12

RMAN>

9、以resetlogs方式開啟資料庫

RMAN> alter database open resetlogs;

database opened

RMAN>

來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/23062014/viewspace-730696/，如需轉載，請註明出處，否則將追究法律責任。

用rman從檔案系統遷移資料庫到asm
2014-01-14
資料庫ASM
四、用rman從檔案系統遷移資料庫到asm
2012-06-07
資料庫ASM
使用RMAN遷移檔案系統資料庫到ASM
2013-12-05
資料庫ASM
三、rman 資料庫遷移--從檔案系統到裸裝置
2012-06-19
資料庫
三、rman 資料庫遷移--從檔案系統到裸裝置用dd複製控制檔案
2013-11-12
資料庫
利用rman遷移裸裝置資料檔案到檔案系統
2010-06-08
如何遷移ASM資料檔案到檔案系統
2011-11-10
ASM
移動資料檔案從ASM到檔案系統
2011-09-16
ASM
利用RMAN將資料庫從檔案系統遷移到ASM
2011-05-10
資料庫ASM
資料庫從檔案系統遷移到ASM
2017-11-29
資料庫ASM
利用RMAN在檔案系統與ASM之間遷移資料庫
2015-04-01
ASM資料庫
將資料庫從ASM遷移到檔案系統
2014-03-01
資料庫ASM
將資料庫從檔案系統遷移到ASM
2014-03-01
資料庫ASM
移動資料檔案從檔案系統到ASM磁碟組中
2011-09-16
ASM
非系統資料檔案損壞，rman備份恢復
2017-04-24
利用RMAN將資料庫從檔案系統遷移到ASM(單例項)
2013-04-08
資料庫ASM單例
ASM檔案系統遷移
2012-08-21
ASM
asm 檔案系統遷移
2012-08-28
ASM
遷移資料庫的檔案到不同路徑(轉)
2019-04-01
資料庫
用RMAN遷移檔案到ASM或從ASM遷出
2011-01-20
ASM
【資料遷移】RMAN遷移資料庫到ASM(二)切換資料檔案到ASM
2016-11-03
資料庫ASM
FastDFS檔案系統遷移和資料恢復
2021-07-07
AST資料恢復
遷移資料庫檔案到ASM
2015-09-17
資料庫ASM
rman恢復資料庫--用備份的控制檔案
2013-11-12
資料庫
ASM與檔案系統之間copy資料檔案--檔案系統到ASM
2014-03-06
ASM
遷移檔案系統管理下的db到asm下
2009-10-11
ASM
dataguard備庫的資料檔案的遷移
2016-04-27
win10系統如何備份檔案 win10系統備份檔案在哪裡
2021-12-03
Win10
把檔案系統的資料檔案遷移到ASM儲存
2014-05-14
ASM
達夢資料庫系統表空間資料檔案遷移過程
2022-01-06
資料庫
EXPDP備份到NFS檔案系統 ORA-27054
2015-03-23
NFS
【備份恢復】歸檔模式下丟失系統關鍵資料檔案利用RMAN備份恢復
2016-10-17
模式
從檔案系統遷移到ASM上
2018-02-05
ASM
oralce 從檔案系統遷移到ASM
2012-08-24
ASM
RMAN說，我能備份(4)--RMAN備份資料檔案和控制檔案
2010-01-15
資料庫檔案的遷移
2014-09-11
資料庫
遷移和移動 UNIX 檔案系統(轉)
2007-08-10
把資料庫控制檔案備份到跟蹤檔案
2012-05-04
資料庫

一、rman 資料庫遷移--從檔案系統到檔案系統用預設的備份路徑

相關文章