Oracle10g Logical DataGuard 详细搭建过程

最新推荐文章于 2021-04-02 19:45:47 发布
最新推荐文章于 2021-04-02 19:45:47 发布
阅读量1.8k 收藏 1
点赞数
分类专栏： Oracle Dataguard Oracle 文章标签： Oracle Oracle Dataguard
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/staricqxyz/article/details/20367343
版权

logical standby是在physical standby基础上搭建

Oracle10g Physical DataGuard 详细搭建过程


--停止standby上的日志应用

SQL> alter database recover managed standby database  cancel;


Database altered.



--修改主库log_archive_dest_3参数,当切换为备库时在线日志归档路径

SQL> alter system set log_archive_dest_3='LOCATION=/u01/app/oracle/oradata/dbserver/arch valid_for=(standby_logfiles,standby_role) db_unique_name=dbserver';


System altered.


SQL> alter system set log_archive_dest_state_3=enable;


System altered.


--主库执行,alert.log显示Logminer Bld: Done

SQL> execute dbms_logstdby.build;


PL/SQL procedure successfully completed.



--修改备库log_archive_dest_3参数,备库在线日志归档路径

SQL> alter system set log_archive_dest_3='LOCATION=/u01/app/oracle/oradata/standby/arch valid_for=(standby_logfiles,standby_role) db_unique_name=standby';


System altered.


SQL> alter system set log_archive_dest_state_3=enable;


System altered.


--如果备库没有临时表空间需要创建

--在standby端将物理备库转为逻辑备库,最后一个standby是逻辑备库名称

SQL> select status from v$instance;


STATUS
------------
MOUNTED


SQL> select database_role from v$database;


DATABASE_ROLE
----------------
PHYSICAL STANDBY


SQL> startup mount force
ORACLE instance started.


Total System Global Area  612368384 bytes
Fixed Size                  2085872 bytes
Variable Size             167775248 bytes
Database Buffers          436207616 bytes
Redo Buffers                6299648 bytes
Database mounted.
SQL> alter database recover to logical standby standby;


Database altered.


SQL> select status from v$instance;


STATUS
------------
STARTED


SQL> startup mount force
ORACLE instance started.


Total System Global Area  612368384 bytes
Fixed Size                  2085872 bytes
Variable Size             167775248 bytes
Database Buffers          436207616 bytes
Redo Buffers                6299648 bytes
Database mounted.
SQL> select database_role from v$database;


DATABASE_ROLE
----------------
LOGICAL STANDBY


SQL> alter database open resetlogs;


Database altered.


SQL> select name from v$database;


NAME
---------
STANDBY



--在主库switch logfile

SQL> alter system switch logfile;


System altered.


SQL> /


System altered.


SQL> /


System altered.


SQL> /


System altered.


SQL> /


System altered.


SQL> /


System altered.



--standby alert.log

RFS[3]: Assigned to RFS process 10806
RFS[3]: Identified database type as 'logical standby'
Mon Mar  3 13:10:28 2014
RFS LogMiner: Client enabled and ready for notification
RFS[3]: Successfully opened standby log 6: '/u01/app/oracle/oradata/standby/standby03.log'
Mon Mar  3 13:10:28 2014
RFS LogMiner: Client enabled and ready for notification
Mon Mar  3 13:11:21 2014
RFS LogMiner: Client enabled and ready for notification
Mon Mar  3 13:11:22 2014
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 5: '/u01/app/oracle/oradata/standby/standby02.log'
Mon Mar  3 13:11:33 2014
RFS LogMiner: Client enabled and ready for notification
Mon Mar  3 13:11:34 2014
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 5: '/u01/app/oracle/oradata/standby/standby02.log'


--在备库启用实时应用

SQL> alter database start logical standby apply immediate;


Database altered.



--接下来就是测试了，在主库插入数据在备库查看是否同步，以下是备库的alert.log

RFS LogMiner: Registered logfile [/u01/app/oracle/oradata/standby/arch/ARC0000000136_0839199018.0001] to LogMiner session id [1]
LOGMINER: session# = 1, reader process P000 started with pid=40 OS id=10844
LOGMINER: session# = 1, builder process P001 started with pid=41 OS id=10846
LOGMINER: session# = 1, preparer process P002 started with pid=42 OS id=10848
Mon Mar  3 13:17:08 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 136, /u01/app/oracle/oradata/standby/arch/ARC0000000136_0839199018.0001
Mon Mar  3 13:17:08 2014
LOGMINER: Turning ON Log Auto Delete
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000136_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 137, /u01/app/oracle/oradata/standby/arch/ARC0000000137_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000137_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 138, /u01/app/oracle/oradata/standby/arch/ARC0000000138_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000138_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 139, /u01/app/oracle/oradata/standby/arch/ARC0000000139_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000139_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 140, /u01/app/oracle/oradata/standby/arch/ARC0000000140_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000140_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 141, /u01/app/oracle/oradata/standby/arch/ARC0000000141_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000141_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 142, /u01/app/oracle/oradata/standby/arch/ARC0000000142_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000142_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 143, /u01/app/oracle/oradata/standby/arch/ARC0000000143_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000143_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 144, /u01/app/oracle/oradata/standby/arch/ARC0000000144_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000144_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 145, /u01/app/oracle/oradata/standby/arch/ARC0000000145_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000145_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 146, /u01/app/oracle/oradata/standby/arch/ARC0000000146_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000146_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 147, /u01/app/oracle/oradata/standby/arch/ARC0000000147_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000147_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 148, /u01/app/oracle/oradata/standby/arch/ARC0000000148_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000148_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 149, /u01/app/oracle/oradata/standby/arch/ARC0000000149_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000149_0839199018.0001
LNS1 started with pid=43, OS id=10850
Mon Mar  3 13:17:17 2014
Thread 1 advanced to log sequence 2 (LGWR switch)
  Current log# 2 seq# 2 mem# 0: /u01/app/oracle/oradata/standby/redo02.log
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ATTRCOL$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_CCOL$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_CDEF$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_COL$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_COLTYPE$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ICOL$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_IND$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDCOMPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDSUBPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOB$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOBFRAG$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_OBJ$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TAB$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABCOMPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABSUBPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TS$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TYPE$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_USER$ have been marked unusable
Indexes of table  SYSTEM.LOGMNR_ATTRCOL$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_ATTRIBUTE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_CCOL$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_CDEF$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_COL$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_COLTYPE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_DICTIONARY$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_ICOL$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_IND$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_INDCOMPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_INDPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_INDSUBPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_LOB$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_LOBFRAG$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_OBJ$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TAB$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TABCOMPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TABPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TABSUBPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TS$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TYPE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_USER$ have been rebuilt and are now usable
LSP2 started with pid=44, OS id=10853
Mon Mar  3 13:17:26 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 136, /u01/app/oracle/oradata/standby/arch/ARC0000000136_0839199018.0001
Mon Mar  3 13:17:26 2014
LOGMINER: Turning ON Log Auto Delete
LOGSTDBY Analyzer process P003 started with pid=45 OS id=10855
LOGSTDBY Apply process P006 started with pid=48 OS id=10861
LOGSTDBY Apply process P008 started with pid=50 OS id=10865
LOGSTDBY Apply process P007 started with pid=49 OS id=10863
LOGSTDBY Apply process P004 started with pid=46 OS id=10857
LOGSTDBY Apply process P005 started with pid=47 OS id=10859
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000136_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 137, /u01/app/oracle/oradata/standby/arch/ARC0000000137_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000137_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 138, /u01/app/oracle/oradata/standby/arch/ARC0000000138_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000138_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 139, /u01/app/oracle/oradata/standby/arch/ARC0000000139_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000139_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 140, /u01/app/oracle/oradata/standby/arch/ARC0000000140_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000140_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 141, /u01/app/oracle/oradata/standby/arch/ARC0000000141_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000141_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 142, /u01/app/oracle/oradata/standby/arch/ARC0000000142_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000142_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 143, /u01/app/oracle/oradata/standby/arch/ARC0000000143_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000143_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 144, /u01/app/oracle/oradata/standby/arch/ARC0000000144_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000144_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 145, /u01/app/oracle/oradata/standby/arch/ARC0000000145_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000145_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 146, /u01/app/oracle/oradata/standby/arch/ARC0000000146_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000146_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 147, /u01/app/oracle/oradata/standby/arch/ARC0000000147_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000147_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 148, /u01/app/oracle/oradata/standby/arch/ARC0000000148_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000148_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 149, /u01/app/oracle/oradata/standby/arch/ARC0000000149_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000149_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 150, /u01/app/oracle/oradata/standby/standby03.log
Mon Mar  3 13:18:05 2014
RFS LogMiner: RFS id [10797] assigned as thread [1] PING handler

ZhongWeicheng
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
Oracle Data Guard最佳实践
12-02
来自Oracle官方的关于Oracle的Data Guard的六项最佳实践，有助于学习Data Guard的部署、迁移、实施等技能
oracle logical standby,Oracle Dataguard管理命令（logical standby）
weixin_33477290的博客
04-06 209
Oracle Dataguard管理命令(logical standby)################### 管理命令：#################1、注册日志的命令standbySQL> ALTER DATABASE REGISTER LOGICAL LOGFILE‘/usr2/u01/app/oracle/oracle9201/oradata/scpdb/standby_ar...
ORACLE 10G DATAGUARD实战步骤【转】
gowissen的专栏
11-27 539
具体步骤如下： 一、主库操作 1、修改主库属性： alter system force logging; ##查看状态 select FORCE_LOGGING from v$database; 2、修改数据库为归档模式： archive log list; shutdown immediate; startup mount; alter database archivelog;(alter da
Dataguard实战(8)：RHEL4.5 安装 Oracle10G Dataguard 多个备库 - 更改物理备库为最大可用或最大保护模式
爱肯的专栏
03-24 710
八、更改物理备库为最大可用或最大保护模式前面建立的备库默认是最大性能模式，一般都设置成最大可用性模式，如果备库发生问题，主库会自动降级为最大性能模式，对主库不会有影响。8.1 备库配置standby redolog（vmtwo）SQL> recover managed standby database cancel;SQL> alter database add standby log
ORACLE10G DATAGUARD配置笔记
weixin_34245082的博客
09-25 97
ORACLE10G DATAGUARD配置笔记环境：OS:RHL4+ORACLE10G10.2.0.1IP:172.17.61.160(primary) 172.17.61.161(standby)ORACLE_SID:orclORACLE_HOME:/oracle/product/10.2.0 一、配置standby database为MAXIMIZE PERFORMAN...
运用logical standby技术实现Oracle数据库的读写分离
最新发布
09-09
在MySQL作为应用系统的后台数据库时，我们常常见到这样的架构，一拖二、一拖三等等。这是用MySQL的读写分离技术，实现...我们这里介绍最后一个方法，利用dataguard技术中的logical standby实现Oracle数据库的读写分离。
Oracle存储过程、包、方法使用总结(推荐)
09-09
主要介绍了Oracle存储过程、包、方法使用总结(推荐),需要的朋友可以参考下
2010年10月最新ORACLE OCP培训教程
12-01
Oracle Database 10g: “g” Stands for Grid 1-6 Oracle Database Architecture 1-8 Database Structures 1-9 Oracle Memory Structures 1-10 Process Structures 1-12 Oracle Instance Management 1-13 Server ...
Oracle 11g For Dummies.pdf
09-23
The building blocks behind the database engine as well as Oracle’s physical and logical structures Hardware, software, system, and storage requirements for implementation How to recognize and ...
10. Logical Layers for SDN
03-25
INE出品的SDN视频教程
Oracle DataGuard备份恢复最佳实践
09-27
提到DataGuard环境下的备份恢复，大家都知道可以在备库上备份，然后恢复到主库，但您知道在生产中实施会遇到多少坑吗？实际生产中我们看到了太多在主库上进行备份，而让备库闲着的现象。本次课程将带您深入了解DataGuard环境下的备份恢复。 讲师介绍：姚远，专注于 Oracle、MySQL 数据库多年，拥有Oracle 10g、12c OCM, MySQL 5.6、5.7、8.0 OCP，并在：EMC、IBM p、RedHat、Cisco、SQL Server、DB2等领域拥有20+技术认证。两次获得国家部级科技进步奖，拥有两项计算机发明专利。现为鼎甲科技高级技术顾问。
Oracle10g logical standby 建立
cuixie2370的博客
10-28 95
1. Check whether production database is in auto archived mode (select * from v$database ; )2. Force loggin...
oracle dataguard详细,详细讲解Oracle11g dataguard（LOGICAL STANDBY）配置过程案例
weixin_34599958的博客
04-02 207
天萃荷净Oracle 11g data guard(LOGICAL STANDBY)配置1、Create a Physical Standby Database11g dataguard(PHYSICAL STANDBY)配置http://oracleplus.net/arch/aljjOracle_11g_dataguard_PHYSICAL_STANDBY_pz_25.html2、Stop R...
ORACLE 10G DATAGUARD实战步骤
05-26 65
ORACLE 10G DATAGUARD实战步骤http://bbs.chinaunix.net/forum.php?mod=viewthread&tid=998901&fromuid=17252115 ...
oracle实验记录 (oracle 10G dataguard(11)建立logical standby)
cuiye1492的博客
11-16 105
逻辑standby 逻辑standby支持数据类型BINARY_DOUBLE、BINARY_FLOAT、BLOB、CHAR、CLOB and NCLOB、DATE、INTERVAL YEAR TOMONTH、INTERVAL ...
[oracle]oracle10g dataguard实战步骤
阿甘修行的专栏
02-03 223
oracle10g dataguard安装步骤 一、主库操作 1、修改主库属性： alter system force logging; 查看状态 select FORCE_LOGGING from v$database; 2、修改数据库为归档模式： archive log list; shutdown immediate; startup mount; alter database ar...
Oracle 10g R2 实现dataguard实时日志应用(real-time apply)
cmhaqkcrx827119593的博客
03-26 179
先简单描述一下data guard的流程: 通常是这样的: primary database通过arch 进程，或者lgwr进程把archive log 送到standby database的archive_dest，然后...
oracle实验记录 (oracle 10G dataguard(2)参数部分)
cuiye1492的博客
11-16 98
参数部分：详细讲解dg需要的参数 db_file_name_convert,log_file_name_convert 主要是映射文件路径， 比如主库ADD 一个文件，standby 应用日志时那么该文件会映射转换到stan...
Oracle10g Physical DataGuard 详细搭建过程
Zhong Weicheng Study Notes
02-14 6046
primary 环境 DB version:oracle10.2.0.4 IP:192.168.1.7 hostname:vzwc db_name:dbserver db_unique_name:dbserver service_name:dbserver instance_name:ORCL standby 环境 DB version:oracle10.2.0.4 IP:
oracle 19c DG搭建教程
03-28
以下是Oracle 19c DG（Data Guard）搭建教程的简要步骤： 1. 准备工作 a. 安装Oracle 19c数据库软件，并创建主库和备库的数据库实例。 b. 确保主库和备库之间的网络连接正常。 c. 在主库和备库中创建一个共享...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值