安科网

oracle 归档管理

Carlos

Carlos

2020-05-11

关注 关注
一、归档模式与非归档模式区别

非归档，联机日志文件循环覆盖，数据库执行recover时所需要的归档不存在，数据库不能进行完全恢复。

二、更改数据库的归档模式
1 shutdown the database instance
shutdown immediate;
2 start the database mount
startup mount
3 change the database archiving mode
alter database archivelog;
4 open the database
alter database open;

eg：

SQL> select log_mode from v$database;

LOG_MODE

NOARCHIVELOG

SQL> archive log list;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination /oracle/crm/disk2/archive
Oldest online log sequence 34
Current log sequence 36
SQL> select dest_name,status,destination from v$archive_dest;

DEST_NAME STATUS DESTINATION

LOG_ARCHIVE_DEST_1 VALID /oracle/archivelog
LOG_ARCHIVE_DEST_2 ALTERNATE /oracle/crm/disk2/archive
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.

Total System Global Area 952020992 bytes
Fixed Size 2232208 bytes
Variable Size 578814064 bytes
Database Buffers 364904448 bytes
Redo Buffers 6070272 bytes
Database mounted.
SQL> alter database archivelog;

Database altered.

SQL> alter database open;

Database altered.

SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /oracle/crm/disk2/archive
Oldest online log sequence 34
Next log sequence to archive 36
Current log sequence 36

三、 调整归档的进程数

SQL> alter system set log_archive_max_processes=6;

System altered.

四、设置归档目录
1 参数LOG_ARCHIVE_DEST_n n由1到10用于指定本地或远程归档目录，n值由11到31仅用于指定远程归档目录
2 LOG_ARCHIVE_DEST_STATE_n (where n is an integer from 1 to 31)
enable:表示该目录数据库可以使用
defer:表示该目录被临时禁止
alternate:表示该目录处于替换状态，如果主目录不可用，这该目录变为enable。同时需要注意的是alternate不能用于log_archive_dest_11 to log_archive_dest_31

eg
SQL> alter system set log_archive_dest_state_2=defer;

System altered.

SQL> col dest_name for a30
SQL> col status for a15
SQL> col destination for a50
SQL> select dest_name,status,destination from v$archive_dest;

DEST_NAME STATUS DESTINATION

LOG_ARCHIVE_DEST_1 VALID /oracle/archivelog
LOG_ARCHIVE_DEST_2 DEFERRED /oracle/crm/disk2/archive

3 指定归档目录语句
alter system set LOG_ARCHIVE_DEST_1 = ‘LOCATION = /disk1/archive‘
alter system set LOG_ARCHIVE_DEST_2 = ‘LOCATION = /disk2/archive‘
alter system set LOG_ARCHIVE_DEST_3 = ‘LOCATION = +RECOVERY‘

4 指定归档名字
alter system set log_archiveformat=‘arch%t%s%r.arch‘ scope=spfile;
%t:thread number
%s:log sequence number
%r: the resetlogs ID

5 查询数据库当前设置的归档目录
select dest_name,status,destination from v$archive_dest;
DEST_NAME STATUS DESTINATION

LOG_ARCHIVE_DEST_1 VALID /oracle/archivelog
LOG_ARCHIVE_DEST_2 ALTERNATE /oracle/crm/disk2/archive

五、归档的备份
1 在rman下备份归档

RMAN> backup archivelog from sequence 64 format ‘/backup/archbk%T%U.bak‘;

Starting backup at 18-MAY-14
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=64 RECID=65 STAMP=847887432
input archived log thread=1 sequence=65 RECID=66 STAMP=847887434
input archived log thread=1 sequence=66 RECID=67 STAMP=847887435
input archived log thread=1 sequence=67 RECID=68 STAMP=847887436
input archived log thread=1 sequence=68 RECID=69 STAMP=847887436
input archived log thread=1 sequence=69 RECID=70 STAMP=847887440
input archived log thread=1 sequence=70 RECID=71 STAMP=847887442
input archived log thread=1 sequence=71 RECID=72 STAMP=847887442
input archived log thread=1 sequence=72 RECID=73 STAMP=847887443
input archived log thread=1 sequence=73 RECID=74 STAMP=847887445
input archived log thread=1 sequence=74 RECID=75 STAMP=847887446
input archived log thread=1 sequence=75 RECID=76 STAMP=847887446
input archived log thread=1 sequence=76 RECID=77 STAMP=847887447
input archived log thread=1 sequence=77 RECID=78 STAMP=847887448
input archived log thread=1 sequence=78 RECID=79 STAMP=847887513
input archived log thread=1 sequence=79 RECID=80 STAMP=847888655
channel ORA_DISK_1: starting piece 1 at 18-MAY-14
channel ORA_DISK_1: finished piece 1 at 18-MAY-14
piece handle=/backup/archbk_20140518_0cp8jg8f_1_1.bak tag=TAG20140518T123735 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 18-MAY-14

2 通过plus archivelog 备份归档
命令 backup database plus archivelog format ‘/backup/fullbk%U%T.bak‘;
该命令执行如下动作
1、 Runs the ALTER SYSTEM ARCHIVE LOG CURRENT statement
2、 Runs BACKUP ARCHIVELOG ALL. If backup optimization is enabled, then RMAN skips logs that it has already backed up to the specified device.

3 、Backs up the rest of the files specified in the BACKUP command

4、Backs up any remaining archived logs generated during the backup. If backup optimization is not enabled, then RMAN backs up the logs generated in Step 1
plus all the logs generated during the backup
/×备份所有剩余的归档以及在备份时新生成的归档/

eg
RMAN> backup database plus archivelog format ‘/backup/fullbk%U%T.bak‘;

Starting backup at 18-MAY-14
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=64 RECID=115 STAMP=847890752
input archived log thread=1 sequence=65 RECID=118 STAMP=847890752
input archived log thread=1 sequence=66 RECID=119 STAMP=847890752
input archived log thread=1 sequence=67 RECID=120 STAMP=847890752
input archived log thread=1 sequence=68 RECID=121 STAMP=847890752
input archived log thread=1 sequence=69 RECID=117 STAMP=847890752
input archived log thread=1 sequence=70 RECID=122 STAMP=847890752
input archived log thread=1 sequence=71 RECID=123 STAMP=847890752
input archived log thread=1 sequence=72 RECID=124 STAMP=847890752
input archived log thread=1 sequence=73 RECID=125 STAMP=847890752
input archived log thread=1 sequence=74 RECID=126 STAMP=847890752
input archived log thread=1 sequence=75 RECID=127 STAMP=847890752
input archived log thread=1 sequence=76 RECID=128 STAMP=847890752
input archived log thread=1 sequence=77 RECID=129 STAMP=847890752
input archived log thread=1 sequence=78 RECID=116 STAMP=847890752
input archived log thread=1 sequence=79 RECID=114 STAMP=847890752
input archived log thread=1 sequence=80 RECID=113 STAMP=847889781
input archived log thread=1 sequence=81 RECID=130 STAMP=847898077
input archived log thread=1 sequence=82 RECID=131 STAMP=847898081
input archived log thread=1 sequence=83 RECID=132 STAMP=847898082
input archived log thread=1 sequence=84 RECID=133 STAMP=847898083
input archived log thread=1 sequence=85 RECID=134 STAMP=847898084
input archived log thread=1 sequence=86 RECID=135 STAMP=847898087
input archived log thread=1 sequence=87 RECID=136 STAMP=847898190
input archived log thread=1 sequence=88 RECID=137 STAMP=847898333
input archived log thread=1 sequence=89 RECID=138 STAMP=847898714
input archived log thread=1 sequence=90 RECID=139 STAMP=847899333
input archived log thread=1 sequence=91 RECID=140 STAMP=847900304
input archived log thread=1 sequence=92 RECID=141 STAMP=847900930
channel ORA_DISK_1: starting piece 1 at 18-MAY-14
channel ORA_DISK_1: finished piece 1 at 18-MAY-14
piece handle=/backup/fullbk_0dp8js84_1_1_20140518.bak tag=TAG20140518T160211 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 18-MAY-14

Starting backup at 18-MAY-14
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/oracle/test/system1.dbf
input datafile file number=00003 name=/oracle/test/sysaux01.dbf
input datafile file number=00010 name=/oracle/test/undotbs5.dbf
input datafile file number=00004 name=/oracle/test/users01.dbf
input datafile file number=00013 name=/oracle/test/test2.dbf
channel ORA_DISK_1: starting piece 1 at 18-MAY-14
channel ORA_DISK_1: finished piece 1 at 18-MAY-14
piece handle=/oracle/CRM2/app/product/11.2.0/db1/dbs/0ep8js89_1_1 tag=TAG20140518T160215 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:03:26
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 18-MAY-14
channel ORA_DISK_1: finished piece 1 at 18-MAY-14
piece handle=/oracle/CRM2/app/product/11.2.0/db1/dbs/0fp8jseo_1_1 tag=TAG20140518T160215 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 18-MAY-14

Starting backup at 18-MAY-14
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=93 RECID=142 STAMP=847901149
channel ORA_DISK_1: starting piece 1 at 18-MAY-14
channel ORA_DISK_1: finished piece 1 at 18-MAY-14
piece handle=/backup/fullbk_0gp8jseu_1_1_20140518.bak tag=TAG20140518T160550 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 18-MAY-14

六、 关于archivelog delete input 和delete all input区别
1 rman的归档位置定义两个
log_archive_dest_1 string LOCATION=/oracle/archive
log_archive_dest_2 string LOCATION=/oracle/archive2/
2 执行alter system switch logfile命令后两个归档目录下的归档日志
[ archive]$ ls -lt
total 2648
-rw-r----- 1 oracle oinstall 1024 Aug 17 16:29 1_38_791488634.dbf
-rw-r----- 1 oracle oinstall 1536 Aug 17 16:29 1_37_791488634.dbf
-rw-r----- 1 oracle oinstall 1536 Aug 17 16:29 1_35_791488634.dbf
-rw-r----- 1 oracle oinstall 1024 Aug 17 16:29 1_36_791488634.dbf
-rw-r----- 1 oracle oinstall 5120 Aug 17 16:26 1_34_791488634.dbf
-rw-r----- 1 oracle oinstall 59392 Aug 17 16:23 1_33_791488634.dbf

[ archive2]# ls -lt
total 88
-rw-r----- 1 oracle oinstall 1024 Aug 17 16:29 1_38_791488634.dbf
-rw-r----- 1 oracle oinstall 1536 Aug 17 16:29 1_37_791488634.dbf
-rw-r----- 1 oracle oinstall 1536 Aug 17 16:29 1_35_791488634.dbf
-rw-r----- 1 oracle oinstall 1024 Aug 17 16:29 1_36_791488634.dbf
-rw-r----- 1 oracle oinstall 5120 Aug 17 16:26 1_34_791488634.dbf
-rw-r----- 1 oracle oinstall 59392 Aug 17 16:23 1_33_791488634.dbf
3 执行
RMAN> backup database plus archivelog delete input; 查看日志可以发现oracle删除的归档日志仅仅是其备份过的。
archived log file name=/oracle/archive2/1_33_791488634.dbf RECID=321 STAMP=791569408
archived log file name=/oracle/archive/1_34_791488634.dbf RECID=322 STAMP=791569592
archived log file name=/oracle/archive/1_35_791488634.dbf RECID=324 STAMP=791569775
archived log file name=/oracle/archive2/1_36_791488634.dbf RECID=327 STAMP=791569775
archived log file name=/oracle/archive2/1_37_791488634.dbf RECID=329 STAMP=791569778
archived log file name=/oracle/archive/1_38_791488634.dbf RECID=330 STAMP=791569780
archived log file name=/oracle/archive/1_39_791488634.dbf RECID=332 STAMP=791570012
archived log file name=/oracle/archive/1_40_791488634.dbf RECID=334 STAMP=791570187
注意删除的归档日志位置随机有archive2 也有archive。
4 重新切换生成归档日志
[ archive]$ ls -lt
total 2684
-rw-r----- 1 oracle oinstall 1024 Aug 17 16:53 1_46_791488634.dbf
-rw-r----- 1 oracle oinstall 1536 Aug 17 16:53 1_44_791488634.dbf
-rw-r----- 1 oracle oinstall 1024 Aug 17 16:53 1_45_791488634.dbf
-rw-r----- 1 oracle oinstall 1024 Aug 17 16:53 1_42_791488634.dbf
-rw-r----- 1 oracle oinstall 1024 Aug 17 16:53 1_43_791488634.dbf
-rw-r----- 1 oracle oinstall 32768 Aug 17 16:53 1_41_791488634.dbf

[ archive2]# ls -lt
total 92
-rw-r----- 1 oracle oinstall 1024 Aug 17 16:53 1_46_791488634.dbf
-rw-r----- 1 oracle oinstall 1536 Aug 17 16:53 1_44_791488634.dbf
-rw-r----- 1 oracle oinstall 1024 Aug 17 16:53 1_45_791488634.dbf
-rw-r----- 1 oracle oinstall 1024 Aug 17 16:53 1_42_791488634.dbf
-rw-r----- 1 oracle oinstall 1024 Aug 17 16:53 1_43_791488634.dbf
-rw-r----- 1 oracle oinstall 32768 Aug 17 16:53 1_41_791488634.dbf
5 执行backup database plus archivelog delete all input ;查看日志发现oracle删除的归档日志 发现删除了两个目录下的所有日志
archived log file name=/oracle/archive2/1_40_791488634.dbf RECID=335 STAMP=791570187
archived log file name=/oracle/archive/1_41_791488634.dbf RECID=336 STAMP=791571221
archived log file name=/oracle/archive2/1_41_791488634.dbf RECID=337 STAMP=791571221
archived log file name=/oracle/archive2/1_42_791488634.dbf RECID=339 STAMP=791571222
archived log file name=/oracle/archive/1_42_791488634.dbf RECID=338 STAMP=791571222
archived log file name=/oracle/archive/1_43_791488634.dbf RECID=340 STAMP=791571222
archived log file name=/oracle/archive2/1_43_791488634.dbf RECID=341 STAMP=791571222
archived log file name=/oracle/archive/1_44_791488634.dbf RECID=342 STAMP=791571228
archived log file name=/oracle/archive2/1_44_791488634.dbf RECID=343 STAMP=791571228
archived log file name=/oracle/archive/1_45_791488634.dbf RECID=344 STAMP=791571228
archived log file name=/oracle/archive2/1_45_791488634.dbf RECID=345 STAMP=791571228
archived log file name=/oracle/archive2/1_46_791488634.dbf RECID=347 STAMP=791571229
archived log file name=/oracle/archive/1_46_791488634.dbf RECID=346 STAMP=791571229
archived log file name=/oracle/archive/1_47_791488634.dbf RECID=348 STAMP=791571526
archived log file name=/oracle/archive2/1_47_791488634.dbf RECID=349 STAMP=791571526
oracle官方文档提示：
If you had specified DELETE INPUT rather than DELETE ALL INPUT, then RMAN would have only deleted the specific archived redo log files that it backed up. For
example, RMAN would delete the logs in /arc_dest1 if these files were used as the source of the backup, but leave the contents of the /arc_dest2 intact
如果指定delete input ，则rman将仅删除已备份的归档日志，例如对于有两个归档目录 /arc_dest1 和 /arc_dest2 如果把/arc_dest1做为backup的源，delete input将删除 /arc_dest1 中的内容，保留dest2中的归档日志，通过实验可以看出，就算有两个归档位置，rman备份的时候貌似是以日志文件为源，备份过的日志删除。

If you had specified DELETE ALL INPUT RMAN backs up only one copy of each log sequence number in these archiving locations.it deletes all copies of any log that it backed up from the other archiving destinations
如果指定delete all input RMAN对于所有归档目录中的日志序列号只备份一次，同时rman会删除dest1 和dest2 中所有归档日志。
结论：对于仅有一个归档目录 delete input 和delet all input 没啥区别。

六 rman备份恢复对归档位置的说明

注意：
1 当需要执行恢复时，rman会自动从备份恢复归档日志，如果归档备份的的话。
2 参数 log_archive_format 和 log_archive_dest_n 决定了rman恢复时获取归档的路径和名字。
eg
SQL> show parameter log_archive_dest_1;

NAME TYPE VALUE

log_archive_dest_1 string LOCATION=/oracle/archive

SQL> show parameter log_archive_format;

NAME TYPE VALUE

log_archiveformat string %t%s_%r.dbf

SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: ‘/oracle/test/test2.dbf‘

SQL> select * from v$recoverfile;
FILE# ONLINE ONLINE ERROR CHANGE# TIME

13 ONLINE  ONLINE  FILE NOT FOUND                0

[ ~]$ rman target /

Recovery Manager: Release 11.2.0.2.0 - Production on Sun May 18 13:10:18 2014

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

connected to target database: CRM (DBID=3601019238, not open)

RMAN> run{
2> restore datafile 13;
3> recover datafile 13;
4> sql‘alter database open‘;
5> }

Starting restore at 18-MAY-14
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=85 device type=DISK

channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00013 to /oracle/test/test2.dbf
channel ORA_DISK_1: reading from backup piece /backup/fullbk_20140518_09p8jeov_1_1.bk
channel ORA_DISK_1: piece handle=/backup/fullbk_20140518_09p8jeov_1_1.bk tag=TAG20140518T121214
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
Finished restore at 18-MAY-14

Starting recover at 18-MAY-14
using channel ORA_DISK_1

starting media recovery

archived log for thread 1 with sequence 80 is already on disk as file /oracle/archive/1_80_839187351.dbf
channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=64
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=65
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=66
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=67
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=68
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=69
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=70
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=71
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=72
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=73
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=74
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=75
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=76
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=77
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=78
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=79
channel ORA_DISK_1: reading from backup piece /backup/archbk_20140518_0cp8jg8f_1_1.bak
channel ORA_DISK_1: piece handle=/backup/archbk_20140518_0cp8jg8f_1_1.bak tag=TAG20140518T123735
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/oracle/archive/1_64_839187351.dbf thread=1 sequence=64
archived log file name=/oracle/archive/1_65_839187351.dbf thread=1 sequence=65
archived log file name=/oracle/archive/1_66_839187351.dbf thread=1 sequence=66
archived log file name=/oracle/archive/1_67_839187351.dbf thread=1 sequence=67
archived log file name=/oracle/archive/1_68_839187351.dbf thread=1 sequence=68
archived log file name=/oracle/archive/1_69_839187351.dbf thread=1 sequence=69
archived log file name=/oracle/archive/1_70_839187351.dbf thread=1 sequence=70
archived log file name=/oracle/archive/1_71_839187351.dbf thread=1 sequence=71
archived log file name=/oracle/archive/1_72_839187351.dbf thread=1 sequence=72
archived log file name=/oracle/archive/1_73_839187351.dbf thread=1 sequence=73
archived log file name=/oracle/archive/1_74_839187351.dbf thread=1 sequence=74
archived log file name=/oracle/archive/1_75_839187351.dbf thread=1 sequence=75
media recovery complete, elapsed time: 00:00:01
Finished recover at 18-MAY-14

sql statement: alter database open

RMAN> exit

Recovery Manager complete.
[ ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.2.0 Production on Sun May 18 13:13:11 2014

Copyright (c) 1982, 2010, Oracle. All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select * from v$recover_file;

no rows selected

SQL> select open_mode from v$database;

OPEN_MODE

READ WRITE

1 从归档备份恢复归档到新的位置
run{
set archivelog destination to ‘/oracle/archive/test/‘;
restore archivelog from sequence 64;
}
eg

RMAN> run{
2> set archivelog destination to ‘/oracle/archive/test/‘;
3> restore archivelog from sequence 64;
4> }

executing command: SET ARCHIVELOG DESTINATION

Starting restore at 18-MAY-14
using channel ORA_DISK_1

channel ORA_DISK_1: starting archived log restore to user-specified destination
archived log destination=/oracle/archive/test/
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=64
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=65
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=66
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=67
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=68
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=69
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=70
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=71
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=72
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=73
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=74
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=75
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=76
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=77
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=78
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=79
channel ORA_DISK_1: reading from backup piece /backup/archbk_20140518_0cp8jg8f_1_1.bak
channel ORA_DISK_1: piece handle=/backup/archbk_20140518_0cp8jg8f_1_1.bak tag=TAG20140518T123735
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:04
Finished restore at 18-MAY-14

2 调用新位置的归档进行数据库恢复
run{
set archivelog destination to ‘/oracle/archive/test/‘;
restore datafile 13;
recover datafile 13;
sql‘alter database open‘;
}
eg
SQL> startup
ORACLE instance started.

Total System Global Area 1043886080 bytes
Fixed Size 2233088 bytes
Variable Size 327159040 bytes
Database Buffers 708837376 bytes
Redo Buffers 5656576 bytes
Database mounted.
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: ‘/oracle/test/test2.dbf‘

SQL> select * from v$recover_file;

FILE# ONLINE  ONLINE_ ERROR                       CHANGE# TIME
13 ONLINE  ONLINE  FILE NOT FOUND                0

QL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[ ~]$ rman target /

Recovery Manager: Release 11.2.0.2.0 - Production on Sun May 18 12:56:03 2014

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

connected to target database: CRM (DBID=3601019238, not open)

RMAN> run{
2> set archivelog destination to ‘/oracle/archive/test/‘;
3> restore datafile 13;
4> recover datafile 13;
5> sql‘alter database open‘;
6> }

executing command: SET ARCHIVELOG DESTINATION
using target database control file instead of recovery catalog

Starting restore at 18-MAY-14
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=85 device type=DISK

channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00013 to /oracle/test/test2.dbf
channel ORA_DISK_1: reading from backup piece /backup/fullbk_20140518_09p8jeov_1_1.bk
channel ORA_DISK_1: piece handle=/backup/fullbk_20140518_09p8jeov_1_1.bk tag=TAG20140518T121214
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
Finished restore at 18-MAY-14

Starting recover at 18-MAY-14
using channel ORA_DISK_1

starting media recovery

archived log for thread 1 with sequence 64 is already on disk as file /oracle/archive/test/1_64_839187351.dbf
archived log for thread 1 with sequence 65 is already on disk as file /oracle/archive/test/1_65_839187351.dbf
archived log for thread 1 with sequence 66 is already on disk as file /oracle/archive/test/1_66_839187351.dbf
archived log for thread 1 with sequence 67 is already on disk as file /oracle/archive/test/1_67_839187351.dbf
archived log for thread 1 with sequence 68 is already on disk as file /oracle/archive/test/1_68_839187351.dbf
archived log for thread 1 with sequence 69 is already on disk as file /oracle/archive/test/1_69_839187351.dbf
archived log for thread 1 with sequence 70 is already on disk as file /oracle/archive/test/1_70_839187351.dbf
archived log for thread 1 with sequence 71 is already on disk as file /oracle/archive/test/1_71_839187351.dbf
archived log for thread 1 with sequence 72 is already on disk as file /oracle/archive/test/1_72_839187351.dbf
archived log for thread 1 with sequence 73 is already on disk as file /oracle/archive/test/1_73_839187351.dbf
archived log for thread 1 with sequence 74 is already on disk as file /oracle/archive/test/1_74_839187351.dbf
archived log for thread 1 with sequence 75 is already on disk as file /oracle/archive/test/1_75_839187351.dbf
archived log for thread 1 with sequence 76 is already on disk as file /oracle/archive/test/1_76_839187351.dbf
archived log for thread 1 with sequence 77 is already on disk as file /oracle/archive/test/1_77_839187351.dbf
archived log for thread 1 with sequence 78 is already on disk as file /oracle/archive/test/1_78_839187351.dbf
archived log for thread 1 with sequence 79 is already on disk as file /oracle/archive/test/1_79_839187351.dbf
archived log file name=/oracle/archive/test/1_64_839187351.dbf thread=1 sequence=64
archived log file name=/oracle/archive/test/1_65_839187351.dbf thread=1 sequence=65
archived log file name=/oracle/archive/test/1_66_839187351.dbf thread=1 sequence=66
archived log file name=/oracle/archive/test/1_67_839187351.dbf thread=1 sequence=67
archived log file name=/oracle/archive/test/1_68_839187351.dbf thread=1 sequence=68
archived log file name=/oracle/archive/test/1_69_839187351.dbf thread=1 sequence=69
archived log file name=/oracle/archive/test/1_70_839187351.dbf thread=1 sequence=70
archived log file name=/oracle/archive/test/1_71_839187351.dbf thread=1 sequence=71
archived log file name=/oracle/archive/test/1_72_839187351.dbf thread=1 sequence=72
archived log file name=/oracle/archive/test/1_73_839187351.dbf thread=1 sequence=73
archived log file name=/oracle/archive/test/1_74_839187351.dbf thread=1 sequence=74
media recovery complete, elapsed time: 00:00:01
Finished recover at 18-MAY-14

sql statement: alter database open

RMAN> exit

Recovery Manager complete.
[ ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.2.0 Production on Sun May 18 12:57:06 2014

Copyright (c) 1982, 2010, Oracle. All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select * from v$recover_file;

no rows selected

八、 删除归档
1 如何正确的删除归档
删除数据库归档前，应该对数据库做一次全备份，为何这样说呢，举个简单的例子 当前oracle有6组日志组，seq号分别是 33、34、35、36、37、38，当前日志组seq号是38，
归档日志seq号从1到37，此时我们对数据库做全备份，当数据库需要进行恢复时，restore后数据文件头部的rba seq号为38，之后执行recover这个动作数据库会从seq号为38号的归档或者联机日志开始。seq号为38之前的归档，恢复时已经不需要了。这也就是我们为啥说对数据库做一次全备份后
即可删除所有归档的原因。

2 如何正确的在操作系统上删除归档
需要明确的一点就是，通过操作系统命令删除归档，rman资料库里面记录该归档的状态为A即为avaliable，这样就造成了rman资料库归档条目状态不一致性，因此当
我们在操作系统上删除了归档后，还应该发起一个crosscheck archivelog all 命令，用于校验rman资料库中的每一条归档记录在数据库上是否存在，如果不存在则更改
改归档条目的记录状态为expired。之后我们便可用命令delete noprompt expired archivelog all 删除rman资料库中所有标记为EXPIRED状态的条目。
eg 命令如下：
rm -rf ×
rman target /
crosscheck archivelog all;
delete noprompt expired archivelog all;

3 在rman下如何删除归档
删除系统内的所有归档:delete noprompt archivelog all
删除7天内以外的所有归档：delete noprompt archivelog all completed before ‘SYSDATE - 7‘;

log oracle oracle归档模式 oracle数据库

Carlos

Carlos

0 关注 0 粉丝 0 动态

关注 关注

相关推荐

RabbitMQ如何保证消息的可靠投递？

String message = "this is info message " + i;autoAck=false: RabbitMQ会等待消费者显示回复确认消息后才从内存中移出消息。deliveryTag: 用来标识信道中投递的消息

zhuxue 2020-10-14

Linux后台执行命令：&与nohup的用法

大家可能有这样的体验：某个程序运行的时候，会产生大量的log，但实际上我们只想让它跑一下而已，log暂时不需要或者后面才有需要。所以在这样的情况下，我们希望程序能够在后台进行，也就是说，在终端上我们看不到它所打出的log。为了实现这个需求，我们介绍以下几种

zhangbingb 2020-09-21

Linux 入侵痕迹清理技巧

本文转载自微信公众号「 Bypass」，作者 Bypass 。在攻击结束后，如何不留痕迹的清除日志和操作记录，以掩盖入侵踪迹，这其实是一个细致的技术活。你所做的每一个操作，都要被抹掉;你所上传的工具，都应该被安全地删掉。编辑history记录文件，删除部分

HeronLinuxampARM 2020-09-14

为什么排序的复杂度为O(N log N)

基本上所有正而八经的算法教材都会解释像快速排序quicksort和堆排序heapsort这样的排序算法有多快，但并不需要复杂的数学就能证明你可以逐渐趋近的速度有多快。大多数计算机专业的科学家使用大写字母 O 标记来指代“趋近，直到到达一个常数比例因子”，这

美丽的泡沫 2020-09-08

Filebeat简介

Filebeat附带预构建的模块，这些模块包含收集、解析、充实和可视化各种日志文件格式数据所需的配置，每个Filebeat模块由一个或多个文件集组成，这些文件集包含摄取节点管道、Elasticsearch模板、Filebeat勘探者配置和Kibana仪表盘

goodstudy 2020-08-19

JS中DOM元素的操作

<button id="btn" class="btnlist" name="btn_n">点我一下</button>. innerHTML语法: ele.innerHTM

luvhl 2020-08-17

javascript解析json格式的数据方法详解

JSON 是一种简单的数据格式，比xml更轻巧。它是 JavaScript 原生格式，这意味着在 JavaScript 中处理 JSON 数据不需要任何特殊的 API 或工具包。那么如何用JavaScript来解析json呢？var o={“key”:”v

littleFatty 2020-08-16

MySQL是如何保证数据的完整性

数据的一致性和完整性对于在线业务的重要性不言而喻，如何保证数据不丢呢？今天我们就探讨下关于数据的完整性和强一致性，MySQL做了哪些改进。在Oracle和MySQL这种关系型数据库中，讲究日志先行策略,只要日志持久化到磁盘，就能保证MySQL异常重启后，数

gamestart0 2020-08-15

mysql解决时区相关问题

在使用 MySQL 的过程中，你可能会遇到时区相关问题，比如说时间显示错误、时区不是东八区、程序取得的时间和数据库存储的时间不一致等等问题。其实，这些问题都与数据库时区设置有关，本篇文章将从数据库参数入手，逐步介绍时区相关内容。log_timestamps

URML 2020-08-15

如何在JavaScript实现休眠或等待功能，实现sleep函数

JavaScript不具有 sleep() 函数，该函数会导致代码在恢复执行之前等待指定的时间段。JavaScript中没有 sleep() 方法，所以你可以尝试使用下一个最好的方法 setTimeout()。不幸的是，setTimeout() 不能像你

sfkong 2020-08-02

debian apach2 wsgi 自定义log logrotate 之后无权限访问

今天测试发现web打不开了，看下error.log发现是自定义log属主变成了root adm，apache2无法访问，后来搜索发现，apache2的日志由logrotate定期压缩备份清理，看了下/etc/logrotate.d/apache2 的配置有

82941732 2020-07-27

es6 Promise 对象、.then()

// resolve // 状态改成fulfilled. },=>{ // 第二个回调 成功reject

whynotgonow 2020-07-26

filebeat配置文件

#input设置，支持Docker,Container,HTTP JSON,Log,Kafka,MQTT,NetFlow,Redis,TCP,DCP,Syslog,Stdin. #output设置，可以output到kafka,logstash,elast

偏头痛杨 2020-07-18

mysql的日志模块

连接器-------->分析器------->优化器--------->执行器-------->存储引擎 #如下图。一家商店有一个记账板，当赊账顾客多的时候，会临时记录在记账板上，避免频繁去记账本上查找更新对应顾客的信息。避免高峰

timewind 2020-07-04

Golang保存PostgreSQL数据至结构

db, err := sql.Open("postgres", "user=admin password=123456 dbname=test sslmode=disable"). if err != nil {.

89407707 2020-06-27

封装excel数据层代码，log模块导入

封装excel操作代码，提高复用率。整体封装思想阐述：。表内用例格式构建。首先获取表体第一行的数据组成的列表。之后逐条将表头与数据zip封包，之后转换为字典。从excel中读取的数据，除了数值，其他不管保存的时候什么格式，读取出来都是str. 解决该问参考

xiaoxiaoCNDS 2020-06-26

TypeScript（13）： 元组

我们知道数组中元素的数据类型都一般是相同的，如果存储的元素数据类型不同，则需要使用元组。元组中元素使用索引来访问，第一个元素的索引值为 0，第二个为 1，以此类推第 n 个为 n-1，语法格式如下:. console.log // 返回元组的大小。m

lyjava 2020-06-26

TypeScript（06）： 运算符

运算符用于执行程序代码运算，会针对一个以上操作数项目来进行运算。以上实例中 7、5 和 12 是操作数。关系运算符用于计算结果是否为 true 或者 false。逻辑运算符用于测定变量或值之间的逻辑。

ChaITSimpleLove 2020-06-25

nginx 日志切割

nginx 日志一般都是两种access.log error.log ，可以每个location 区域配置一份，也就是每个请求服务一个日志。它的日志不会自动切割，需要人为根据时间或者日志量切割。　　LOG_PATH=/opt/nginx/logs 　

Strongding 2020-06-25

CentOS 7 如何清空文件内容

方法1、在非编辑状态下使用快捷键gg跳至首行头部，再使用dG即可。方法2、cat /dev/null > /var/log/yum.log

Aveiox 2020-06-23
Carlos

Carlos

W3CSchool教程
HTML 教程
CSS 教程
Bootstrap 教程
Javascript 教程
jQuery 教程
后端教程
C 教程
Java 教程
PHP 教程
Python 教程
Go 教程
移动开发
Android 教程
Swift 教程
Kotlin 教程
jQuery Mobile 教程
ionic 教程
关于我们
新闻动态
联系方式
招聘英才
安科实验室
帮助与反馈

安科网(Ancii)，中国第一极客网

Copyright © 2013 - 2019 Ancii.com

京ICP备18063983号 京公网安备11010802014868号