You can stop and start Oracle Integration Generation 2 instances. After a stop request is initiated, the instance goes into a pausing state. During the pausing state, no new integrations and processes are started. In-flight integrations and processes continue until they either complete or reach a checkpoint. When the integrations and processes are no longer running, the instance goes into a completely paused state. During this state, Oracle Integration design time, settings, and monitoring capabilities are unavailable.

1. Start or stop an instance in either of two ways:
   1. On the Integration Instances page, go to the end of the row for the specific instance, and click . Note that an active instance is identified as Active and an inactive/stopped instance is identified as Inactive in the State column.
   2. On the details page of a specific instance, click the More Actions menu.
2. Select the action to perform:
   1. To stop your instance, select Stop, then select Stop again when prompted to confirm your selection.

      The instance state changes to Updating during the pausing process. When complete, the state changes to Inactive in the State column.

      This action causes the following to occur:

      • For Oracle Integration users, billing is paused for the duration that the instance is paused. For Oracle Integration for SaaS users, billing is not impacted by pausing an instance.
      • Integration endpoints are paused.
      • Process instances are paused.
      • Runtime is paused.
      • Scheduled integrations do not execute.
      • Database purging continues to run.
      • REST APIs are unavailable for use. If you attempt to use the APIs while your instance is in a paused state, you receive a 409 error.
      • Design time is not available for use. If you access the Oracle Cloud Infrastructure Console, it displays a page indicating the stopped state and asks you to start the instance for the console to become available.
      • You cannot stop an instance if patching is in progress.
   2. To resume your instance, select Start, then select Start again when prompted to confirm your selection.
      Note
      
      

      • You cannot start an instance when maintenance and security patching are in progress.
      • If you stop your instance for more than 24 hours, the connectivity agent shuts down. You need to manually restart the connectivity agent when you restart your instance. See Restart the Agent in Using Integrations in Oracle Integration Generation 2.

      The instance state changes to Updating during the resumption. When complete, the state changes to Active in the State column.