两次 backup archivelog like

简介: 试试在12.1~19c的RAC连续运行两次 backup archivelog like ‘+%’ not backed up 1 times

试试在12.1~19c的RAC连续运行两次 backup archivelog like ‘+%’ not backed up 1 times; 看第二次有没有归档日志

检查归档日志

[oracle@rac1 ~]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Tue Sep 22 04:52:56 2020
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle.  All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0
SQL> select name from v$archived_log;
NAME
--------------------------------------------------------------------------------
+DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_2_seq_1.271.1051712653
+DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_1_seq_5.272.1051712689
+DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_2_seq_2.273.1051714497
+DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_1_seq_6.274.1051714499
+DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_1_seq_7.275.1051714499
+DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_2_seq_4.280.1051746963
+DATA/SCUTECH/ARCHIVELOG/2020_09_22/thread_2_seq_5.282.1051749313
+DATA/SCUTECH/ARCHIVELOG/2020_09_22/thread_1_seq_8.281.1051748533
+DATA/SCUTECH/ARCHIVELOG/2020_09_22/thread_2_seq_3.279.1051748549
9 rows selected.



第一次备份归档日志

RMAN> backup archivelog like '++DATA/SCUTECH/ARCHIVELOG.%' not backed up 1 times; 
Starting backup at 22-SEP-20
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=250 instance=scutech1 device type=DISK
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 22-SEP-20
RMAN> backup archivelog like '+DATA/SCUTECH/ARCHIVELOG/2020_09_22/thread_2_seq_3.279%' not backed up 1 times; 
Starting backup at 22-SEP-20
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=2 sequence=3 RECID=9 STAMP=1051751667
channel ORA_DISK_1: starting piece 1 at 22-SEP-20
channel ORA_DISK_1: finished piece 1 at 22-SEP-20
piece handle=/opt/oracle/app/oracle/product/19c/dbhome_1/dbs/02vb1a8r_1_1 tag=TAG20200922T045658 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:20:56
Finished backup at 22-SEP-20
Starting Control File and SPFILE Autobackup at 22-SEP-20
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 09/22/2020 05:25:41
ORA-00245: control file backup failed; in Oracle RAC, target might not be on shared storage
RMAN> 
RMAN>


检查第一次备份归档日志后的日志

SQL> col name form a70
SQL> select FIRST_TIME,NAME from v$archived_log;
FIRST_TIME  NAME
----------------------- ----------------------------------------------------------------------
Sep 21 2020 14:24:10  +DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_2_seq_1.271.1051712653
Sep 21 2020 14:18:20  +DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_1_seq_5.272.1051712689
Sep 21 2020 14:27:08  +DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_2_seq_2.273.1051714497
Sep 21 2020 14:24:47  +DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_1_seq_6.274.1051714499
Sep 21 2020 14:54:54  +DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_1_seq_7.275.1051714499
Sep 21 2020 22:54:11  +DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_2_seq_4.280.1051746963
Sep 22 2020 00:00:21  +DATA/SCUTECH/ARCHIVELOG/2020_09_22/thread_2_seq_5.282.1051749313
Sep 21 2020 15:18:15  +DATA/SCUTECH/ARCHIVELOG/2020_09_22/thread_1_seq_8.281.1051748533
Sep 21 2020 14:54:55  +DATA/SCUTECH/ARCHIVELOG/2020_09_22/thread_2_seq_3.279.1051748549
9 rows selected.

第2次备份

RMAN>  backup archivelog like '+DATA/SCUTECH/ARCHIVELOG/2020_09_22/thread_2_seq_3.279%' not backed up 1 times; 
Starting backup at Sep 22 2020 05:30:12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=255 instance=scutech1 device type=DISK
skipping archived log of thread 2 with sequence 3; already backed up
Finished backup at Sep 22 2020 05:30:13
RMAN> quit


检查第2次备份归档日志后的日志

SQL> SQL>  set linesize 200
SQL> select FIRST_TIME,NAME from v$archived_log;
FIRST_TIME  NAME
----------------------- ----------------------------------------------------------------------
Sep 21 2020 14:24:10  +DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_2_seq_1.271.1051712653
Sep 21 2020 14:18:20  +DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_1_seq_5.272.1051712689
Sep 21 2020 14:27:08  +DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_2_seq_2.273.1051714497
Sep 21 2020 14:24:47  +DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_1_seq_6.274.1051714499
Sep 21 2020 14:54:54  +DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_1_seq_7.275.1051714499
Sep 21 2020 22:54:11  +DATA/SCUTECH/ARCHIVELOG/2020_09_21/thread_2_seq_4.280.1051746963
Sep 22 2020 00:00:21  +DATA/SCUTECH/ARCHIVELOG/2020_09_22/thread_2_seq_5.282.1051749313
Sep 21 2020 15:18:15  +DATA/SCUTECH/ARCHIVELOG/2020_09_22/thread_1_seq_8.281.1051748533
Sep 21 2020 14:54:55  +DATA/SCUTECH/ARCHIVELOG/2020_09_22/thread_2_seq_3.279.1051748549
9 rows selected.
相关实践学习
日志服务之使用Nginx模式采集日志
本文介绍如何通过日志服务控制台创建Nginx模式的Logtail配置快速采集Nginx日志并进行多维度分析。
相关文章
|
1月前
19c restore standby controlfile from servic
restore standby controlfile from servic
18 0
|
关系型数据库 MySQL 数据库
|
关系型数据库 MySQL 数据库
|
关系型数据库 MySQL 数据库
|
SQL 数据库 数据库连接
RMAN备份与ORA-19625&ORA-19502
    常州一地区负责人嚎哭,他业务全停了,说是数据库连接不上了,原因是RMAN备份引起的,具体原因分析请看下文。     1、首先,看系统存储情况,如下图: 系统负责人说,D盘和E盘都有数据库文件,数据库备份在E盘。
1180 0
|
SQL Oracle 关系型数据库
[20160720]rman set newname for datafile
[20160720]rman set newname for datafile本质.txt --前几天在恢复历史数据库,因为生产系统数据库是asm,恢复必须要转成文件类型。
1452 0
|
Oracle 关系型数据库
[20160712]logminer 与rman 删除archivelog
[20160712]logminer 与rman 删除archivelog.txt --昨天晚上使用logminer遇到的问题,主要后台的rman脚本正好删除需要的archivelog。
1434 0