Direct the agent to disconnect a "target" engine. Agent must be Mounted and Started. The downstream effect of the Disconnect is similar to Stop in that the disconnected engine will terminate. The difference is that the agent will continue to capture changes. This is particularly useful when more than one engine is subscribed to the same capture agent and there is no need to stop all the engines at the same time. It is also useful for Oracle and UDB capture agents where there is risk of losing access to archived logs.
Syntax
sqdconf disconnect <cab_file_name>
--target=<target_name>
Keyword and Parameter Descriptions
| Keyword | Description |
|---|---|
| --target=<target_name> | The subscribing apply engine. |
Note:
- This will result in a mounted, started, stalled state.
- Relational Captures that use CDCSTORE transient data manager, will utilize the storage configured for CDCSTORE. Disconnecting an apply engine for an extended period of time makes sizing of the allocated space an important task and must consider the volume and size of the workload being captured. Once all of the preallocated storage has been used after the disconnect, the agent will report a "FULL" condition. That is normal and simply means that no more data will be captured until existing data has been published. If however there are multiple Engines subscribing to the Capture, those Engines will remain connected but effectively be paused since the transient storage area is filled to capacity blocking further data from being published.