Oracle goldengate 11g schema replication from standby database
4 likes1,339 views
GoldenGate can replicate database schemas between an Oracle source and target database. It was configured to replicate the SCOTT schema from a source Oracle 11gR2 database in standby mode to a target Oracle 11gR2 database. The key steps included enabling supplemental logging on the source, setting up the GoldenGate user and processes on both databases, and defining the extract, pump and replicate processes to copy data and DDL changes from the source to the target schema.
Oracle goldengate 11g schema replication from standby database
- 1. Oracle Goldengate 11g Schema replication from Standby Database GoldenGate is touted by Oracle as its future for data replication. It will slowly phase out Oracle Streams and will be more closely coupled with Oracle products. Golden Gate is relatively simpler to use and monitor than Oracle streams. Below I will demonstrate how to configure ASYNC Schema Replication one side using Oracle GoldenGate 11g on Oracle 11gR2 database. SID of SOURCE: TP --> Primary Database SID of SOURCE: TS --> Standby Database SID of target: SOURCE SOURCE Server name: testdb01, testdb02 Target Server name: testdb01 Source Schema name: SCOTT Target Schema name: SCOTT Tables: All tables 1. Tell database to log more (supplemental logging ~10% of more redo writing) on source database only. Enable supplemental log in Primary database, automatic enable in Standby database alter database add supplemental log data; Output same as both Primary and Standby database SQL> SELECT supplemental_log_data_min "Minimum", supplemental_log_data_pk "Primary key", supplemental_log_data_ui "Unique Key", supplemental_log_data_fk "Foregin Key", supplemental_log_data_all "All" FROM v$database; 2 3 4 5 6 Minimum Pri Uni For All -------- --- --- --- --- YES NO NO NO NO 2. Set the Environment variables in .bash_profile of user gguser on both source and target database servers.
- 2. — source — TMP=/tmp; export TMP TMPDIR=$TMP; export TMPDIR ORACLE_BASE=/opt/oracle/app/oracle; export ORACLE_BASE ORACLE_HOME=$ORACLE_BASE/product/11.2.0/db_1; export ORACLE_HOME ORACLE_SID=TP; export ORACLE_SID PATH=$ORACLE_HOME/bin:/usr/sbin:/usr/local/bin:$PATH export PATH export OGG_HOME=/export/home/oracle/OGG export PATH=${OGG_HOME}:${OGG_HOME}/tools:$PATH export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/export/home/oracle/OGG alias g="${OGG_HOME}/ggsci" — Detination — TMP=/tmp; export TMP TMPDIR=$TMP; export TMPDIR ORACLE_BASE=/opt/oracle/app/oracle; export ORACLE_BASE ORACLE_HOME=$ORACLE_BASE/product/11.2.0/db_1; export ORACLE_HOME ORACLE_SID=TS; export ORACLE_SID PATH=$ORACLE_HOME/bin:/usr/sbin:/usr/local/bin:$PATH export PATH export OGG_HOME=/export/home/oracle/OGG export PATH=${OGG_HOME}:${OGG_HOME}/tools:$PATH export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/export/home/oracle/OGG alias g="${OGG_HOME}/ggsci" 3. Create the tablespace for both databases (source + target ) like: Create in Primary database which auto replicate in Standby database, in target data also create tablespace as like ggate user Create tablespace ggate datafile ‘/opt/oracle/app/oracle/oradata/TP/ggate01.dbf’ size 1000M autoextend on next 100M; 4. GoldenGate schema creation into source and target database create user ggate identified by ggate default tablespace ggate temporary tablespace TEMP profile DEFAULT; alter user ggate QUOTA UNLIMITED ON ggate; grant CONNECT to ggate; grant CREATE SESSION to ggate;
- 3. grant RESOURCE to ggate; grant SELECT ANY TABLE to ggate; grant ALTER SESSION to ggate; grant CREATE TABLE to ggate; grant FLASHBACK ANY TABLE to ggate; grant SELECT ANY DICTIONARY to ggate; grant DBA to ggate; 5. Enable DDL in both Source and target database login as sysdba on both source and target run following steps… SQL> grant execute on utl_file to ggate; SQL> @marker_setup.sql SQL> @ddl_setup.sql SQL> @role_setup.sql SQL> grant GGS_GGSUSER_ROLE to ggate; And more important grant on dictionay views otherwise extract will keep on abending on both source and target schema (in our case IVR and IVR on both source and target. Schema name is same on both databases) — on source — SQL> grant select any dictionary to SCOTT; — on target — SQL> grant select any dictionary to SCOTT; 6. Manager Configuration in Source Side — Source Configuration that is testbed02 from TS (Standby database) —
- 4. GGSCI (testdb02) 1> status all GGSCI (testdb02) 1> edit params mgr PORT 5000 lagreportminutes 5 laginfominutes 1 lagcriticalminutes 2 purgeoldextracts ./dirdat/t*, minkeepdays 2, usecheckpoints GGSCI (testdb02) 1> start mgr GGSCI (testdb02) 1> info all If manager is running then manager configuration is ok. 7. Trans data enable in table level GGSCI (testdb02) 1> dblogin userid ggate, password ggate GGSCI (testdb02 as ggate@TS) 20> list tables scott.* SCOTT.BONUS SCOTT.DEPT SCOTT.EMP SCOTT.SALGRADE Found 4 tables matching list criteria. If you see the list of tables then your configuration is good and you can continue: GGSCI (testdb02 as ggate@TS) 22> info trandata scott.* Logging of supplemental redo log data is disabled for table SCOTT.BONUS. Logging of supplemental redo log data is disabled for table SCOTT.DEPT. Logging of supplemental redo log data is disabled for table SCOTT.EMP.
- 5. Logging of supplemental redo log data is disabled for table SCOTT.SALGRADE. Enable table level supplemental log from Primary Database alter table SCOTT.BONUS add supplemental log data (ALL) columns; alter table SCOTT.DEPT add supplemental log data (ALL) columns; alter table SCOTT.EMP add supplemental log data (ALL) columns; alter table SCOTT.SALGRADE add supplemental log data (ALL) columns; Now check in Source Standby Database GGSCI (testdb02 as ggate@TS) 23> info trandata scott.* Logging of supplemental redo log data is enabled for table SCOTT.BONUS. Columns supplementally logged for table SCOTT.BONUS: ALL. Logging of supplemental redo log data is enabled for table SCOTT.DEPT. Columns supplementally logged for table SCOTT.DEPT: ALL. Logging of supplemental redo log data is enabled for table SCOTT.EMP. Columns supplementally logged for table SCOTT.EMP: ALL. Logging of supplemental redo log data is enabled for table SCOTT.SALGRADE. Columns supplementally logged for table SCOTT.SALGRADE: ALL. 8. Extract Process ADD in Source Side connection in Standby Database Let’s create and configure now the extractor process, edit add these files and save: GGSCI (testdb02 as ggate@TS) 24> add extract extst1, tranlog, begin now EXTRACT added. GGSCI (testdb02 as ggate@TS) 25> add exttrail ./dirdat/k1, extract extst1, megabytes 100 EXTTRAIL added.
- 6. GGSCI (testdb01 as ggate@SOURCE) 11> edit params EXTST1 extract extst1 SETENV (ORACLE_SID = "TS") userid ggate@TS, password ggate discardfile ./dirrpt/exts1.dsc,purge reportcount every 15 minutes, rate exttrail ./dirdat/k1 TRANLOGOPTIONS MINEFROMACTIVEDG CACHEMGR CACHESIZE 1GB table SCOTT.*; 9. After starting the extract process get error Extract on ADG: OGG-00868 The number of Oracle redo threads (2) is not the same as the number of checkpoint threads (1). (Doc ID 2004661.1) SQL> select group#, THREAD#, SEQUENCE#,STATUS from v$standby_log; GROUP# THREAD# SEQUENCE# STATUS ---------- ---------- ---------- ---------- 5 1 52 ACTIVE 6 1 0 UNASSIGNED 7 0 0 UNASSIGNED 8 0 0 UNASSIGNED SQL> alter database recover managed standby database cancel; Database altered. SQL> alter database drop standby logfile group 7;
- 7. Database altered. SQL> alter database drop standby logfile group 8; Database altered. SQL> alter database recover managed standby database using current logfile disconnect; Database altered. 10. PUMP Process ADD in Source Side connection in Standby Database Extract process created, now we create the data pump process: GGSCI (testdb02) 8> add extract dpest1, exttrailsource ./dirdat/k1 EXTRACT added. GGSCI (testdb02) 9> add rmttrail ./dirdat/k1, extract dpest1, megabytes 100 RMTTRAIL added.GGSCI (testdb01 as ggate@SOURCE) 1> edit param dpest1 extract dpest1 passthru rmthost testdb01, mgrport 8000 rmttrail ./dirdat/k1 table SCOTT.*; //rmthost is the target server name or ip address. Ensure port 8000 is open on target server 11. Replicate Process ADD in Target Database — Destination Configuration — Target side on your ggsci prompt: GGSCI (testdb01) 2> dblogin userid ggate@SOURCE , password ggate Successfully logged into database. GGSCI (testdb01 as ggate@SOURCE) 3> ADD CHECKPOINTTABLE GGATE.CHKPTAB
- 8. GGSCI (testdb01 as ggate@SOURCE) 4> add replicat repst1, exttrail ./dirdat/k1 CHECKPOINTTABLE GGATE.CHKPTAB REPLICAT added. Manager created and verified, now we are going to create replicate processes. GGSCI (testdb01 as ggate@SOURCE) 11> view param REPST1 replicat repst1 SETENV (ORACLE_SID = "SOURCE") userid ggate@SOURCE, password ggate discardfile ./dirrpt/rep1.dsc, purge assumetargetdefs reportcount every 15 minutes, rate batchsql deferapplyinterval 5 mins map SCOTT.*, target SCOTT.*; 12. Check the stats OGG is working Fine Source Standby Database Target Database