All posts, Golden Gate, Oracle, SQL by Team Ajara

Difference between Oracle and SQL server in GG setup

Difference between Oracle and SQL server in GoldenGate setup.

GG Setup on Oracle

S/No	Task/Feature	Oracle	Comments
1	Connectivity	GGSCI> dblogin userid gger password userpw
2	Determine if change data capture has been enabled	SQL> select owner, log_group_name, table_name from dba_log_groups where owner = ‘HR’;
3	To Disable triggers	use paramaeter SUPPRESSTRIGGERS– in replicat (available for versions > 10.2.0.5)	From GG version 11, a new SUPPRESSTRIGGERS option is available as part of the Replicat DBOPTIONS parameter, to automatically suppress the triggers from firing on the target.
4	SETENV	SETENV(ORACLE_HOME= /u01/app/oracle/product/12.1.2) SETENV(ORACLE_SID=ORCLWEST)	Using SETENV parameter we can set the environment
5	EXTTRAIL	EXTTRAIL ‘<filename>’

GG Setup on MS SQL

S/No	Task/Feature	SQL Server	Comments
1	Connectivity	dblogin sourcedb sqlserver, userid sa, password userpw	SOURCEDB specifies the SQL Server ODBC data source, and USERID specifies the database user ID. If you’re using Windows authentication, you can leave off the USERID and PASSWORD options.
2	Determine if change datacapture has been enabled	select * from cdc.change_tables
3	To Disable triggers	use paramaeter SUPPRESSTRIGGERS– in replicat (available for versions > 10.2.0.5)	From GG version 11, a new SUPPRESSTRIGGERS option is available as part of the Replicat DBOPTIONS parameter, to automatically suppress the triggers from firing on the target.
4	SETENV	SETENV (GGS_CacheRetryCount = 25) SETENV (GGS_CacheRetryDelay = 2000)	For SQL Server, you can use SETENV to specify the number of times GoldenGate will try to read the transaction log before abending the time to delay between retries:
5	EXTTRAIL	EXTTRAIL ‘<Filename>’ TRANLOGOPTIONS MANAGESECONDARYTRUNCATIONPOINT	For SQL Server, you should specify an additional parameter, as shown in the following example, to tell GoldenGate how to manage the secondary truncation points: You can specify MANAGESECONDARYTRUNCATIONPOINT If you want GoldenGate to maintain a secondary truncation point. You would specify this parameter if SQL Server replication wasn’t running. If SQL Server replication was running concurrently with GoldenGate, then you would specify NOMANAGESECONDARYTRUNCATIONPOINT to allow SQL Server to manage the secondary truncation point.