Database Ingestion service properties

Property	Description
maxTaskUnits	The maximum number of application ingestion and replication task units and database ingestion and replication task units that can run concurrently on an on-premises machine where the Secure Agent is running. Task units are not related to the capacity and availability of your hardware or software. You can configure maxTaskUnits to precisely control CPU usage. Valid values are 1 to 2000000000 (2 billion). To calculate a reasonable number of task units for your Secure Agent machine, Informatica recommends that you divide the number of cores by 3 or 4. For example, if you have an 8-core machine, you could set this property to 2. Then monitor CPU usage and adjust the property value as needed to tune performance. During initial load processing, this property determines the number of tables that can be unloaded simultaneously. Remaining tables are queued and start unload processing when resources become available. Note: A single job can process many tables. The total number of tables that can be processed is limited only by available memory. On the average, 25 MB of RAM is required per table for an initial load task based on a 1 KB row size. During incremental load processing, this property determines the number of application ingestion and replication and database ingestion and replication jobs that can run simultaneously. Setting this property to a value greater than the number of cores on the Secure Agent machine can increase parallelism for task execution but also cause performance bottlenecks at task execution time.
serviceLogRetentionPeriod	The number of days to retain each internal Database Ingestion service log file after the last update is written to the file. When this retention period elapses, the log file is deleted. The default value is 7 days. Service logs are retained on the Secure Agent host where they are created: <infaagent>/apps/Database_Ingestion/logs. Note: This property is applicable to both Application Ingestion and Replication and Database Ingestion and Replication.
taskLogRetentionPeriod	The number of days to retain each job log file after the last update is written to the file. When this retention period elapses, the log file is deleted. The default value is 7 days.
ociPath	For Oracle sources and targets, the path to the Oracle Call Interface (OCI) directory that contains the oci.dll or libcIntsh.so file. By default, Oracle uses $ORACLE_HOME/lib on Linux or %ORACLE_HOME%\bin on Windows. The OCI library is used by database ingestion CDC tasks to connect to Oracle. For a DBMI agent that is running, this value is appended to the PATH environment variable value on Windows or to the LD_LIBRARY_PATH environment variable value on Linux. This property is not required if you already included the OCI path in the PATH or LD_LIBRARY_PATH environment variable. Note: This property is applicable only to Database Ingestion and Replication.
serviceUrl	The URL that the Database Ingestion service uses to connect to the Informatica Intelligent Cloud Services cloud. Note: This property is applicable to both Application Ingestion and Replication and Database Ingestion and Replication.
logLevel	The level of detail to include in the logs that the Database Ingestion service produces. Options are: - TRACE - DEBUG - INFO - WARN - ERROR The default value is TRACE. Note: This property is applicable to both Application Ingestion and Replication and Database Ingestion and Replication.
taskExecutionHeapSize	The maximum heap size, in gigabytes, for the Task Execution service. This value, in conjunction with maxTaskUnits property, affects the number of concurrent application ingestion and replication and database ingestion and replication tasks that can run on a Secure Agent. Try increasing the heap size to run more tasks concurrently. Enter this value followed by "g" for gigabytes, for example, '9g'. The default value is '8g'. Note: This property is applicable to both Application Ingestion and Replication and Database Ingestion and Replication.
useProxy	Set this property to true to enable the DBMI Agent to go through a proxy when connecting to or writing data to targets. The DBMI Agent then uses the proxy settings from the Secure Agent proxy configuration. By default, proxy settings are not used. Note: This property is applicable to both Application Ingestion and Replication and Database Ingestion and Replication.
intermediateStorageDirectory	For incremental load and combined initial and incremental load jobs, the local root directory under which intermediate files that contain data are stored when the Enable Persistent Storage option is selected in the associated task definitions. Note: This property is applicable only to Database Ingestion and Replication.
storageBackupDirectory	For incremental load and combined initial and incremental load jobs, the path to the directory that stores backup files when the Enable Persistent Storage option is selected in the associated task definitions. Note: This property is applicable only to Database Ingestion and Replication.
storageProperties	For incremental load and combined initial and incremental load jobs, a comma-separated list of key=value pairs that is used when the Enable Persistent Storage option is selected in the associated task definitions. Specify this property only at the direction of Informatica Global Customer Support. Note: This property is applicable only to Database Ingestion and Replication.
task_container.jvm.allowExceptionForInvalidEncodedData	If you receive transliteration errors that report invalid encoding to UTF-8, and you do not want to repair or correct the source data, set this property to false so that database ingestion and replication jobs do not fail when trying to unload the data from the source. With this setting, the Database Ingestion service passes an equivalent Java property to the DataDirect JDBC driver to prevent the exception from occurring. After you set this property, you must restart the Database Ingestion service. Note: This property is applicable only to Database Ingestion and Replication.
supportedLoadTypes	For application ingestion and replication jobs and deatabase ingestion and replication jobs, the load types that the Database Ingestion agent service can process. You can enter one or more of the following valies, separated by a comma (,): - INITIAL. Initial load jobs or the initial load phase of combined initial and incremental load jobs. - INCREMENTAL. Incremental load jobs or the incremental phase of combined initial and incremental load jobs, which write to your target.. - INCREMENTAL_STAGING. CDC staging tasks of incremental load or combined load jobs. Default is INITIAL,INCREMENTAL,INCREMENTAL_STAGING, which indicates all load types. Note: If multiple Database Ingestion agents are configured to support the same load types,the jobs use the agent with the most available task units.