Forum Stats

  • 3,854,989 Users
  • 2,264,447 Discussions


Goldengate with initial load expdp by scn

cptkirksh Member Posts: 89 Red Ribbon

We are running GG MA 19.1 and are migrating from 18c on exadat to 19c on a new exadata. We are using GG to migrate to the new hardware. We have a DB that has a table that gets edited quite a bit. We set up the extract and pulled the SCN from that. Then we did an expdp by scn for an initial load to the new hardware. This is a DB of about 1TB so it took a few hours to fully export and import but it went successfully. After the import ended we started the replicat by using after aftercsn to match our SCN from the initial extract start. Well, the replicat immediately. abended. It was trying to update a record that wasn't in the target. We had to enter the lines in the replicat handlecollisions and insertmissingupdates. Now I read all of the notes to take that out as soon as possible and once the lag caught up we did remove that. Everything seems fine but I am concerned what we did wrong? Shouldn't the fact that we did all of this by SCN it should all line up. Any thoughts would be great. Thanks.


    ORASCN Member Posts: 1,874 Bronze Crown

    Hi ,

    Please share the steps you had followed. Below is the steps recommended,

    1. Create the necessary tables (only structures) on the Target side.

    2. Start the Change Synchronization Capture / Online Extract process.

    3. Start the Datapump Process.

    4. Check the current scn of the database using the below command,

    select current_scn from V$database;

    5. Export the table data from Source with the following parameter in the EXPDP flashback_scn=<CURRENT_SCN_from above query>.

    6. Import the table dump in the Target.

    7. Start the Online Replication process on the Target with the below command,

    start replicat <Replicat_Name>, aftercsn <CURRENT_SCN_noted_before>