1. 首頁
  2. 問答
  3. 在Oracle 11g中恢復RMAN Oracle 10g備份11g

在Oracle 11g中恢復RMAN Oracle 10g備份11g

2012-07-31 158 views
4

我在Sun Solaris OS上擁有Oracle 10g（10.2.0.3）的RMAN完全數據庫備份，我希望在Linux OS上的Oracle 11g（11.2.0.3）上進行恢復。備份片以二進制方式手動傳輸到Oracle 11g服務器。Oracle 11g安裝在Linux OS上。我只有RMAN備份，並且無法訪問備份所在的主數據庫。在Oracle 11g中恢復RMAN Oracle 10g備份11g

-rwxrwxr-x 1 mepc dba 36356096 Jul 16 14:49 snapcf_MEPC.f 
-rwxrwxr-x 1 mepc dba 166028800 Jul 16 15:29 MEPC_full_backup_MEPC_nnnbkn9f_1_1 
-rwxrwxr-x 1 mepc dba 169567744 Jul 16 15:29 MEPC_full_backup_MEPC_nmnbkn9f_1_1 
-rwxrwxr-x 1 mepc dba 164813824 Jul 16 15:39 MEPC_full_backup_MEPC_nonbkn9f_1_1 
-rwxrwxr-x 1 mepc dba 144025600 Jul 16 16:06 MEPC_full_backup_MEPC_nqnbkn9f_1_1 
-rwxrwxr-x 1 mepc dba 168576512 Jul 16 16:09 MEPC_full_backup_MEPC_npnbkn9f_1_1 
-rwxrwxr-x 1 mepc dba 168649216 Jul 16 17:33 MEPC_full_backup_MEPC_o5nbkpvv_1_1 
-rwxrwxr-x 1 mepc dba 162847232 Jul 16 17:34 MEPC_full_backup_MEPC_o6nbkpvv_1_1 
-rwxrwxr-x 1 mepc dba 167351808 Jul 16 17:35 MEPC_full_backup_MEPC_o7nbkpvv_1_1 
-rwxrwxr-x 1 mepc dba 166838272 Jul 16 17:36 MEPC_full_backup_MEPC_o8nbkpvv_1_1 
-rwxrwxr-x 1 mepc dba 166876160 Jul 16 17:37 MEPC_full_backup_MEPC_o9nbkpvv_1_1 
-rwxrwxr-x 1 mepc dba 327606272 Jul 16 17:54 MEPC_full_backup_MEPC_o4nbknav_1_1 
-rwxrwxr-x 1 mepc dba 549658624 Jul 16 18:26 MEPC_full_backup_MEPC_o2nbknav_1_1 
-rwxrwxr-x 1 mepc dba 162984448 Jul 16 18:28 MEPC_full_backup_MEPC_oanbkpvv_1_1 
-rwxrwxr-x 1 mepc dba 163567616 Jul 16 18:29 MEPC_full_backup_MEPC_obnbkpvv_1_1 
-rwxrwxr-x 1 mepc dba 161380352 Jul 16 18:29 MEPC_full_backup_MEPC_ocnbkpvv_1_1 
-rwxrwxr-x 1 mepc dba 1072275456 Jul 18 13:52 MEPC_full_backup_MEPC_o3nbknav_1_1 
-rwxrwxr-x 1 mepc dba 1813348352 Jul 18 17:00 MEPC_full_backup_MEPC_o1nbknav_1_1 
-rwxrwxr-x 1 mepc dba 36438016 Jul 25 15:45 controlfile_bkup_MEPC_c-1469445140-20120522-09

備份採取上述格式。我知道從中進行備份的數據庫的ORACLE_SID和dbid。

每當我嘗試以下命令

[email protected]:/mepc_backup/May22fullbkp$ rman target/

Recovery Manager: Release 11.2.0.3.0 - Production on Tue Jul 31 12:14:54 2012 

Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. 

connected to target database: MEPC (DBID=1595278680) 

RMAN> shutdown; 
using target database control file instead of recovery catalog 
database closed 
database dismounted 
Oracle instance shut down 

RMAN> startup nomount; 

connected to target database (not started) 
Oracle instance started 

Total System Global Area 1071333376 bytes 

Fixed Size      1349732 bytes 
Variable Size    620758940 bytes 
Database Buffers    444596224 bytes 
Redo Buffers     4628480 bytes 

RMAN> restore spfile to '$ORACLE_HOME/dbs/initMEPC.ora' from autobackup db_recovery_file_dest='/mepc_backup/May22fullbkp' db_name='MEPC';

以下錯誤被通報

Starting restore at 31-JUL-12 
using channel ORA_DISK_1 

recovery area destination: /mepc_backup/May22fullbkp 
database name (or database unique name) used for search: MEPC 
channel ORA_DISK_1: no AUTOBACKUPS found in the recovery area 
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20120731 
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20120730 
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20120729 
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20120728 
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20120727 
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20120726 
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20120725 
channel ORA_DISK_1: no AUTOBACKUP in 7 days found 
RMAN-00571: =========================================================== 
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== 
RMAN-00571: =========================================================== 
RMAN-03002: failure of restore command at 07/31/2012 12:22:06 
RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece

我試圖回收通過目錄也rman的備份和下面的錯誤被通報

List of Files Which Where Not Cataloged 
======================================= 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_nonbkn9f_1_1 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_obnbkpvv_1_1 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_ocnbkpvv_1_1 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o7nbkpvv_1_1 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o9nbkpvv_1_1 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_nmnbkn9f_1_1 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_nnnbkn9f_1_1 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o3nbknav_1_1 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o6nbkpvv_1_1 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/controlfile_bkup_MEPC_c-1469445140-20120522-09 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_npnbkn9f_1_1 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_oanbkpvv_1_1 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_nqnbkn9f_1_1 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o1nbknav_1_1 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o5nbkpvv_1_1 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/snapcf_MEPC.f 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o2nbknav_1_1 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o4nbknav_1_1 
    RMAN-07517: Reason: The file header is corrupted 
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o8nbkpvv_1_1 
    RMAN-07517: Reason: The file header is corrupted

該文件沒有損壞，因爲我檢查了se上的校驗和rvers和它是一樣的。

請幫助我如何在Oracle 11g中恢復RMAN oracle 10g備份，並讓我知道我哪裏出錯了。

在此先感謝。

來源

2012-07-31 Harsh

回答

1

你不能這樣做。 AFAIK，Solaris - 假設sparc - 和Linux - 假設英特爾 - 具有不同的endian格式，這是您的問題。您可以使用遷移跨平臺表空間方案。 參見Oracle® Database Backup and Recovery Reference 如果您的endian格式看起來相同，則應使用rman convert數據庫轉換數據庫。在這種情況下，您可以恢復跨平臺和跨版本。

來源

2012-07-31 10:33:30

+0

被如下 PLATFORM_NAME Endian_Format 源的Solaris [TM] OE（64位）\t大 目標Linux IA（32位）\t小 作爲每鏈路提供用於兩個數據庫中的endian格式由你，它說我們可以轉換表空間，數據文件，數據庫的endian格式。我們如何才能在目標數據庫中轉換RMAN備份片斷的endian格式。 我試圖執行此命令（使用正確的語法），但如果失敗。 轉換控制文件RMAN BACKUP控制文件DB FILE NAME CONVERT RMAN BACKUP控制文件從平臺Solaris tm OE 64位 在此先感謝。 – Harsh 2012-07-31 12:44:29

+0

我讀到這個的方式，你應該在源服務器上做好準備。目前我沒有運行sparc來測試，但閱讀文檔中的內容，仔細閱讀。 – 2012-07-31 17:36:56

+0

我只能訪問RMAN Oracle 10g備份片段。通過二進制模式手動將此備份移動到Linux上的Oracle 11g服務器。這就是爲什麼我試圖在目標數據庫中轉換末端格式。那麼，我正在閱讀文檔並試圖找到一個合適的出路。請提出還需要做些什麼。提前致謝。 – Harsh 2012-07-31 19:27:58

0

不適用於10G/11g中，但是這是在12C不同：

在12c中，RMAN提供以下與備份命令選項選項：

運：這個選項創建一個備份集可以運送到任何目的地。如果目標數據庫使用不同於源的endian格式，則會在目標數據庫上執行endian格式轉換。 TO PLATFORM：此選項將導致在源數據庫上執行endian格式轉換，並且只能由該受支持的平臺使用。 DATAPUMP：這指定在執行跨平臺備份時創建數據泵導出轉儲文件。轉儲文件是在獨立的備份集中創建的。

來源

2013-10-02 15:49:54 Tagar

相關問題

 相關問題