Database Ingestion agent service availability during an upgrade
A light-weight version of the Database Ingestion service that runs under the Secure Agent (DBMI Agent) is available to minimize the downtime of application ingestion and replication jobs and database ingestion and replication jobs during application upgrade processing.
The light-weight DBMI Agent runs only essential services during startup and stands by until the cloud upgrade completes. As it reaches standby status, the older DBMI Agent version shuts down and migrates application ingestion and replication jobs and database ingestion and replication jobs to the light-weight DBMI Agent version.
•Incremental load and combined load jobs that are performing CDC processing are stopped and restarted on the light-weight DBMI Agent from where they last left off.
•Initial load jobs and combined load jobs in the unload phase are restarted from the beginning on the light-weight DBMI Agent.
Because the light-weight DBMI Agent is available to accept ingestion and replication jobs during the upgrade process, the jobs experience minimal downtime.
If the light-weight version of the DBMI Agent fails to start, for example, because of low memory on the Secure Agent machine, the older version of the DBMI Agent continues running for up to 24 hours, ensuring that no service disruption occurs while startup of the light-weight DBMI Agent is retried.
Note that Database Ingestion agent service log files, including Metadata Manager,Task Container, and DBMI Agent log files, include the application package version to enable both agents to run during migration for minimal downtime.