tasks for initial, incremental, or combined initial and incremental load operations, review the following limitations and guidelines:
Mass Ingestion Databases
does not support the Hosted Agent.
Mass Ingestion Databases
supports multiple agents in a Secure Agent group.
In initial load jobs, each subtask of the job is assigned to the agent that has the maximum spare capacity. If the job stops, you can restart it. After the restart, the job will be allocated again to agents with the most spare capacity at the time.
In incremental load jobs and combined initial and incremental load jobs, only one agent is assigned. The same agent will be used if the job is restarted.
If a Secure Agent in a runtime environment that is assigned to a
database ingestion
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 a Secure Agent service on Windows and plan to use Flat File connections, ensure that the logon account for the Secure Agent is an Administrator account. Otherwise, an error occurs when you try to configure a Flat File connection.
Mass Ingestion Databases
uses UTF-8 as the code page. If you select another code page type when defining a connection,
Mass Ingestion Databases
ignores it.
Mass ingestion jobs unload binary data in hexadecimal format when the data will be sent to an Amazon S3, Flat File, or Microsoft Azure Data Lake Storage target. Each hexadecimal column value has the "0x" prefix. If you want to use output files to load the data to a target, you might need to edit the files to remove the "0x" prefixes.
If a source column has a numeric data type that is not compatible with any numeric data type on the target,
Mass Ingestion Databases
maps the source column to a target varchar column.
Mass Ingestion Databases
does not display error messages that are longer than 1024 characters in the user interface. Instead,
Mass Ingestion Databases
prompts you to see a log file with the error, which is automatically downloaded.
Informatica recommends that source tables have primary keys. If a source table does not have a primary key, Mass Ingestion Databases treats all columns as part of the primary key. In this case, each Update operation is processed as a Delete followed by an Insert on any target. Also, if you change the source primary key and have an Amazon S3, Flat File, Google Cloud Storage, or Microsoft Azure Data Lake Storage target, Mass Ingestion Databases processes each Update operation as a Delete followed by an Insert on the target.
ASK INFAPreview
