2.24 DELETE CHECKPOINTTABLE
Not valid for Replicat for Java, Oracle GoldenGate Applications Adapter, or Oracle GoldenGate Big Data.
Use DELETE CHECKPOINTTABLE
to drop a checkpoint table
from the database. Use the DBLOGIN
command to establish a database
connection before using this command.
To stop using a checkpoint table while the associated Replicat group remains active, follow these steps:
-
Run GGSCI or Admin Client.
-
Stop Replicat.
STOP REPLICAT group
-
Delete the Replicat group and then add it back with the following commands.
DELETE REPLICAT group ADD REPLICAT group, EXTTRAIL trail, NODBCHECKPOINT
-
Exit GGSCI or Admin Client, then start it again.
-
Start Replicat again.
START REPLICAT group
-
Log into the database with the
DBLOGIN
command, using the appropriate authentication options for the database. -
Delete the checkpoint table with
DELETE CHECKPOINTTABLE
.
If the checkpoint table is deleted while Replicat is still running and transactions are occurring, Replicat will abend with an error that the checkpoint table could not be found. However, the checkpoints are still maintained on disk in the checkpoint file. To resume processing, add the checkpoint table back under the same name. Data in the trail resumes replicating. Then, you can delete the checkpoint table.
Syntax
DELETE CHECKPOINTTABLE [[container
. | catalog
.]owner.table] [!]
-
container
. |
catalog
. -
The Oracle pluggable database, if applicable. If this option is omitted, the catalog or pluggable database defaults to the one that is associated with the
SOURCEDB
,USERID
, orUSERIDALIAS
portion (depending on the database) of theDBLOGIN
command. -
owner.table
-
The owner and name of the checkpoint table to be deleted. An owner and name are not required if they are the same as those specified with the
CHECKPOINTTABLE
parameter in theGLOBALS
file. -
!
-
Bypasses the prompt that confirms intent to delete the table.
Example
DELETE CHECKPOINTTABLE ggs.fin_check
Parent topic: Common Command Line Interface Commands