Administrator > Secure Agent services > Database Ingestion service
  

Database Ingestion service

The Database Ingestion service (DBMI agent) enables you to define and run database ingestion tasks. You configure database ingestion tasks in the Mass Ingestion service.
After you download the Secure Agent to your runtime environment, the DBMI packages are pushed to the on-premises system where the Secure Agent runs, provided that you have custom licenses for both Mass Ingestion Databases and the DBMI packages. You can then optionally configure properties for the Database Ingestion service that runs on the Secure Agent.

Database Ingestion service properties

To change or optimize the behavior of the Database Ingestion service (DBMI agent) that the Secure Agent uses, configure Database Ingestion properties for your runtime environment.
To configure the properties, open your runtime environment. Under System Configuration Details, click Edit. Then select the Database Ingestion service and the DBMI_AGENT_CONFIG type.
The following table describes these agent properties:
Property
Description
maxTaskUnits
The maximum number of database ingestion tasks that can run concurrently on the on-prem machine where the Secure Agent runs. The default value is 10.
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.
Note: Service logs are retained on the Secure Agent host where they are created: <infaagent>/apps/Database_Ingestion/logs.
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) file oci.dll or libcIntsh.so. For a DBMI agent that is running, this value is appended to the path that is specified in the PATH environment variable on Windows or in the LD_LIBRARY_PATH environment variable on Linux.
serviceUrl
The URL that the Database Ingestion service uses to connect to the Informatica Intelligent Cloud Services cloud.
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.
taskExecutionHeapSize
The maximum heap size, in gigabytes, for the Task Execution service. This value, in conjunction with maxTaskUnits property, affects the number of concurrent database ingestion 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'.

Database Ingestion Agent environment variables

To change or optimize the behavior of the Database Ingestion (DBMI) Agent, define the following environment variables:
Environment Variable
Description
DBMI_REPLACE_UNSUPPORTED_CHARS
For Microsoft Azure SQL Data Warehouse targets, controls whether a database ingestion job replaces characters in character data that the target cannot process correctly. To enable character replacement, set this environment variable to true.
DBMI_REPLACE_UNSUPPORTED_CHARS=true
Mass Ingestion Databases then uses the character that is specified in the DBMI_UNSUPPORTED_CHARS_REPLACEMENT environment variable to replace unsupported characters.
DBMI_UNSUPPORTED_CHARS_REPLACEMENT
If the DBMI_REPLACE_UNSUPPORTED_CHARS environment variable is set to true, specifies the character that replaces the characters in source data that a Microsoft Azure SQL Data Warehouse target cannot process correctly.
Default value: ? (question mark)
DBMI_WRITER_CONN_POOL_SIZE
Indicates the number of connections that a database ingestion job uses to propagate the change data to the target. The default value is 8. Valid values are 4 through 8.
DBMI_WRITER_RETRIES_MAX_COUNT
If a network issue occurs while a database ingestion job is loading source data to an Amazon S3 or Microsoft Azure Data Lake Storage Gen2 target, indicates the maximum number of times that the database ingestion job retries a request to continue the initial load or incremental load. If all of the retries fail, the job fails.
The default value is 5.
DBMI_WRITER_RETRIES_INTERVAL_IN_MILLIS
Specifies the time interval, in milliseconds, that a database ingestion job waits before retrying the request to continue the initial load or incremental load to an Amazon S3 or Microsoft Azure Data Lake Storage Gen2 target if a network issue occurs.
The default value is 1000.
Note: After you define or change an environment variable, restart the Database Ingestion Agent for the changes to take effect.