rman>> rman> restore database;
rman> recover database; //online redolog 不存在
SQL>recover database until cancel; //当redo log丢失,数据库在缺省的方式下,是不容许进行recover操作的,那么如何在这种情况下操作呢
SQL>create pfile from spfile;
vi /u01/product/10.20/dbs/initora10g.ora,在这个文件的最后一行添加
*.allow_resetlogs_corruption='TRUE'; //容许resetlogcorruption
SQL>shutdown immediate;
SQL>startuppfile='/u01/product/10.20/dbs/initora10g.ora'mount;
SQL>alter database open resetlogs;
基于时间点的恢复:
run{
set untiltime "to_date(07/01/02 15:00:00','mm/dd/yy hh24:mi:ss')";
restoredatabase;
recoverdatabase;
alterdatabase open resetlogs;
}
ALTER SESSION SET NLS_DATE_FORMAT='YYYY-MM-DDHH24:MI:SS';
1.startup mount;
2.restore database until time"to_date('2009-7-19 13:19:00','YYYY-MM-DD HH24:MI:SS')";
3.recover database until time"to_date('2009-7-19 13:19:00','YYYY-MM-DD HH24:MI:SS')";
4.alter database open resetlogs;
如果有openresetlogs,都是不完整恢复.
基于 SCN的恢复:
1.startup mount;
2.restore database until scn 10000;
3.recover database until scn 10000;
4.alter database open resetlogs;
基于日志序列的恢复:
1.startup mount;
2.restore database until SEQUENCE 100 thread 1;//100是日志序列
3.recover database until SEQUENCE 100 thread 1;
4.alter database open resetlogs;
日志序列查看命令:SQL>select * from v$log;其中有一个sequence字段.resetlogs就会把sequence 置为1
=================================RMAN catalog模式下的备份与恢复=====================
1.创建Catalog所需要的表空间
SQL>create tablespace rman_ts> 2.创建RMAN用户并授权
SQL>create user rman> SQL>grant recovery_catalog_owner to rman;(grantconnect to rman)
查看角色所拥有的权限:select * from dba_sys_privs where grantee='RECOVERY_CATALOG_OWNER';
(RECOVER_CATALOG_OWNER,CONNECT,RESOURCE)
3.创建恢复目录
oracle>rman catalog rman/rman
RMAN>create catalog tablespace rman_ts;
RMAN>register database;(database是target database)
database registered in recovery catalog
starting full resync of recovery catalog
full resync complete
RMAN> connect target /;
以后要使用备份和恢复,需要连接到两个数据库中,命令:
oracle>rman target / catalog rman/rman (第一斜杠表示target数据库,catalog表示catalog目录 rman/rman表示catalog用户名和密码)
命令执行后显示:
Recovery Manager:> Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ORA10G (DBID=3988862108)
connected to recovery catalog database
命令解释:
Report schema Report shema是指在数据库中需找schema
List backup 从control读取信息
Crosscheck backup 看一下backup的文件,检查controlfile中的目录或文件是否真正在磁盘上
Delete backupset 24 24代表backupset 的编号, 既delete目录,也delete你的文件
注意:在做了alter databaseopen resetlogs;会把onlineredelog file清空,数据文件丢失.所以这个时候要做一个全备份。
resetlogs命令表示一个数据库逻辑生存期的结束和另一个数据库逻辑生存期的开始,每次使用resetlogs命令的时候,SCN不会被重置,不过oracle会重置日志序列号,而且会重置
联机重做日志内容.这样做是为了防止不完全恢复后日志序列会发生冲突(因为现有日志和数据文件间有了时间差)。
Rman 归档文件丢失导致不能备份的,在备份前先执行以下两条命令
crosscheck archivelog all;
delete expired archivelog all;
补充知识:RECOVER DATABASE UNTIL CANCEL 和 RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE 区别
RECOVER DATABASE UNTIL CANCEL ==> DATAFILEHEADER SCN一定会小于CONTROLFILE的DATAFILE SCN 如果你有进行RESTORE DATAFILE,则该RESTORE的DATAFILE HEADERSCN一定会小于目前CONTROLFILE的DATAFILE SCN,此时会无法开启数据库,必须进行mediarecovery。重做archive log直到该datafile header的SCN=current scn
RECOVER DATABASE UNTIL CANCEL USING BACKUPCONTROLFILE; ==> DATAFILE HEADER SCN一定会大于CONTROLFILE的DATAFILE SCN 如果只是某TABLE被DROP掉,没有破坏数据库整体数据结构,还可以用NCOMPLETERECOVERY解决如果是某个TABLESPACE ORDATAFILE被DROP掉,因为档案结构已经破坏,目前的CONTROLFILE内已经没有该DATAFILE的信息,就算你只RESTORE DATAFILE然后进行INCOMPLETERECOVERY也无法救回被DROP的DATA FILE。只好RESOTRE 之前备份的CONTROLFILE(里头被DROPDATAFILE Metadata此时还存在),不过RESTOREC CONTROLFILE后此时Oracle会发现CONTROL FILE内的SYSTEM SCN会小于目前的DATAFILE HEADERSCN,也不等于目前储存于LOGFILE内的SCN,此时就必须使用RECOVER DATABASE UNTIL CANCEL USING BACKUPCONTROLFILE到DROPDATAFILE OR DROP TABLESPACE之前的SCN。
************* Scrip of RMAN *********************
Full backup
run {
allocate channel oem_backup_disk1 type disk format'G:\Full\%U';
backup incremental level 0 cumulative as BACKUPSETtag '%TAG' database include current controlfile;
backup as BACKUPSET tag '%TAG' archivelog all notbacked up;
release channel oem_backup_disk1;
}
Partial for Data file backup
run {
allocate channel oem_backup_disk1 type disk format'G:\partial\%U';
backup incremental level 0 cumulative as BACKUPSETtag '%TAG' datafile 'I:\ORACLE\PRODUCT\10.2.0\ORADATA\MSLTSD\SYSTEM01.DBF','I:\ORACLE\PRODUCT\10.2.0\ORADATA\MSLTSD\UNDOTBS01.DBF', 'I:\ORACLE\PRODUCT\10.2.0\ORADATA\MSLTSD\SYSAUX01.DBF','I:\ORACLE\PRODUCT\10.2.0\ORADATA\MSLTSD\USERS01.DBF' include current controlfile;
backup as BACKUPSET tag '%TAG' archivelog all notbacked up;
release channel oem_backup_disk1;
}
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
Archive log file backup
run {
allocate channel oem_backup_disk1 type disk format'E:\OracleBackup\MSLTSD\ARCHIVELOG\%U';
backup as BACKUPSET tag '%TAG' archivelog all notbacked up 2 times;
delete noprompt archivelog until time 'sysdate - 2'backed up 2 times to device type disk;