In our verification, even when executing SHRINK SPACE on the source database using the following queries, it appears that the SHRINK SPACE operation is not being replicated to the target database.
▼ Queries
ALTER TABLE <TABLE_NAME> ENABLE ROW MOVEMENT;
ALTER TABLE <TABLE_NAME> SHRINK SPACE CASCADE;
Therefore, regarding the above statement that SHRINK SPACE is supported, what behavior is Qlik Replicate expected to perform when a SHRINK SPACE operation is executed on the source database?
When a SHRINK SPACE operation occurs,Replicatewill capture all of the changes logged to the redo log as a result of the operation and ignore them.
The following message will appear in the task’s log file:
Operations generated by the SHRINK SPACE process were ignored.
Monitoring considerations:
WhenReplicatecaptures changes resulting from a SHRINK SPACE operation, the task’s Incoming Changes bar will indicate an unusually large number of changes. However, these changes will not be reflected in the Applied Changes pie chart or the Applied Changes Details table.
Limitations and considerations section for the limitations related to SHRINK SPACE operations inReplicate Log Readerand LogMiner mode.
Regarding the term “ignore” used in this article, does it mean that the SHRINK SPACE operation itself is ignored and not executed on the target database?
If the SHRINK SPACE operation itself is ignored, then what exactly does “Only table-level SHRINK SPACE operations are supported” mean?
Does it simply mean that running SHRINK SPACE on the source database will not cause the task to stop or fail, rather than meaning the operation is replicated to the target?
