How GoldenGate process consumes memory

Question: We are using Golden Gate to replicate the data from Oracle 9.2.0.8 on Solaris8 SPARC 64 bit (GoldenGate Version 10.4.0.31 Build 001) to Oracle RAC 11.2.0.1 on Solaris10 SPARC 64bit (GoldenGate Version 10.4.0.19 Build 002). Both GoldenGate Extract and Replicat process are working fine. Please refer below information for more easy to understand our . . . → Read More: How GoldenGate process consumes memory

Will Goldengate use Remote Procedure Call (RPC)?

Question: My Customer using Oracle GoldenGate to sync data from 11.2.0.1 RAC (on Solaris 10 SPRAc 64bit) to 9.2.0.8 standalone DB (On solaris Sparc 64bit). My customer recently doing an OS security scan check for node of 11.2.0.1 RAC. The security scan check result saying the RAC node (HK8SP226) has a potential security issue on . . . → Read More: Will Goldengate use Remote Procedure Call (RPC)?

配置GoldenGate意外处理及记录Oracle错误信息(1)

GoldenGate自身不提供异常处理的程序。在默认情况下,若Replicat进程遭遇操作故障都会导致其异常终止(ABEND),同时将会回滚事务到最近的检查点。在生产环境中这往往并不理想。当我们在做无缝的数据迁移时会用到HANDLECOLLISIONS和NOHANDLECOLLISIONS参数,这2个参数控制了Replicat是否会试图解决重复记录和缺失记录的错误,但这错误真的应该被忽略吗?这个问题只有熟悉应用的维护人员才能解答,我们需要做的是在出现这类错误后及时记录错误的相关信息。

这就要求我们在Replicat中配置相关的意外处理程序,该程序用以记录是哪个Replicat进程,是那些数据引起了错误的产生。

接下来我们会尝试建立不同的意外处理程序,用以捕获复制过程中Oracle出现的相关错误,但在这些故障发生后我们允许Replicat继续它的工作:

1. 首先我们要做的是创建用以记录错误相关信息的错误记录表: SQL> conn maclean/maclean Connected. SQL> create table exception_log 2 ( replicat_name varchar2(10), 3 table_name varchar2(100), 4 errno number, 5 dberrmsg varchar2(4000), 6 optype varchar2(20), 7 errtype varchar2(20), 8 logrba number, 9 logposition number, 10 committimestamp timestamp); Table created. SQL> alter table exception_log add primary key (logrba,logposition,committimestamp); Table altered. 以上意外处理记录表应建立于Goldengate管理员账户名下,可用以记录所有Replicat的意外数据。 2.修改各Replicat的参数文件添加相关的意外处理程序: . . . → Read More: 配置GoldenGate意外处理及记录Oracle错误信息(1)

How to handle ddl in GoldenGate environment without ddl replication?

Question:gg only config to replicate dml, when source has some ddl changes, how to handle in source and target?

Answer: GoldenGate capture the dml changes only by default,if you have made any changes in DDL structure,then stop the extract and replicat process and make changes in DDL structure and restart the extract and replicat process,then . . . → Read More: How to handle ddl in GoldenGate environment without ddl replication?

GoldenGate Build for Oracle 8i

BUILD REQUEST INSTALLATION MEDIA BUILD REQUEST ORACLE GOLDENGATE BUILD FOR 8I -32BIT ON WINDOWS (XP, 2003) 1040_WINNT.zip BUILD REQUEST SUN SOLARIS 5.8 SPARC (64-BIT) , ORACLE 8I GG VERSION 10.0.0.52_00 ggs_solaris8_sparc_ora81_32bit_v10_0_0_52_001.tar GGS V10.4.0.31.001 BUILD FOR HPUX 11.11 PA-RISC 64BIT / ORACLE 8.1 ggs_hpux1111_pa_ora81_32bit_v10_4_0_31_001.tar . . . → Read More: GoldenGate Build for Oracle 8i

GoldenGate实现Live Standby主备库切换(2)

在《GoldenGate实现Live Standby主备库切换(1)》中我们介绍了如何针对GoldenGate Live standby环境执行计划内的Switchover切换。除去计划内的主备切换,实际生产中更多的故障切换发生在主机故障或主库不可用的情况下,这种情况下一般我们已经无法在Primary上停止应用及extract了;当我们在这样的情况下failover到Standby上后如同在DataGuard环境下一样即便Primary上的数据库恢复了我们也无法直接进行回切了,需要做的是重新配置Primary上的OGG并将Standby上的数据以initial load的形式还原回去,在数据重新同步后才能再切换到Primary上。下面我们就来介绍如何在计划外的情况下从主库failover到备库,并尝试回切:

1. 使用lag replicat命令了解standby上的replicat的延迟情况,若返回”At EOF (end of file)”则说明replicat已应用所有trail中的数据到备库上。 GGSCI (rh3.oracle.com) 1> info all Program Status Group Lag Time Since Chkpt MANAGER RUNNING EXTRACT STOPPED EXTSTD2 00:00:00 23:42:47 EXTRACT STOPPED PUMPSTD2 00:00:00 23:41:29 REPLICAT RUNNING REPSTD1 00:00:00 00:00:00 GGSCI (rh3.oracle.com) 5> lag replicat repstd1 Sending GETLAG request to REPLICAT REPSTD1 … Last . . . → Read More: GoldenGate实现Live Standby主备库切换(2)

How to understand goldengate report file statistics

- Are total process records = inserts + updates + deletes +discards + ignores? Generally total process records = inserts + updates + deletes +discards + ignores – Are update collisions is part of updates ? Yes – Are delete collisions is part of deletes? Yes – Are total successfully process records = inserts + . . . → Read More: How to understand goldengate report file statistics

GoldenGate实现Live Standby主备库切换(1)

Oracle Goldengate目前支持主被动式的双向配置,换而言之OGG可以将来自于激活的主库的数据变化完全复制到从库中,从库在不断同步数据的同时已经为计划内的和计划外的outages做好了故障切换的准备,也就是我们说的Live Standby。这里我们重点介绍一下配置Oracle Goldengate Live Standby系统的步骤,和具体的故障切换过程。

SQL> conn clinic/clinic Connected. SQL> drop table tv; create table tv (t1 int primary key,t2 int,t3 varchar2(30)); Table dropped. SQL> Table created. SQL> drop sequence seqt1; create sequence seqt1 start with 1 increment by 1; Sequence dropped. SQL> SQL> Sequence created. declare rnd number(9,2); begin for i in 1..100000 . . . → Read More: GoldenGate实现Live Standby主备库切换(1)