|
start |
Scroll |
Activate the agent. The agent must be mounted and not already started.
Syntax
sqdconf start <cab_file_name>
[--safe-restart=<number>]
[--pause]
[--ziip]
[--no-ddl-tracking]
Keyword and Parameter Descriptions
[--pause] - Pause the agent immediately after the start.
[--safe-restart=<number>] - If the value given is negative, this is the offset to be added to the calculated restart log point. The calculated restart log point for an agent mining the raw logs is the last known safe_restart_point, based on the transactions in-flight at the time when the capture last ran, or the current log point at the time of this start. Except for the later case, there is no good reason to use this parameter for a routine restart. Especially since using such a parameter will invalidate any attempt by the capture agent to avoid sending duplicate log records, in the case when the last run stopped in the middle of a partially committed transaction due to MQ max uncommitted parameter.
If the agent is using the committed only feature of logminer, then the offset is applied to the calculated restart point, which is either the last commit point seen when the agent was last running or, if not available, the current SCN at the time of this start. In the absence of --safe-restart parameter the capture agent would restart mining as far back as the archived logs at its disposal would allow. This is the safest way to avoid missing in-flight transaction between restarts. In some cases, you may be able to decide that such safety precaution are too conservative. This parameter will allow you to limit the scope of such re-mining.
If the value is positive,this is taken as the absolute log-point to be used to reset the restart log point. This value must be before the last know restart log point and after the oldest log point the archived logs make available. Furthermore, in the case of a capture agent exploiting the raw log records, setting the value before the last known restart point but after the last known safe restart point will provoke a warning. Proceed at your own risk.
[--ziip] - z/OS ONLY, Precisely recommends zIIP processors be used to enhance CPU cycle efficiency and reduce CPU cost associated with NaCL software encryption and Log Stream I/O.
[--no-ddl-tracking] - Db2/z ONLY. Implementation of Db2 Schema Evolution in 4.0 requires the Db2 Log Capture to look at both the catalog and log for schema changes. This delays initial startup because of pre-capture log processing. The pre-scan can be eliminated using this parameter but must be used with caution because it will disable automatic Schema Evolution by downstream Replicator Engines.
