How Upgrade Affects Runtime Data

Integration Data Retention Time

Oracle Integration 3 supports only 32 days of data retention. During upgrade only the most recent 32 days of retained data will be migrated.

For integrations, 32 or fewer days of retained data are typically sufficient.

Historical Data in Activity Stream

The activity stream in Oracle Integration Generation 2 is not moved to Oracle Integration 3. Therefore, after the upgrade completes, historical data for your integrations isn't available in Oracle Integration 3.

The activity stream feature is available in Oracle Integration 3. Therefore, historical information is available from the upgrade date onward.

If you capture the activity stream in Oracle Cloud Infrastructure, this information remains available after the upgrade. If you don't capture this data yet, you can start at any time. See Capture the Activity Stream in Oracle Cloud Infrastructure Console.

Actively Running Synchronous Integrations

When the downtime begins as part of the upgrade, Oracle Integration stops accepting incoming requests for actively running synchronous integrations. Oracle Integration also finishes processing all previously received requests in a few minutes.

During the downtime, any client that sends a request to Oracle Integration gets a failure notice.

Note:

During the downtime, if an integration invokes a co-located integration using a local invoke call, or if an integration is a hybrid integration that uses the connectivity agent, the integration doesn't run successfully.

After the upgrade finishes, Oracle Integration accepts incoming requests again.

Actively Running Asynchronous Integrations

When the downtime begins as part of the upgrade, Oracle Integration stops accepting incoming requests for actively running asynchronous integrations. Oracle Integration also finishes processing the previously received requests. In most cases, Oracle Integration processes the requests in a few minutes.

After the upgrade finishes, Oracle Integration accepts incoming requests again.

Actively Running Scheduled Integrations

When the downtime begins as part of the upgrade, Oracle Integration stops accepting incoming requests for scheduled integrations and finishes processing all previously received requests. In most cases, Oracle Integration processes the requests in a few minutes.

Any requests that Oracle Integration doesn't process in a few minutes are discarded, but no data is lost. Here's why: Oracle migrates the global schedule parameters for the integration and starts the schedule in Oracle Integration 3. After the upgrade is complete and Oracle Integration 3 begins processing requests, Oracle Integration 3 uses the parameters to start processing where Oracle Integration Generation 2 stopped processing.

The post-upgrade cut over is seamless, but depending on when your upgrade occurs, you might experience some business impact. For instance, if an integration sends emails every 30 minutes starting at 9 AM, and your upgrade is from 8:30 AM to 10:30 AM, the email that usually arrives at 9 AM will probably be delayed.

Failed Integration Instances

Oracle does not migrate failed integration instances to Oracle Integration 3.

Additionally, by default, a failed integration instance prevents an upgrade from succeeding. However, an override is available. To upgrade even when you have one or more failed integration instances, you must select the override setting when you schedule the upgrade. If you don't select this setting and have one or more failed integration instances, the upgrade fails.

To learn about your options for failed integration instance, see Complete Upgrade Prerequisites.

To learn about the setting that lets you upgrade with a failed integration instance, see 2. Schedule the Upgrade and Configure Settings.

Integration Insight

Insight isn't supported in Oracle Integration 3. Your Insight models and consoles won't be migrated when you upgrade to Oracle Integration 3. As an alternative, use Oracle Cloud Infrastructure Logging Analytics and Process Automation Analytics.