Before you configure application ingestion and replication tasks for initial, incremental, or combined initial and incremental load operations, review the following limitations and guidelines:
•Application Ingestion and Replication does not support the Cloud Hosted Agent, a runtime environment on a cloud platform, or the serverless runtime environment. Use a local Secure Agent installation.
•If a Secure Agent in a runtime environment that is assigned to a application ingestion and replication task terminates, you cannot undeploy the associated ingestion job, update the task to specify another runtime environment, and deploy the task again. In this situation, perform one of the following actions:
- Assign a different Secure Agent to the runtime environment. Ensure that the new Secure Agent is running. Then restart the associated ingestion job.
- Copy the task. In the task copy, specify another runtime environment that has an active Secure Agent. Then deploy the task and run the associated ingestion job.
•If you run multiple incremental load or combined initial and incremental load jobs against the same source, you cannot move capture processing of some source objects from one job to another job or merge the jobs into a single job, without resynchronizing the source and target objects being processed by the new job. Each job maintains a unique recovery checkpoint. If you try to move capture processing of an object from one job to another job, the correct recovery information for that table is not maintained, potentially causing data loss or duplicate events on the target.
•Application Ingestion and Replication uses the minimum source constraints needed for replication when generating target objects. If a source has a primary key, the job preferentially uses the primary key and no other constraint when creating the target object.
Source object properties that are not required for replication, such as for storage and partitioning, are not reflected on the target
.
•Because Data Ingestion and Replication seeks to maintain consistency between the source and target when replicating data, it does not add or recognize any constraints on the target, such as those for nullability, foreign keys, and defaults. Doing so could lead to inconsistencies between the source and target and potential replication errors. For example, errors could occur if the NOT NULL constraint is added to a target column that receives data from a nullable source column, or if the DEFAULT constraint is added to a target column that receives source data that doesn't match the default.
Note: If source constraints exist at the time of task deployment, they're not re-created at the target because they might not have existed previously when data was added to a source column and captured.