Deactivating an integration in Oracle Integration is a non-destructive action designed to pause its execution. This action immediately stops the integration from accepting and processing new messages. However, it does not delete or purge any existing data. All historical information, including monitoring details, tracking data, and completed runtime instances, is preserved and remains accessible on the monitoring pages. This data is subject to the standard retention policy of the Oracle Integration instance, not the activation status of a specific integration. Deactivation is a reversible state, unlike deletion.

A. Deactivating an integration immediately disables its trigger, effectively stopping the acceptance and processing of any new inbound messages or events.

C. For event-based integrations, OIC specifically provides an option to retain the event subscription for six hours, allowing missed events to be processed upon reactivation.

D. As the integration is inactive, it cannot execute or create new instances. Consequently, no new failed instances can be generated or observed after deactivation.

1. Oracle Cloud Infrastructure Documentation

Using Integrations in Oracle Integration 3

"Activate and Deactivate Integrations": This document explicitly states

"When you deactivate an integration

the trigger is disabled and no new instances are accepted... You can still monitor instances of a deactivated integration on the Track Instances page." This directly confirms that historical data is not lost (invalidating option B) and that new messages are stopped (validating option A).

2. Oracle Cloud Infrastructure Documentation

Using Integrations in Oracle Integration 3

"Manage Integrations in the Designer"

Section: "Deactivate an Integration": This section details the deactivation process for event-based integrations

stating: "If you select to retain the subscription

Oracle Integration Cloud waits six hours for you to reactivate the integration. If you reactivate within six hours

any events that occurred during the deactivation period are sent to the integration for processing." This validates option C.