Re: Suggestion Required: Best Practise for re-org table which is part of Goldengate Extract

I cannot post to the list directly, but I can send to you. Another method is to find out the user ID of the Golden Gate user- the schema used for GG itself. You can run "alter table shrink" or expdp / impdp as this user, and GG will ignore the rows that were processed by that user. This way you do not even need to stop any GG process or mess with SCN. If you use rdbms_redefinition , make sure the temp table is excluded from GG as well.

-----oracle-l-bounce_at_freelists.org<mailto:-----oracle-l-bounce_at_freelists.org> wrote: -----
To: "oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>" <oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>> From: Sourav Biswas
Sent by: oracle-l-bounce_at_freelists.org<mailto:oracle-l-bounce_at_freelists.org> Date: 09/27/2017 06:20PM
Subject: Suggestion Required: Best Practise for re-org table which is part of Goldengate Extract

Hi All,

Can someone provide some documentation or best practices, for re-org tables which are part of Goldengate replication.

We have a situation, where we need to re-organize few tables using Datapump. And these tables are a sub-set of huge set of tables which are part of Goldengate extract.

An easy way would be to stop the extract , perform the re-org activity and then start the extract after resetting to current csn .

I was wondering , in case someone please suggest a better alternative.

Best Regards,
Sourav Biswas