Appendix A. GGSCI Commands
In the world of IT, writing a book takes at least a year, in which time technology has moved on and in some cases the contents can be out of date. Therefore, the objective of this appendix is two fold:
To act as a quick reference guide to all the available GoldenGate Software Command Interface (GGSCI) commands, including the GoldenGate installed components
To catch any subjects and terminology not addressed in the previous chapters
Some say that since the Oracle acquisition of GoldenGate, the product has changed its name. This is indeed true; GoldenGate Software (GGS) is now known as Oracle GoldenGate (OGG). No surprise there. However this is not true for the GoldenGate Command Interpreter; it is still called GGSCI and not OGGCI, even in the latest version of GoldenGate!
The following table lists and describes the available GGSCI commands, arranged by command group:
Command Group |
Command |
Description |
---|---|---|
MANAGER |
INFO MANAGER |
Displays the Manager process status information. For example:
Or
|
MANAGER |
REFRESH MANAGER |
Updates the Manager process configuration without stopping and starting. Valid for all configuration parameters except For example:
Or
|
MANAGER |
SEND MANAGER |
Obtains addition status information when used with the following options:
For example:
|
MANAGER |
START MANAGER |
Starts the Manager process. The command supports wildcards. For example:
Or
|
MANAGER |
STATUS MANAGER |
Same as |
MANAGER |
STOP MANAGER |
Stops the Manager process. The command supports wildcards. For example:
Or
|
EXTRACT |
ADD EXTRACT |
Creates a new Extract group. For example:
|
EXTRACT |
ALTER EXTRACT |
Alters an existing Extract group. For example:
|
EXTRACT |
CLEANUP EXTRACT |
Deletes the run history for the specified Extract group. The Extract process must first be stopped. When used with the For example:
|
EXTRACT |
DELETE EXTRACT |
Deletes an Extract group. The Extract process must first be stopped. When used with an exclamation mark, the command will delete all Extract groups associated with a wildcard without prompting for confirmation. For example:
|
EXTRACT |
INFO EXTRACT |
Displays status summary for an Extract process. The For example:
|
EXTRACT |
KILL EXTRACT |
Kills an Extract process. Use when the process cannot be stopped gracefully. For example:
|
EXTRACT |
LAG EXTRACT |
Displays the lag time between the Extract process and the data source. The command supports wildcards. For example:
|
EXTRACT |
SEND EXTRACT |
Sends requests to the Extract process, such as; ad-hoc report generation and statistics. The command can also be used to force the Extract process to be rolled over to next trail file. For example:
|
EXTRACT |
VIEW REPORT |
Allows process reports generated by the SEND command to be viewed. For example:
|
EXTRACT |
START EXTRACT |
Starts the Extract process. The command supports wildcards. For example:
|
EXTRACT |
STATS EXTRACT |
Displays Extract process statistics. For example:
|
EXTRACT |
STATUS EXTRACT |
Provides basic Extract process state. The command supports wildcards. For example:
|
EXTRACT |
STOP EXTRACT |
Stops the Extract process. The command supports wildcards. For example:
|
REPLICAT |
ADD REPLICAT |
Creates a new Replicat group. For example:
|
REPLICAT |
ALTER REPLICAT |
Alters an existing Replicat group. For example:
|
REPLICAT |
CLEANUP REPLICAT |
Deletes the run history for the specified Extract group. The Replicat process must first be stopped. When used with the For example:
|
REPLICAT |
DELETE REPLICAT |
Deletes an Extract group. The Replicat process must first be stopped. When used with an exclamation mark, the command will delete all Replicat groups associated with a wildcard without prompting for confirmation. For example:
|
REPLICAT |
INFO REPLICAT |
Displays status summary for a Replicat process. The For example:
|
REPLICAT |
KILL REPLICAT |
Kills a Replicat process. Use when the process cannot be stopped gracefully. For example:
|
REPLICAT |
LAG REPLICAT |
Displays the lag time between the Replicat process and the data source. The command supports wildcards. For example:
|
REPLICAT |
SEND REPLICAT |
Sends requests to the Replicat process, such as adhoc report generation and statistics. For example:
|
REPLICAT |
VIEW REPORT |
Allows process reports generated by the SEND command to be viewed. For example:
|
REPLICAT |
START REPLICAT |
Starts the Replicat process. The command supports wildcards. For example:
|
REPLICAT |
STATS REPLICAT |
Displays Replicat process statistics. For example:
|
REPLICAT |
STATUS REPLICAT |
Provides basic Replicat process state. The command supports wildcards. For example:
|
REPLICAT |
STOP REPLICAT |
Stops the Replicat process. The command supports wildcards. For example:
|
TRAIL |
ADD EXTTRAIL |
Creates a local trail for an Extract group. For example:
|
TRAIL |
ADD RMTTRAIL |
Creates a remote trail for an Extract or Data pump group. For example:
|
TRAIL |
ALTER EXTTRAIL |
Allows the trail file size to be altered. The Extract process must be restarted for the changes to take effect. For example:
|
TRAIL |
ALTER RMTTRAIL |
Allows the trail file size to be altered. The Extract process must be restarted for the changes to take effect. For example:
|
TRAIL |
DELETE EXTTRAIL |
Deletes the local trail. For example:
|
TRAIL |
DELETE RMTTRAIL |
Deletes the remote trail. For example:
|
TRAIL |
INFO EXTTRAIL |
Provides information on the local trail status. The command supports wildcards. For example:
|
TRAIL |
INFO RMTTRAIL |
Provides information on the remote trail status. The command supports wildcards. For example:
|
PARAMS |
EDIT PARAMS |
Allows a process' parameter file to be edited. The command invokes the default editor, such as vi. For example:
|
PARAMS |
SET EDITOR |
Changes the default editor. For example:
|
PARAMS |
VIEW PARAMS |
Allows a process' parameter file to be viewed. For example:
|
DATABASE |
DBLOGIN |
Provides access to the database with username and password. For example:
|
DATABASE |
ENCRYPT PASSWORD |
Allows the database password to be encrypted in the parameter file. Since Oracle 11g, the password is case sensitive. For example:
|
DATABASE |
LIST TABLES |
Lists tables in a database schema. The command supports wildcards. The command must follow a successful For example:
|
TRANDATA |
ADD TRANDATA |
Adds supplemental logging to a database table, necessary for transactional changes to be written to the redo logs. The command must follow a successful For example:
|
TRANDATA |
DELETE TRANDATA |
Stops the supplemental logging on a database table. The command supports wildcards and must follow a successful For example:
|
TRANDATA |
INFO TRANDATA |
Provides supplemental logging status on a database table. The command supports wildcards and must follow a successful For example:
|
CHECKPOINT |
ADD CHECKPOINTTABLE |
Adds a Checkpoint table on the target database. The command must follow a successful For example:
|
CHECKPOINT |
CLEANUP CHECKPOINTTABLE |
Removes obsolete checkpoint records from the Checkpoint table. Use when Replicat groups are deleted or Trail files are removed. The command must follow a successful For example:
|
CHECKPOINT |
DELETE CHECKPOINTTABLE |
Deletes the Checkpoint table from the database. The command must follow a successful For example:
|
CHECKPOINT |
INFO CHECKPOINTTABLE |
Displays the existence and creation date of the Checkpoint table. The command must follow a successful For example:
|
MISC |
! |
Runs the last executed command. For example: ! |
MISC |
CREATE SUBDIRS |
Creates the GoldenGate subdirectories. For example:
|
MISC |
FC |
Display, edit, and execute the last command. For example:
|
MISC |
HELP |
Provides help on command syntax. For example:
|
MISC |
HISTORY |
Lists a history of GGSCI commands used. For example:
|
MISC |
INFO ALL |
Displays a summary of the configured processes. For example:
|
MISC |
OBEY |
Invokes a GGSCI command script. For example:
|
MISC |
SHELL |
Allows OS commands to be executed from GGSCI For example:
|
MISC |
SHOW |
Shows environment information. For example:
|
MISC |
VERSIONS |
Displays version of OS and database. For example:
|
MISC |
VIEW GGSEVT |
Displays the contents of the GoldenGate event log For example:
|