碼上歡樂
相關內容    簡體    繁體

RMAN restore fails with ORA-01180: can not create datafile 1

本文轉載自   查看原文   2018-06-15 10:02   955    ORA-01180/ 數據庫技術(Oracle)/ rman

 

最近在驗證、測試備份有效性時，遇到了“ORA-01180: can not create datafile 1”這個錯誤，順便結合metalink的官方文檔“RMAN restore fails with ORA-01180: can not create datafile 1 (文檔 ID 1265151.1)”里面的內容做一個學習、歸納、總結，順便加深一下理解。

 

 

creating datafile fno=1 name=/u01/oradata/SCM2/system01.dbf

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of restore command at 06/14/2018 10:28:34

ORA-01180: can not create datafile 1

ORA-01110: data file 1: '/u01/oradata/SCM2/system01.dbf'

 

 

 當然這個數據文件可能是system01.dbf,也可能是其它任何數據文件。但是如果它是FILE_ID為1數據文件，那么就是關鍵問題，因為FILE_ID為1是系統數據文件。它無法在RMAN還原過程中被創建。而它又必須從備份中還原（restore）。出現這個錯誤呢，要么就是沒有可用的備份（no backups available for use），要么是當前的化身（Incarnation） 未正確設置。

 

 

官方文檔提供下面命令來判別具體原因.

 

RMAN> list incarnation of database;
 
RMAN> list backup of datafile 1;
 
RMAN> list copy of datafile 1;
 
RMAN> list backup summary;

 

 

1: 檢查是否沒有可用的備份

 

 

如下命令所示，你可以檢查是否存在可用的備份

 

RMAN>  list backup of datafile 1;
 
 
List of Backup Sets
===================
 
BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
21778   Full    2.47G      DISK        00:08:28     03-JUN-18      
        BP Key: 21778   Status: EXPIRED  Compressed: YES  Tag: TAG20180603T002006
        Piece Name: /u04/backup/backupsets/ora_df977790007_s23771_s1
  List of Datafiles in backup set 21778
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  1       Full 28945050985 03-JUN-18 /u01/oradata/SCM2/system01.dbf
 
BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
21792   Full    2.47G      DISK        00:08:21     04-JUN-18      
        BP Key: 21792   Status: EXPIRED  Compressed: YES  Tag: TAG20180604T001936
        Piece Name: /u04/backup/backupsets/ora_df977876376_s23786_s1
  List of Datafiles in backup set 21792
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  1       Full 28945603859 04-JUN-18 /u01/oradata/SCM2/system01.dbf
 
BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
21806   Full    2.47G      DISK        00:08:33     05-JUN-18      
        BP Key: 21806   Status: AVAILABLE  Compressed: YES  Tag: TAG20180605T002025
        Piece Name: /u04/backup/backupsets/ora_df977962825_s23801_s1
  List of Datafiles in backup set 21806
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  1       Full 28946703480 05-JUN-18 /u01/oradata/SCM2/system01.dbf
 
RMAN>

 

 

如上所示，雖然有兩個備份文件狀態是EXPIRED，但是還是存在一個可用的備份文件，如果備份的狀態全部是EXPIRED，則對備份集鍵運行crosscheck 查看它是否存在，例如

 

 

 

RMAN> crosscheck backupset 138;

 

 

如果存在，狀態將會被更新為AVAILABLE。如果在運行crosscheck后狀態仍為EXPIRED，則你需要的備份在物理上不存在。

 

 

RMAN> crosscheck backupset 21806;
 
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=910 devtype=DISK
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u04/backup/backupsets/ora_df977962825_s23801_s1 recid=21806 stamp=977962827
Crosschecked 1 objects
 
RMAN> crosscheck backupset 21804;
 
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of crosscheck command at 06/15/2018 08:21:59
RMAN-06160: no backup pieces found for backup set key: 21804
 
RMAN>

 

$ ls  /u04/backup/backupsets/ora_df977876376_s23786_s1
  ls: /u04/backup/backupsets/ora_df977876376_s23786_s1: No such file or directory
$ ls /u04/backup/backupsets/ora_df977790007_s23771_s1
  ls: /u04/backup/backupsets/ora_df977790007_s23771_s1: No such file or directory
$ ls /u04/backup/backupsets/ora_df977962825_s23801_s1
  /u04/backup/backupsets/ora_df977962825_s23801_s1
$

 

 

2： 檢查數據庫當前的Incarnation

 

 

官方文檔提供的例子如下所示

 

 

RMAN> list backup of datafile 1;


List of Backup Sets
===================

BS Key  Type LV Size       Device Type Elapsed Time Completion Time    
------- ---- -- ---------- ----------- ------------ --------------------
138     Full    531.25M    DISK        00:00:00     13 FEB 2015 14:31:35
        BP Key: 136   Status: AVAILABLE  Compressed: NO  Tag: TAG20150213T143135
        Piece Name: /opt/app/oracle/fra/ORA102/backupset/2015_02_13/o1_mf_nnndf_TAG20150213T143135_bftw0r14_.bkp
  List of Datafiles in backup set 138
  File LV Type Ckp SCN    Ckp Time             Name
  ---- -- ---- ---------- -------------------- ----
  1       Full 25207062   13 FEB 2015 14:31:35 /opt/app/oracle/oradata/ORA102/system01.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time    
------- ---- -- ---------- ----------- ------------ --------------------
139     Full    531.32M    DISK        00:00:00     13 FEB 2015 14:09:34
        BP Key: 137   Status: AVAILABLE  Compressed: NO  Tag: TAG20150213T140934
        Piece Name: /opt/app/oracle/fra/ORA102/backupset/2015_02_13/o1_mf_nnndf_TAG20150213T140934_bfttqhh6_.bkp
  List of Datafiles in backup set 139
  File LV Type Ckp SCN    Ckp Time             Name
  ---- -- ---- ---------- -------------------- ----
  1       Full 25206825   13 FEB 2015 14:09:34 /opt/app/oracle/oradata/ORA102/system01.dbf

 

RMAN> list incarnation of database;


List of Database Incarnations
DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
------- ------- -------- ---------------- --- ---------- ----------
1       1       ORA102   400119926        CURRENT 1          19 MAR 2012 15:29:58
2       2       ORA102   400119926        ORPHAN  5766931    04 OCT 2012 15:37:51
3       3       ORA102   400119926        ORPHAN  5768164    16 OCT 2012 15:33:09
...
9       9       ORA102   400119926        ORPHAN  25204629   13 FEB 2015 13:03:55
10      10      ORA102   400119926        ORPHAN  25205038   13 FEB 2015 13:35:57
11      11      ORA102   400119926        ORPHAN  25206695   13 FEB 2015 14:09:07
13      13      ORA102   400119926        ORPHAN  25206882   13 FEB 2015 14:16:24
14      14      ORA102   400119926        ORPHAN  25206882   13 FEB 2015 14:43:32
12      12      ORA102   400119926        ORPHAN  25206883   13 FEB 2015 14:30:54

 

要還原在2015年2月13日14點09分34秒進行的備份標簽 (TAG20150213T140934)，你必須在執行還原之前將incarnation重置為11 。

 

RMAN> reset database to incarnation 11;

 

個人遇到的例子如下，使用Tag為TAG20180605T002025的備份集還原，照理說當前的Incarnation是正確的

 

RMAN> list backup of datafile 1;
 
using target database control file instead of recovery catalog
 
List of Backup Sets
===================
 
BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
21806   Full    2.47G      DISK        00:08:33     05-JUN-18      
        BP Key: 21806   Status: AVAILABLE  Compressed: YES  Tag: TAG20180605T002025
        Piece Name: /u04/backup/backupsets/ora_df977962825_s23801_s1
  List of Datafiles in backup set 21806
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  1       Full 28946703480 05-JUN-18 /u01/oradata/SCM2/system01.dbf
RMAN> list incarnation of database;
 
 
List of Database Incarnations
DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
------- ------- -------- ---------------- --- ---------- ----------
1       1       SCM2     4095319980       PARENT  1          05-OCT-12
2       2       SCM2     4095319980       CURRENT 28333829966 28-MAR-18

 

 

那么，我們檢查一下告警日志，如下截圖所示，因為catalog歸檔日志時，把不相關的歸檔日志catalog了，Oracle從歸檔日志中自動探測到incarnation信息，並重置incarnation，從而導致恢復報錯。

 

 

clip_image001[4]

 

 

參考官方文檔 RMAN restore database fails ORA-01180: can not create datafile 1 (文檔 ID 1573040.1)

 

 

When a BACKUP controlfile is used with a Flash Recovery Area defined, an  implicit crosscheck of the FRA is done and any files found belonging to the database are catalog'd to the controlfile.

Archivelogs created after a resetlogs operation will cause a new incarnation to be registered in the controlfile.

 

The new incarnations meant the database backup needed for restore  no longer belonged to the current incarnation.

 

 

 

參考資料：

 

RMAN restore fails with ORA-01180: can not create datafile 1 (文檔 ID 1265151.1)

RMAN restore database fails ORA-01180: can not create datafile 1 (文檔 ID 1573040.1)


免責聲明！

本站轉載的文章為個人學習借鑒使用，本站對版權不負任何法律責任。如果侵犯了您的隱私權益，請聯系本站郵箱yoyou2525@163.com刪除。



猜您在找 RMAN-06023: no backup or copy of datafile 1 found to restore 異機恢復 RMAN-06023: no backup or copy of datafile 17 found to restore RMAN備份時報“ORA-19504: failed to create file”和“ORA-27038: created file already exists” Oracle rman中restore和recover的區別 使用RMAN對控制文件進行restore Can't restore sql from selection. Oracle 12c: RMAN restore/recover pluggable database 有關rman備份ora-27192和ora-19511錯誤 WindowsDB數據RMAN recover至linux報錯RMAN-11003 ORA-10562 ORA-10564 RMAN-03002, RMAN-06059, ORA-19625 and ORA-27037 When Running RMAN Backup of Archivelogs
 
粵ICP備18138465號   © 2018-2025 CODEPRJ.COM