Example of an external data experiment (2) Verify the synchronization between two nodes in Table BONUS and table SALGRADE

Example of an external data experiment (2) Verify the synchronization between the BONUS table and the SALGRADE table in the previous articles: 1. One-way replication configuration address of GoldenGate configuration (1: click Open link 2, GoldenGate configuration (2), two-way replication configuration address: click open link 3, GoldenGate configuration (3), DDL replication configuration address: Click

Example of an external data experiment (2) Verify the synchronization between the BONUS table and the SALGRADE table in the previous articles: 1. One-way replication configuration address of GoldenGate configuration (1: click Open link 2, GoldenGate configuration (2), two-way replication configuration address: click open link 3, GoldenGate configuration (3), DDL replication configuration address: Click

Example of an external data experiment (2) Verify the synchronization between two nodes in Table BONUS and table SALGRADE

The following articles are continued:

1. One-way replication configuration address for GoldenGate configuration (1): Click the open link

2. Configure GoldenGate (2) bidirectional replication configuration address: Click the open link.

3. DDL replication configuration address of GoldenGate configuration (3): Click to open the link.

4. Configure GoldenGate (4) configure the ingress data address: Click the open link.

5. Example of an external data experiment (1) Verify the synchronization between TCUSTMER and TCUSTORD. Address: Click to open the link.

1. Execute job verification Synchronization

View the result. It is displayed that BONUS and SALGRADE cannot be synchronized at two nodes, for example:

2. Check the report and find the following:

Table has no keys defined.-- Pre-prediction error because the primary key constraint is missing

Comparison terminated with errors.

3. Add a primary key for BONUS and SALGRADE

SQL>Select CONSTRAINT_NAME, INDEX_NAME, TABLE_NAME fromuser_constraints;

-- Check constraints. No primary key information is added for BONUS and SALGRADE.

CONSTRAINT_NAME INDEX_NAME TABLE_NAME

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

FK_DEPTNO EMP

PK_DEPT DEPT

PK_EMP EMP

SYS_C002941 SYS_C002941 TCUSTMER

SYS_C002942 SYS_C002942 TCUSTORD

SQL>Alter table BONUS add constraint PK_ename primarykey (ename); -- add a primary key for BONUS

Table altered.

SQL>Alter table SALGRADE add constraint PK_GRADE primarykey (grade); -- add a primary key for SALGRADE

Table altered.

4. Execute job verification Synchronization

As shown in, the synchronization check is successful:

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

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.