$ sqdconf mount /<SQDATA_VAR_DIR>/udbcdc/udbcdc.cab
$ sqdconf apply /<SQDATA_VAR_DIR>/udbcdc/udbcdc.cab
$ sqdconf start /<SQDATA_VAR_DIR>/udbcdc/udbcdc.cab It is important to realize that the message from SQDCONF indicating that the start command was executed successfully, does not necessarily mean that the agent is still in started state. It only means that the start command was accepted by the capture agent and that the initial setup necessary to launch a capture thread were successful. These preparation steps involve connecting to UDB and setting up the necessary environment to start a log mining session.
The capture agent runs as a daemon, so it does not have a terminal window to emit warnings or errors. Such messages are instead posted in the system log. The daemon name for UDB capture is sqdudbc. If there is a mechanism in place to monitor the system log, it is a good idea to include the monitoring of sqdudbc messages. This will allow you to detect when a capture agent is mounted, started, or stopped - normally or because of an error. It will also contain, for most usual production error conditions, some additional information to help diagnose the problem.