系统表空间恢复

系统表空间恢复

[@more@]

Ø 系统表空间损坏或丢失

SQL> alter database open resetlogs; alter database open resetlogs * ERROR at line 1: ORA-01157: cannot identify/lock data file 1 - see DBWR trace file ORA-01110: data file 1: '/u01/oradata/retc/rwsw_system' SQL> recover database using backup controlfile; ORA-00283: recovery session canceled due to errors ORA-01110: data file 1: '/u01/oradata/retc/rwsw_system' ORA-01157: cannot identify/lock data file 1 - see DBWR trace file ORA-01110: data file 1: '/u01/oradata/retc/rwsw_system'

Ø restore系统表空间SYSTEM

rman target / catalog rman/rman@rmandb Recovery Manager: Release 9.2.0.7.0 - 64bit Production Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved. connected to target database: RETC (DBID=1688860591) connected to recovery catalog database RMAN> run 2> { 3> allocate channel t1 type 'SBT_TAPE' 4> parms 'BLKSIZE=524288,ENV=(TDPO_OPFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)'; 5> set newname for datafile 1 to '/u01/oradata/retc/rwsw_system'; 6> restore tablespace system from tag='TAG20121124T053038'; 7> release channel t1; 8> } 9> allocated channel: t1 channel t1: sid=10 devtype=SBT_TAPE channel t1: Tivoli Data Protection for Oracle: version 5.2.0.0 executing command: SET NEWNAME Starting restore at 06-DEC-12 channel t1: starting datafile backupset restore channel t1: specifying datafile(s) to restore from backup set restoring datafile 00001 to /u01/oradata/retc/rwsw_system channel t1: restored backup piece 1 piece handle=7cnr387v_1_1 tag=TAG20121124T053038 params=NULL channel t1: restored backup piece 2 piece handle=7cnr387v_2_1 tag=TAG20121124T053038 params=NULL channel t1: restore complete Finished restore at 06-DEC-12 released channel: t1 Recovery Manager complete.

Ø 恢复系统表空间SYSTEM

SQL> recover database using backup controlfile ORA-00279: change 30626721711 generated at 11/24/2012 05:30:40 needed for thread 1 ORA-00289: suggestion : /u01/oradata/archivelog/1_198779.dbf ORA-00280: change 30626721711 for thread 1 is in sequence #198779 Specify log: {=suggested | filename | AUTO | CANCEL} ORA-00279: change 30626721711 generated at 11/24/2012 04:41:10 needed for thread 2 ORA-00289: suggestion : /u01/oradata/archivelog/2_260039.dbf ORA-00280: change 30626721711 for thread 2 is in sequence #260039 Specify log: {=suggested | filename | AUTO | CANCEL} ORA-00279: change 30626756837 generated at 11/24/2012 06:02:49 needed for thread 2 ORA-00289: suggestion : /u01/oradata/archivelog/2_260040.dbf ORA-00280: change 30626756837 for thread 2 is in sequence #260040 ORA-00278: log file '/u01/oradata/archivelog/2_260039.dbf' no longer needed for this recovery

Specify log: {=suggested | filename | AUTO | CANCEL} ORA-00279: change 30626757063 generated at 11/24/2012 06:02:50 needed for thread 1 ORA-00289: suggestion : /u01/oradata/archivelog/1_198780.dbf ORA-00280: change 30626757063 for thread 1 is in sequence #198780 ORA-00278: log file '/u01/oradata/archivelog/1_198779.dbf' no longer needed forthis recovery Specify log: {=suggested | filename | AUTO | CANCEL} ORA-00279: change 30626972131 generated at 11/24/2012 08:23:48 needed for thread 2 ORA-00289: suggestion : /u01/oradata/archivelog/2_260041.dbf ORA-00280: change 30626972131 for thread 2 is in sequence #260041 ……… ……… Specify log: {=suggested | filename | AUTO | CANCEL} ORA-00279: change 30628644962 generated at 11/24/2012 13:59:15 needed for thread 1 ORA-00289: suggestion : /u01/oradata/archivelog/1_198798.dbf ORA-00280: change 30628644962 for thread 1 is in sequence #198798 ORA-00278: log file '/u01/oradata/archivelog/1_198797.dbf' no longer needed for this recovery Specify log: {=suggested | filename | AUTO | CANCEL} ORA-00279: change 30628731073 generated at 11/24/2012 14:12:29 needed for thread 1 ORA-00289: suggestion : /u01/oradata/archivelog/1_198799.dbf ORA-00280: change 30628731073 for thread 1 is in sequence #198799 ORA-00278: log file '/u01/oradata/archivelog/1_198798.dbf' no longer needed for this recovery Specify log: {=suggested | filename | AUTO | CANCEL} cancel Media recovery cancelled. SQL>

系统表空间SYSTEM已经恢复，数据库已经处于一致的状态，值得注意的是，恢复系统表空间，数据库必须处于mount状态。非系统表空间，数据库可以处于open状态，在恢复的时候，offline需要恢复的表空间或数据文件，然后恢复，恢复完成之后，再online表空间或数据文件。

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/28227905/viewspace-1059890/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/28227905/viewspace-1059890/