Goldengate table-based replication
This article is based on table replication settings. For the installation and configuration of goldengate, and user-based configuration, please refer to "goldengate deployment implementation case"
1. Configure the main process on the source side
Add main process
GGSCI (ggate1) 2 > edit params mgr
PORT 7809
PURGEOLDEXTRACTS / oracle/ggate/dirdat/mytest_xiuj/ex*, USECHECKPOINTS, MINKEEPDAYS 7
Log in to the database
GGSCI (ggate1) 3 > dblogin userid ggate,password ggate
Successfully logged into database.
GGSCI (ggate1) 4 > start mgr
2. Process is selected for configuration.
GGSCI (ggate1) 13 > add trandata mytest.mytest_xiuj
Logging of supplemental redo data enabled for table MYTEST.MYTEST_XIUJ.
GGSCI (ggate1) 14 > add extract exiuj,tranlog,begin now
EXTRACT added.
GGSCI (ggate1) 15 > add exttrail / oracle/ggate/dirdat/mytest_xiuj/ex,extract exiuj
EXTTRAIL added.
GGSCI (ggate1) 17 > edit params exiuj
Extract exiuj
Userid ggate,password ggate
Exttrail / oracle/ggate/dirdat/mytest_xiuj/ex
Table mytest.mytest_xiuj
3. Configure the transport process
GGSCI (ggate1) 23 > add extract pxiuj,exttrailsource / oracle/ggate/dirdat/mytest_xiuj/ex
EXTRACT added.
GGSCI (ggate1) 24 > add rmttrail / u01qqqx / u01qqt _ dirate_
RMTTRAIL added.
GGSCI (ggate1) 25 > edit params pxiuj
Extract pxiuj
Rmthost 192.168.92.191,mgrport 7809
Passthru
Rmttrail / u01/app/ggate/dirdat/mytest_xiuj/re
Table mytest.mytest_xiuj
4. Configure the replication process
GGSCI (ggate2) 3 > dblogin userid ggate,password ggate
Successfully logged into database.
GGSCI (ggate2) 4 > add checkpointtable chkxiuj
Successfully created checkpoint table CHKxiuj.
GGSCI (ggate2) 5 > add replicat rxiuj,exttrail / u01qqqqt _ date _
REPLICAT added.
GGSCI (ggate2) 6 > edit params rxiuj
Replicat rxiuj
Setenv (NLS_LANG = "SIMPLIFIED CHINESE_CHINA.UTF8")-- Note that there can be no less, because the character set of the destination side is different from that of the source side.
Assumetargetdefs
HANDLECOLLISIONS
Userid ggate,password ggate
Discardfile / u01/app/ggate/dirdat/mytest_xiuj/rep1_discard.txt, append, megabytes 10
Map mytest.mytest_xiuj, target receiver.mytest_xiuj
-- description:
When configuring goldengate, determine whether the character sets on the source side and the destination side are the same
Through:
SQL > select userenv ('language') from dual
USERENV ('LANGUAGE')
SIMPLIFIED CHINESE_CHINA.ZHS16GBK
The source side is "SIMPLIFIED CHINESE_CHINA.UTF8", which makes the destination side the same as the source side, otherwise there will be garbled code on the destination side. Therefore, you must add a value to set the environment in the replication process: setenv (NLS_LANG = "SIMPLIFIED CHINESE_CHINA.UTF8")
Query export character set
Select * from database_properties where property_name = 'NLS_CHARACTERSET'
Related views and tables
Nls_database_parameters props$ v$nls_parameters