Making Basic Updates to a Connector
Update a connector in Connector Hub.
Note
- To avoid automatic deactivation by Oracle Cloud Infrastructure, validate that the connector successfully moves data by checking for expected results at the target service and optionally enable logs.
- It's not possible to retrofit an existing connector to use a stream with a private endpoint. If the stream pool selected for the stream source or target is public, it can't be changed to private, and the connector can't be updated to reference a private stream. To change the source or target to use a different private stream, or to use a source or target other than Streaming, re-create the connector with the source and target that you want. An example of the need for a different private stream is a stream that was moved to a different stream pool. In that case, re-create the connector using the moved stream. Ensure that you deactivate or delete the old connector with the stream source or target that you don't want any more.
When you update a connector, For more information about tagging, see Resource Tags.
If you updated the source service or tasks, then data movement might pause for a few minutes, as indicated by Data Freshness metrics. Within a few minutes, the connector begins moving data according to its configuration. The connector applies tasks to data from the source service and then moves the data to the target service. Use the oci sch service-connector update command and required parameters to update a connector:
oci sch service-connector update --service-connector-id <connector_OCID>
For a complete list of parameters and values for CLI commands, see the CLI Command Reference.
Run the UpdateServiceConnector operation to update a connector.