rac四个节点 如果把归档放在本地目录,是否其他节点能否访问到归档

本文介绍 Oracle RAC 环境下归档日志的两种管理方案,并展示了如何通过 SQL 和 RMAN 命令查看及删除归档日志。强调了共享存储在归档日志管理中的重要性。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

归档位置的设计也有两种方案:

1)各节点生成的归档放到共享存储上,这样自然可以确保每个节点都能够访问到,比如将归档存放到ORACLE的ASM,或者是第三方提供的集群文件系统中。 对于这种方法,一些集群的配置比较麻烦,而且也增加了ASM的维护,出现问题也不好处理。

2)各节点除在本地生成归档文件外,另外向其它节点或者说执行备份的节点发送归档日志,以确保执行备份的那台节点能够访问到所有的归档文件。在这种方法中,因为ORACLE 的重做日志发送机制非常灵活,在10g版本中可以同时向10个目标地写入归档(11g增加到了30个),所以利用这种特性,将各节点生成的归档发送到执行备份的节点中,来实现该节点能够访问所需的归档文件。

 

 

 

1 .查看节点4归档

 

SQL> archive log list
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /u01/app/oracle/product/RAC11g/dbs/arch
Oldest online log sequence     5
Next log sequence to archive   7
Current log sequence           7
SQL>

 

2.  查看节点3归档

 

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

SQL> archive log list
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /u01/app/oracle/product/RAC11g/dbs/arch
Oldest online log sequence     5
Next log sequence to archive   7
Current log sequence           7
SQL>

 

 

3 在节点3使用rman命令查看归档

 

[oracle ~]$ rman target /

Recovery Manager: Release 11.2.0.3.0 - Production on Mon Dec 2 08:56:39 2013

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

connected to target database: BSQQNS (DBID=4291392101)

RMAN> crosscheck  archivelog all;

using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1710 instance=bsqqns3 device type=DISK
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch1/1_30_828441637.dbf RECID=41 STAMP=832111230
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch2/1_31_828441637.dbf RECID=43 STAMP=832196175
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch2/1_32_828441637.dbf RECID=44 STAMP=832196176
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch1/1_33_828441637.dbf RECID=46 STAMP=832378465
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch2/1_34_828441637.dbf RECID=48 STAMP=832503828
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch1/1_35_828441637.dbf RECID=49 STAMP=832503832
validation succeeded for archived log
archived log file name=/u01/app/oracle/product/RAC11g/dbs/arch1_36_828441637.dbf RECID=52 STAMP=832590189
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch2/1_37_828441637.dbf RECID=59 STAMP=832591234
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch1/1_38_828441637.dbf RECID=60 STAMP=832601328
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch1/1_39_828441637.dbf RECID=64 STAMP=832605107
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch1/1_40_828441637.dbf RECID=65 STAMP=832605355
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch1/1_41_828441637.dbf RECID=66 STAMP=832707028
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch1/1_42_828441637.dbf RECID=70 STAMP=832707183
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch1/1_43_828441637.dbf RECID=71 STAMP=832760776
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch1/1_44_828441637.dbf RECID=74 STAMP=832983828
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch1/1_45_828441637.dbf RECID=77 STAMP=833094028
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch2/2_20_828441637.dbf RECID=42 STAMP=832196175
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch2/2_21_828441637.dbf RECID=45 STAMP=832196517
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch2/2_22_828441637.dbf RECID=47 STAMP=832503780
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch2/2_23_828441637.dbf RECID=53 STAMP=832590189
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch2/2_24_828441637.dbf RECID=54 STAMP=832590380
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch2/2_25_828441637.dbf RECID=62 STAMP=832605099
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch2/2_26_828441637.dbf RECID=68 STAMP=832707167
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch2/2_27_828441637.dbf RECID=73 STAMP=832814800
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch2/2_28_828441637.dbf RECID=75 STAMP=833088605
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch1/3_1_828441637.dbf RECID=50 STAMP=832505138
validation succeeded for archived log
archived log file name=/u01/app/oracle/product/RAC11g/dbs/arch3_2_828441637.dbf RECID=56 STAMP=832590759
validation succeeded for archived log
archived log file name=/u01/app/oracle/product/RAC11g/dbs/arch3_3_828441637.dbf RECID=57 STAMP=832591189
validation succeeded for archived log
archived log file name=/u01/app/oracle/product/RAC11g/dbs/arch3_4_828441637.dbf RECID=61 STAMP=832605098
validation succeeded for archived log
archived log file name=/u01/app/oracle/product/RAC11g/dbs/arch3_5_828441637.dbf RECID=69 STAMP=832707171
validation succeeded for archived log
archived log file name=/u01/app/oracle/product/RAC11g/dbs/arch3_6_828441637.dbf RECID=72 STAMP=832777111
validation succeeded for archived log
archived log file name=+BSQQNS/bsqqns/arch2/4_1_828441637.dbf RECID=51 STAMP=832505278
validation failed for archived log
archived log file name=/u01/app/oracle/product/RAC11g/dbs/arch4_2_828441637.dbf RECID=55 STAMP=832590440
validation failed for archived log
archived log file name=/u01/app/oracle/product/RAC11g/dbs/arch4_3_828441637.dbf RECID=58 STAMP=832591190
validation failed for archived log
archived log file name=/u01/app/oracle/product/RAC11g/dbs/arch4_4_828441637.dbf RECID=63 STAMP=832605100
validation failed for archived log
archived log file name=/u01/app/oracle/product/RAC11g/dbs/arch4_5_828441637.dbf RECID=67 STAMP=832707166
validation failed for archived log
archived log file name=/u01/app/oracle/product/RAC11g/dbs/arch4_6_828441637.dbf RECID=76 STAMP=833094015
Crosschecked 37 objects

 

注:在节点3能否查看各节点的归档

 

4 在节点3删除各节点归档

 

[oracle@qnsdb4 dbs]$ rman target /

Recovery Manager: Release 11.2.0.3.0 - Production on Mon Dec 2 09:08:54 2013

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

connected to target database: BSQQNS (DBID=4291392101)

RMAN> delete archivelog all;

using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1710 instance=bsqqns4 device type=DISK
List of Archived Log Copies for database with db_unique_name BSQQNS
=====================================================================

Key     Thrd Seq     S Low Time
------- ---- ------- - ---------
80      1    46      A 02-DEC-13
        Name: +BSQQNS/bsqqns/arch1/1_46_828441637.dbf

78      2    29      A 02-DEC-13
        Name: +BSQQNS/bsqqns/arch2/2_29_828441637.dbf

81      3    7       A 29-NOV-13
        Name: /u01/app/oracle/product/RAC11g/dbs/arch3_7_828441637.dbf

79      4    7       A 02-DEC-13
        Name: /u01/app/oracle/product/RAC11g/dbs/arch4_7_828441637.dbf


Do you really want to delete the above objects (enter YES or NO)? YES
deleted archived log
archived log file name=+BSQQNS/bsqqns/arch1/1_46_828441637.dbf RECID=80 STAMP=833101499
deleted archived log
archived log file name=+BSQQNS/bsqqns/arch2/2_29_828441637.dbf RECID=78 STAMP=833101494
deleted archived log
archived log file name=/u01/app/oracle/product/RAC11g/dbs/arch4_7_828441637.dbf RECID=79 STAMP=833101496
Deleted 3 objects

RMAN-06207: WARNING: 1 objects could not be deleted for DISK channel(s) due
RMAN-06208:          to mismatched status.  Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212:   Object Type   Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Archivelog      /u01/app/oracle/product/RAC11g/dbs/arch3_7_828441637.dbf


RMAN>

 

注:最好把归档设置在共享目录上,在一个节点就能删除归档日志,否则的话,不能删除其他非共享的归档日志

 

 

本地自己的操作系统上,完全模拟生产环境,让学员跟着视频一步一步搭建一套在RHEL7操作系统上面的oracle19c的rac环境。同时学员还会学会DNS服务器,DNS客户端,NTP服务器,NTP客户端等操作系统知识。让学员在短时间内,oracle和操作系统知识,有一定的提升。让学员可以独自轻松安装一套oracle rac环境。一课程主题 模拟生产环境,用多路径共享存储,用虚拟软件安装一套RHEL7.5+oracle19c+rac+打补丁二课程特色 完成模拟生产环境,用openfiler软件模拟生产惠普的3par存储,用2个虚拟网卡模拟数据库服务器的2个HBA卡。课程以实践为主,从头到尾一步一步教学员怎样操作,实践性强模拟生产需求,完全可以把这套环境拿到生产环境安装三课程内容 1.课程结束成果演示    1.1 用workstation,安装一套rhel7+oracle19c+rac+multipath+共享存储+DNS服务器+DNS客户端+NTP服务器+NTP客户端的生产环境    1.2 怎样打oracle19c的rac补丁(包括GI补丁,oracle补丁,数据库补丁,OJVM补丁,bug补丁)2.安装openfiler软件,模拟共享存储+配置多路径访问    2.1安装openfiler软件   2.2配置openfiler软件(配置2个虚拟网卡,模拟服务器的2个HBA卡)   2.3创建ocr磁盘   2.4创建mgmt磁盘   2.5创建数据文件磁盘   2.6创建归档日志磁盘3.安装2台数据库服务器    3.1安装2台数据库服务器RHEL7.5   3.2配置服务器双网卡绑定+配置服务器心跳线4.安装多路径软件识别共享存储中的磁盘     4.1安装服务器本地yum源    4.2安装iscsi软件,配置多路径配置文件,识别共享存储中的磁盘    4.3识别ocr磁盘    4.4识别mgmt磁盘    4.5识别数据文件磁盘    4.6识别归档日志磁盘5.oracle19c的rac环境系统参数官方说明     5.1如何配置oracle19c的rac的系统参数(我们参考官方说明)    5.2oracle19c+rac环境Best Practices 官方说明文档6.安装oracle19c+rac之前的准备工作     6.1修改/etc/hosts文件    6.2配置DNS服务器+DNS客户端+NTP服务器+NTP客户端    6.3创建用户和组    6.4创建目录    6.5修改用户环境变量    6.6安装相关软件包    6.7配置ssh互信    6.9禁用服务器透明大页7.安装oracle+19c+rac软件    7.1安装GI软件   7.2创建ASM磁盘,主要是数据文件磁盘和归档日志磁盘   7.3安装数据库软件   7.4创建数据库实例   7.5日常常用维护集群命令(启停数据库,启停集群,查看监听,教同学们怎样不死记命令,而且命令还正确)8.打补丁   8.1打GI和ORACLE的操作系统补丁  8.2打OJVM补丁  8.3打ORA600的bug补丁9.课程总结和成果演示  9.1课程总结和成果演示 四学习必要工具 安装workstation软件  官网下载openfiler,rhel7.5软件下载oracle软件(包括19.3的rac安装包,19.4的补丁)以上软件我都已经在视频里面做了下载地址说明五课程纠错1)rac的私有ip应该是不同的网段,我在视频中设置错误。Ensure all private Ethernet interfaces are set to different subnets on each node. If different subnets are not used and connectivity is lost, this can cause a node reboot within the cluster2)配置好multipath,以及多路径的别名后,还要增加如下配置文件。[root@hellorac1 rules.d]# cat /etc/udev/rules.d/99-persistent.rulesENV==data, OWNER:=grid, GROUP:=asmadmin, MODE:=660上面的配置文件增加成功后,运行如下命令:#udevadm control --reload-rules#/sbin/udevadm trigger --type=devices --action=change执行完成之后,会发现/dev/dm*相应的磁盘权限变成grid.asmadmin. 视频中只运行了udevadm control --reload-rules。3)安装GI部分1和部分2,先看部分2,再看部分1.特此纠正上面的3个错误。谢谢大家的支持和厚爱。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值