Removing Database Objects
Follow these instructions to remove supplemental logging and any Oracle GoldenGate CDC Cleanup objects (for SQL Server) from the source database in the Oracle GoldenGate Extract configuration, and to remove the checkpoint table in the Replicat configuration. Specific steps and commands may not apply to your configuration.
On a Source System:
-
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.
-
Run
ggsci
from your Oracle GoldenGate directory. -
Stop all Oracle GoldenGate processes.
STOP ER *
-
Stop the Manager process.
STOP MANAGER
-
In GGSCI, log into the database with the
DBLOGIN
(or theMININGDBLOGIN
command if you need to remove a database logmining server from a downstream mining database).[MINING]DBLOGIN
requires privileges granted in thedbms_goldengate_auth.grant_admin_privilege
procedure.[MINING]DBLOGIN USERIDALIAS
alias
-
In GGSCI, run any or all of the following commands, depending on your configuration.
-
Disable schema-level supplemental logging (wildcards are not allowed):
DELETE SCHEMATRANDATA
schema
[NOSCHEDULINGCOLS | ALLCOLS] -
Disable table-level supplemental logging.
DELETE TRANDATA [container.]schema.table [NOSCHEDULINGCOLS | ALLCOLS]
-
(Bidirectional configuration) Remove the Oracle trace table.
DELETE TRACETABLE [container.]schema.table
-
(Classic capture configuration) Disable log retention.
DBLOGIN
requires privileges shown in Log Retention Options.UNREGISTER EXTRACT
group
LOGRETENTION -
(Integrated capture configuration) Remove the database logmining server from an Oracle mining database.
DELETE EXTRACT group UNREGISTER EXTRACT group DATABASE
-
-
Run the following Oracle procedure to remove the privileges from the Oracle GoldenGate administration users for both classic and integrated processes.
dbms_goldengate_auth.revoke_admin_privilege('ggadm')
On a Target System: