在Oracle 11g中恢复RMAN Oracle 10g备份11g

我在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

你不能这样做。 AFAIK，Solaris - 假设sparc - 和Linux - 假设英特尔 - 具有不同的endian格式，这是您的问题。您可以使用迁移跨平台表空间方案。参见Oracle® Database Backup and Recovery Reference 如果您的endian格式看起来相同，则应使用rman convert数据库转换数据库。在这种情况下，您可以恢复跨平台和跨版本。

来源

2012-07-31 10:33:30

被如下 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

我读到这个的方式，你应该在源服务器上做好准备。目前我没有运行sparc来测试，但阅读文档中的内容，仔细阅读。 – 2012-07-31 17:36:56

我只能访问RMAN Oracle 10g备份片段。通过二进制模式手动将此备份移动到Linux上的Oracle 11g服务器。这就是为什么我试图在目标数据库中转换末端格式。那么，我正在阅读文档并试图找到一个合适的出路。请提出还需要做些什么。提前致谢。 – Harsh 2012-07-31 19:27:58

不适用于10G/11g中，但是这是在12C不同：

在12c中，RMAN提供以下与备份命令选项选项：

运：这个选项创建一个备份集可以运送到任何目的地。如果目标数据库使用不同于源的endian格式，则会在目标数据库上执行endian格式转换。 TO PLATFORM：此选项将导致在源数据库上执行endian格式转换，并且只能由该受支持的平台使用。 DATAPUMP：这指定在执行跨平台备份时创建数据泵导出转储文件。转储文件是在独立的备份集中创建的。

来源

2013-10-02 15:49:54 Tagar

在Oracle 11g中恢复RMAN Oracle 10g备份11g

回答

相关问题