How To Enable Archive Log Mode In a RAC Environment

How To Enable Archive Log Mode In a RAC Environment (文档 ID 1963148.1)

APPLIES TO:

Oracle Applications Manager - Version 12.2 to 12.2 [Release 12.2]

Information in this document applies to any platform.

GOAL

How to enable archive log mode In a RAC Environment?

SOLUTION

A. The following steps need to be taken to enable archive logging in a RAC database environment:

1. Shutdown immediate all database instances:

$ srvctl stop database -d

2. Startup the database in mount mode:

$ srvctl start database -d -o mount

3. Enable archive logging:

$ sqlplus / as sysdba
sql> alter database archivelog;
sql> exit;

4. Stop the database.

$ srvctl stop database -d

5. Re-start all database instances:

$ srvctl start database -d

6. Verify archiving is enabled/disabled by running the following command:

sql> archive log list;

Note: There may be a  need to set your log_archive_dest(_n) parameters to a shared location in each spfile, but the log_archive_start parameter does not need to be set anymore as of 10g (See Note 274302.1) for more details.

B. To disable archive logging, follow the same steps above, but use the NOARCHIVELOG clause of the ALTER DATABASE statement.

Please note, from 10.2 onwards, it is no longer required to modify cluster_database parameter to change archive log mode. Please refer to:

Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide
What‘s New in Oracle Real Application Clusters Administration and Deployment?

"Changing the Archiving Mode

There is no longer a need to modify the CLUSTER_DATABASE parameter setting to change the archiving mode in Oracle RAC. Instead, change archive log mode as long as the database is mounted in the local instance and not open in any instances."

REFERENCES

NOTE:1186764.1 - How To Enable/Disable Archive Logging In RAC Environment for 10.2 and higher version
NOTE:371139.1 - How to Enable/Disable Archive Log Mode In 10g and 11g

时间: 2024-11-06 07:28:06

How To Enable Archive Log Mode In a RAC Environment的相关文章

ORA-16009 remote archive log destination must be a STANDBY database

ORA-16009错误处理 问题描述: 主备在做Switchover切换时,在切换后的备库报如下错误: Wed Jul 22 04:49:02 2015 Errors in file /u01/app/oracle/admin/orcl/bdump/orcl_arc0_8755.trc: ORA-16009: remote archive log destination must be a STANDBY database 解决办法: 查看主库log_archive_dest_2 参数,结果此参

ORA-00257 archive log 日志已满

ORA-00257 archive log 日志已满 报错信息: ORA-00257: archiver error. Connect internal only, until freed   原因: 归档日志已满 解决办法: 1. 用sys用户登录   sqlplus sys as sysdba 2. 看看archivlog所在位置 SQL> show parameter log_archive_dest; 3. 如果VALUE为空时,可以用archive log list;检查一下归档目录和

How to delete expired archive log files using rman?

he following commands will helpful to delete the expired archive log files using Oracle Recovery Manager(RMAN).Connect to the Rman prompt and try the bellow commands. RMAN>list expired archivelog all; RMAN>crosscheck archivelog all; RMAN>delete n

DBA_Oracle Archive Log的基本应用和启用(概念)

2014-11-15 BaoXinjian 一.摘要 归档日志即重做日志的备份,使用归档日志的目的是为了实现介质恢复. 日志操作模式 1. Noarchivelog(非归档模式) 不保存重做日志. 不能在open状态下进行物理备份:要定期执行完全数据库备份:只能将数据库恢复到上次的完全备份点. 2. Archivelog 当进行日志切换时,ARCH进程会将重做日志的内容复制到归档日志中. 在归档重做日志前,新事务变化不能覆盖旧事务变化. 可以在open 状态下进行物理备份. 可以将数据库恢复到失

[Oracle维护工程师手记系列]为什么flashback 的时候既需要 flashback log ,又需要 archive log?

为什么flashback 的时候既需要 flashback log ,又需要 archive log 呢? 如果数据库的活动不是很频繁,可以看到,其flashback log 是比较小的.那么是通过怎样的方式 flashback 到过去的呢? 示意如下: 12:50 第一次更改数据(100-->200) 1:00 进行 第一次 flashback log 写入. 记录内容是 更改前的数据:100 1:10 第二次更改数据(200-->300) 1:30 再进行下一次flashback log 

Warning. Log sequence in archive filename wrapped to fix length as indicated by %S in LOG_ARCHIVE_F

最近在做数据库检查的时候发现有下面警告信息: Thu Apr 02 10:34:39 2015 Current log# 1 seq# 235103 mem# 0: D:\ORADATA\ORCL\REDO01.LOG Thu Apr 02 10:34:40 2015 ARC1: Evaluating archive log 3 thread 1 sequence 235102 Thu Apr 02 10:34:40 2015 ARC1: Warning. Log sequence in arc

【知识点整理】Oracle中NOLOGGING、APPEND、ARCHIVE和PARALLEL下,REDO、UNDO和执行速度的比较

[知识点整理]Oracle中NOLOGGING.APPEND.ARCHIVE和PARALLEL下,REDO.UNDO和执行速度的比较 1  BLOG文档结构图 2  前言部分 2.1  导读和注意事项 各位技术爱好者,看完本文后,你可以掌握如下的技能,也可以学到一些其它你所不知道的知识,~O(∩_∩)O~: ① 系统和会话级别的REDO和UNDO量的查询 ② NOLOGGING.APPEND.ARCHIVE和PARALLEL下,REDO.UNDO和执行速度的比较(重点)   Tips: ① 本文

archive gap

什么是archive gap Archive Gap就是standby端日志应用的过程中丢失的一段范围的redo.典型的发生在standby端不能接收primary的redo信息或者接收后不能应用这些redo. 一旦出现GAP,则standby端的Log Apply Services将会暂停,直到Gap解决后恢复正常. 产生Archive Gap的可能原因: - 网络或者日志传输服务中断 - standby故障 - 日志传输服务配置错误 - standby端I/O异常 - 在archivelog

ORA-16014: log 2 sequence# 14 错误解决

在执行:ALTER SYSTEM SWITCH LOGFILE:时提示修改成功,但是在ASM硬盘组内归档日志空间则没有相应的归档日志文件,则说明日志切换不成功,然后再通过:SQL> ALTER SYSTEM ARCHIVE LOG CURRENT:修改时则提示如下错误: ERROR at line 1: ORA-16014: log 2 sequence# 14 not archived, no available destinations ORA-00312: online log 2 thr