Use the following instructions to remove database objects and stopping processes for your configuration. Some steps and commands may not apply to your configuration, however other instructions are applicable to all databases (until specified).

For SQL Server, use these steps to remove supplemental logging and any Oracle GoldenGate CDC Cleanup objects from the source database in the Oracle GoldenGate capture configuration, and to remove the Replicat checkpoint table in the apply configuration. 

On a Source System:

1. Log on as the system administrator or as a user with permission to issue Oracle GoldenGate commands and delete files and directories from the operating system.

2. Run ggsci from the Oracle GoldenGate directory.

3. Stop all Oracle GoldenGate processes if not already done.

   STOP EXTRACT *

4. Stop the Manager process.

   STOP MANAGER

5. Issue the following command to log into the source database, see SOURCEDB.

   DBLOGIN SOURCEDB {data_source | database@host:port} USERIDALIAS alias

6. Remove any heartbeat table entries by running the DELETE HEARTBEATTABLE command.

7. For a SQL Server Extract configuration, remove the Oracle GoldenGate CDC cleanup job and objects if they were created.

   1. Open a command prompt and change to the Oracle GoldenGate installation folder.

   2. Run the ogg_cdc_cleanup_setup.sh/bat file as follows:

      ogg_cdc_cleanup_setup.sh/bat dropJob userid password database_name servername\instancename schema

      The userid password must be a valid SQL Server login and password for a sysadmin user. database_name servername\instancename are the source database name and instance name. If only server name is listed, then the default instance will be used to connect to the database server. schema is the schema name listed in the GLOBALS file, with the GGSCHEMA parameter.

      For example:

      ogg_cdc_cleanup_setup.bat dropJob ggsuser ggspword db1 server1\inst1 ogg

8. Remove supplemental logging from tables that were enabled with it. See DELETE TRANDATA. Remove supplemental logging for any filter tables used for bi-directional replication as well. You can use a wildcard to specify multiple table names.

   DELETE TRANDATA owner.table

9. For PostgreSQL, the registered replication slot must be deleted after removing the Extract, otherwise the database logs will continue to grow.

   DELETE EXTRACT extname
   UNREGISTER EXTRACT extname

On a Target System: