Example of an external data experiment (4) Verify that external data finds the updata and delete operations

Example of the external data experiment (4) Verify that external data finds out the non-synchronization caused by the updata and delete operations) verify that data is not synchronized due to the insert operation. Address: Click to open the link environment: ItemSourceSystemTargetSystemPlatformRedHatEnterpriseL

Example of the external data experiment (4) Verify that external data finds out the non-synchronization caused by the updata and delete operations) verify that data is not synchronized due to the insert operation. Address: Click to open the link environment: Item Source System Target System Platform Red Hat Enterprise L

Example of an external data experiment (4) Verify that external data finds out the non-synchronization caused by updata and delete operations.

Extension: Example of the external data experiment (3) Verify that external data finds out the non-synchronization caused by the insert operation. Address: Click to open the link.

Environment:

Item	Source System	Target System
Platform	Red Hat Enterprise Linux Server release 5.4	Red Hat Enterprise Linux Server release 5.4
Hostname	Gc1	Gc2
Database	Oracle 10.2.0.1	Oracle 11.2.0.1
Character Set	ZHS16GBK	ZHS16GBK
ORACLE_SID	PROD	EMREP
Listener Name/Port	LISTENER/1521	LISTENER/1521
Goldengate User	Ogg	Ogg

1. Continue to the experiment 3 environment, close the synchronization process, and perform updata and delete operations on gc1.

SQL>Select * from TCUSTMER;

CUST NAME CITY ST

--------------------------------------------------------

HYL HUANGDBA BEIJING CN

ZX XING SHIJIAZ CN

Will bg software co. SEATTLE WA

Jane rocky flyer inc. DENVER CO

ZC ZHANCHI DBA BEIJING CN

SQL>Delete from tcustmer where CUST_CODE = 'zx ';

1 row deleted.

SQL>Update tcustmer set city = 'zhengzhou', state = 'cn' where cust_code = 'zc ';

1 row updated.

SQL>Commit;

Commit complete.

SQL>Select * from TCUSTMER;

CUST NAME CITY ST

--------------------------------------------------------

HYL HUANGDBA BEIJING CN

Will bg software co. SEATTLE WA

Jane rocky flyer inc. DENVER CO

ZC ZHANCHI DBA ZHENGZHOU CN

2. Use external data to verify gc1 and gc2 Synchronization

3. view the report generated by external data

Click "View" to View details, as shown in:

-- The details show that the data in the experiment table on two nodes is not synchronized due to the update and delete operations on gc1.

4. synchronous processing

GGSCI (gc2) 10>Info all

Program Status Group Lag Time Since Chkpt

MANAGER RUNNING

Extract running EORA_1 00:00:00 00:00:02

Extract running PORA_1 00:00:00 00:00:00

Replicat stopped RORA_1 00:00:00 00:10:55

GGSCI (gc2) 11>Start RORA_1

Sending START request to MANAGER...

REPLICAT RORA_1 starting

GGSCI (gc2) 12>Info all

Program Status Group Lag Time Since Chkpt

MANAGER RUNNING

Extract running EORA_1 00:00:00 00:00:01

Extract running PORA_1 00:00:00 00:00:00

Replicat running RORA_1 00:10:34 00:00:02

Gc2:

SQL>Select * from TCUSTMER;

CUST NAME CITY ST

--------------------------------------------------------

HYL HUANGDBA BEIJING CN

ZC ZHANCHI DBA ZHENGZHOU CN

Will bg software co. SEATTLE WA

Jane rocky flyer inc. DENVER CO

Gc1:

SQL>Select * from TCUSTMER;

CUST NAME CITY ST

--------------------------------------------------------

HYL HUANGDBA BEIJING CN

Will bg software co. SEATTLE WA

Jane rocky flyer inc. DENVER CO

ZC ZHANCHI DBA ZHENGZHOU CN

-- Complete synchronization

Verify with external data again and the data has been synchronized.

****************** ********

Statement:
Original works, from "Deep Blue blog" blog, allow reprint, reprint please be sure to indicate the source (http://blog.csdn.net/huangyanlong ).

The author has the right to pursue legal liability for copyright issues.