1. Using Integrations in Oracle Integration 3
  2. Monitor Integrations During Runtime
  3. Manage Errors

Manage Errors

You can manage errors from the Errors pages in Oracle Integration. You can resubmit failed instances, discard failed instances, view message recovery status, and view basic and detailed error messages. You can also view and download the activity stream, which provides access to error messages and message payloads in failed instances.

Topics:

See About Error Management.

View Error Messages and the Message Payload in the Activity Stream of Failed Instances

You can view error messages and the message payload in the activity stream of failed integration instances on the Errors page. You can also download the activity stream logs and the payload of the failed section of an integration instance.

  1. In the navigation pane, click Observability, then Errors.
  2. Perform the following tasks:

Filter the Display of Error Message Details

  1. Click Filter Filter icon to filter the display of errors by the following:
    • Last updated or creation time
    • Project (begin entering a name to display a list from which to select)
    • Integration

      Begin typing an integration name. Do not use copy and paste. The filter is refreshed to display fields for the defined secondary business identifiers.

      You can now begin typing the values of the business identifiers to narrow down the search. This input follows the same rules (for example, for exact matches and phrase matches) as described in Search for Primary and Secondary Business Identifier Values.

    • Error type (all, recoverable, or nonrecoverable)
    • Instance ID
    • Error message
      For example:
      • Enter part of an error message, such as unknown, unauthorized, or endpoint.
      • Enter an exact phrase match of an error message in double quotes, such as "Could not activate endpoint for endpointID"
    • Detailed error message
    • Connection name
    • Integration style (all, application, schedule, or event)
    • Integration state (all, retained, or purged)
    When you enter an integration name, the filter is refreshed to display fields for the defined business identifiers. You can enter variable values with special characters or variable values of multiple words with white space in double quotes (for example, &filename or "file tracking").


    This image shows the Sort by, Time Window with Data Range button and Last button, From, To, Project, Integration, Error Type, Instance ID, Error message, Detailed error message, Connection, Integration style, and Display instances fields.

  2. Click Date Range in the Time Window section.
  3. Specify a custom time range with which to filter the search for errors with the From and To buttons. This functionality also exists on other monitoring pages such as the Instances page and Monitor Integrations page.

View Error Message and Payload Details on the Errors Page

Error message details can be displayed in two parts: a summarized error message for easy understanding and resolution and, if necessary, a more specific error message if more detailed troubleshooting is required. You can view error messages on the Errors page or by clicking on a business identifier to view the entire integration flow on the Instance Details page. You can also view the payload details in the activity stream of a failed instance.

  1. Hover over the row of the failed instance.
  2. Click View View icon. The Activity Stream panel opens. The activity stream shows details about the movement of the message through the integration, including where any failures occurred. The date and time according to your user preferences are displayed.


    The activity stream shows a nonrecoverable error message link at the top. Below this, the tracing level is set to production. Three icons appear to the far right. Below the tracing level are entries that show the movement of the message payload through the integration. All are green (successfully processed) except for the last one, which is red (failed processing).

  3. Click Download Logs Download icon at the top of the activity stream to download the activity stream logs for the entire instance.
  4. Scroll through, expand milestones, and click View Payload View icon to view the payload for the part of the integration flow that failed.


    The activity stream shows a nonrecoverable error message link at the top, which is being clicked. Below this, the tracing level is set to production. Three icons appear to the far right. Below the tracing level are entries that show the movement of the message payload through the integration. The last entry is in error and is selected to show entries for Summary, Detail, and three icons. Summary is selected to show the payload.

    An option is provided in the activity stream for quickly showing all error content only. This option can be especially useful for instances in which a logic action such as a for-each loop or while loop with many iterations has failed. This option enables you to jump quickly to the iteration that failed instead of scrolling through each iteration of the loop to access the errors. Show errors in either of two ways:

    1. Click View Errors View errors icon to view only the errors in the activity stream. This persists the selection of errors in the activity stream across multiple instances until you deselect the button. This button enables you to toggle between showing only errors and showing all content in the activity stream.


      The activity stream shows the instance ID at the top. Below is the error message and tracing level. To the right are the view errors icon, expand icon, and download logs icon.

      or

    2. Click the error in the activity stream banner to jump to that specific error.


      The activity stream shows a nonrecoverable error message link at the top, which is being clicked. Below this, the tracing level is set to production. Three icons appear to the far right. Below the tracing level are entries that show the movement of the message payload through the integration. The clicked error at the top has been highlighted below in the activity stream.

  5. Perform tasks within the failed part of the payload.
    Element Description
    Download Payload Download icon Click to download this part of the payload to your desktop.
    Copy Payload Copy to clipboard icon Click to copy this part of the payload for pasting into a document.
    Toggle Line Numbers Toggle line numbers icon Click to show or hide line numbers in the payload.

    or

  1. Hover over the row of the failed instance.
  2. Click Expand Expand icon to view a summarized version of the error message for easy understanding and a detailed version that describes how to resolve the error.


    This image shows the summarized error message and detailed error message.

View the Flow of the Failed Instance and Payload Errors in the Activity Stream on the Instance Details Page

You can view the flow of the failed instance to identify any trigger, actions, or invokes in error on the Instance Details page. You can also drill into those elements to view specific error messages and payload errors.

  1. Click a specific business identifier of an integration instance in the Primary Identifier column.
    The cursor is hovered over a business identifier in the Name column.

    The integration flow of the failed instance and Activity Stream panel are displayed.

  2. Scroll through the flow to find the trigger, action, or invoke in error.
  3. Click the element, then click Actions Actions icon and select View Error.


    This image shows a for each action that includes a map action and an integration action. The Actions menu of the integration action is selected to show the View, View Child Instance, View Error (which is being selected), and Activity Stream options.

    The Activity Stream panel opens to the specific section at which the error occurred. For this example, the error occurred in an integration action (parent integration calling a child integration) of a parallel for-each action. All five of the iterations of the parallel for-each are displayed for viewing in the activity stream.


    The image shows the Activity Stream panel. A download icon appears to the right. Below is the activity stream of milestones in the integration flow. A parallel for each is in error. It has been expanded to show additional details.

  4. Scroll through and view the errors.
  5. Click Activity Stream Activity stream icon to close the activity stream. This link operates as a toggle for closing or opening the activity stream.
  6. Click the failed trigger, action, or invoke again, then click Actions Actions icon and select Activity Stream.

    This also opens the Activity Stream panel to the specific section at which the error occurred.


    The integration flow appears on the left. The integration action in error is shown in red. The Actions menu for the integration element in error has been selected to show the exact section of the activity stream where the error occurred.

  7. Scroll through the payload and expand the sections in error to view specific details.
  8. Click View Payload View icon to view the payload of the section in error.


    The error in the activity stream section is expanded to show the error. The Summary, Detail, download payload, copy payload, and toggle row number buttons are shown above the error.

  9. Perform other tasks within this section.
    Element Description
    Summary Click to view a summary of payload details. This action also highlights the section of the integration flow in error.
    Details Click to view more specific payload details. This action also highlights the section of the integration flow in error.
    Download Payload Download icon Click to download this part of the payload to your desktop.
    Copy Payload Copy to clipboard icon Click to copy this part of the payload for pasting into a document.
    Toggle Line Numbers Toggle line numbers icon Click to show or hide line numbers in the payload.
  10. Click Activity Stream The activity stream icon to close the activity stream.

Resubmit Failed Messages

You can manually resubmit failed messages. Oracle Integration does not automatically resubmit failed messages. After resubmitting an instance, you can track all resubmissions of that instance on the Instances page. You can also change the tracing level for a resubmitted message.

After resubmitting a failed message, the instance can restart from different places in the integration:
  • From the beginning of the integration.
  • From another location in the integration, depending upon the design. For example, if there is a wait activity in the integration prior to the recoverable fault, then resubmitting the fault starts the integration just after the wait activity.
Faulted instances in asynchronous flows in Oracle Integration are recoverable and can be resubmitted. An exception to this are scheduled flows with scheduled parameters, which are nonrecoverable. Synchronous flows also cannot be resubmitted. You can resubmit an instance a maximum of ten times. You can resubmit errors in the following ways:

  • Single failed message resubmissions

  • Bulk failed message resubmissions

There is a time window for recovering a failed integration instance that's recoverable. See Service Limits in Provisioning and Administering Oracle Integration 3.

Error instances that are resubmitted and successfully resolved are removed from the error list. If an instance is resubmitted and is in progress, a state of In Progress is displayed in the list. During this state, additional resubmissions of this error instance are not permitted.

Note:

Do not discard a message that you want to resubmit. A discarded message cannot be resubmitted.

  1. In the navigation pane, click Observability, then Errors.

  2. Click Filter Filter icon, then select the time period or retention period during which to search for integration errors.


    Description of oic3_resubmit_error.png follows
    Description of the illustration oic3_resubmit_error.png

  3. Resubmit errors in either of two ways:

    1. Hover over the row of the specific error to resubmit.

    2. Click Resubmit Retry icon.

      The Resubmit instance panel opens.

    3. Select the tracing level to use for the resubmitted instance. When resubmitting an errored integration instance, you can change the level of tracing (production, audit, or debug) for just this specific resubmitted instance. Increasing the tracing level (for example, setting it to Debug) enables you to view more specific information about errors in the activity stream and downloaded logs. This setting applies only to this instance and does not change the tracing level set when the integration was activated.
      • Production
      • Audit
      • Debug

      The tracing options provide different levels of information logging. See Activate an Integration.

      When the instance resubmission completes, the activity stream provides details. The tracing level shown at the top represents the level set during integration activation. To see details about the tracing level set for this specific resubmission, scroll down to this message:
      Recovery process initiated (Tracing level: Debug)


      The Activity Stream panel instance ID, error message, and tracing level set during integration activation at the top. In the stream is the message indicating that the tracing level was set to debug for this integration instance: Recovery process initiated (Tracing level: Debug).

    Or

    1. Select the check boxes of errors to resubmit together. Only instances identified by the Resubmit Retry icon icon that is visible when you hover over a row can be resubmitted.

    2. Click Resubmit in the upper right corner.

      Note:

      This method of message resubmission does not allow you to select the tracing level to use for the resubmitted instance. Instead, the tracing level selected during integration activation is used.
  4. Click Confirm to resubmit the instance when prompted.

    A Resubmission summary panel opens with details about the instance being resubmitted for processing. Click Refresh Refresh icon to see if it still appears on the Errors page before trying another resubmission.

    Instances aren't accepted for resubmission for the following reasons:
    • The instance is not recoverable.
    • The instance has reached the maximum number of retries limit.
    • The instance has not yet reached the deadline for recovery set internally for batch processing.

You can track all instance runs (both the initial run and all resubmissions) above the activity stream on the Instance Details page.

  1. In the navigation pane, click Observability, then Instances.
  2. Click the instance name.
  3. Note the number of instance runs above the Activity Stream panel. The number 1 indicates that this is the first run of the integration.

    <- 1 of 2 submissions ->


    The business identifier appears at the top. To the right is the In Progress and refresh icon. Below are four icons, the instance of value, and the Tracing level: Production. Below is the integration flow consisting of schedule, map, and invoke elements. To the right is the Activity Stream panel, which shows major milestones in the flow. Above the panel are the number of submissions and three icons.

  4. Click -> to access tracking details for the first resubmission of this instance (that is, the second run of this instance).

    The status for the first resubmitted instance is displayed.

    The business identifier appears at the top. To the right is the In Progress and refresh icon. Below are four icons, the instance of value, and the Tracing level: Production. Below is the integration flow consisting of schedule, map, and invoke elements. To the right is the Activity Stream panel, which shows major milestones in the flow A processing error appears in red for the invoke. Above the panel are the number of submissions and three icons.

  5. Click the <- to return to the tracking details for the first run of this instance.

Discard Errors

You can discard errors based on the integration in which they occurred. A discarded error message is removed from the Errors page and can be seen in an aborted state on the Instances page. You cannot perform any further operations on a discarded message, including recovery. After a certain time period, the error message is permanently deleted from the server.

To discard errors:
  1. In the navigation pane, click Observability, then Errors.
  2. Click Filter Filter icon, then select the time period or retention period during which to search for integration errors.
    You can also specify a custom time range for which to search for errors.


    Description of oic3_abort_error.png follows
    Description of the illustration oic3_abort_error.png

  3. Discard errors in either of two ways:
    1. Select the check boxes of individual errors to discard. Only instances identified by the Abort Abort icon icon that is visible when you hover over a row can be discarded.
    2. Click Abort.
    or
    1. Go to the row of the specific error to discard.
    2. Click Abort Abort icon.
  4. Click Confirm to abort the instance when prompted.
    A message is displayed at the top of the page:
    Instance ID "number" is submitted for abort. Click on the refresh button to see if this instance still appears on the errors list before trying to abort again.

View the Status of Message Recovery

You can search for and view the status of failed messages that have been submitted for recovery on the Errors page.

  1. In the navigation pane, click Observability, then Errors.

  2. Submit a failed message for recovery.

  3. From the drop-down list at the top right, select Error Recovery Jobs.


    List options are Errors, Errors by Integration, Errors by Connection, and Error Recovery Jobs.

  4. The Error Recovery Jobs page is displayed for viewing the status of message recovery.

    • Received: Recovery is still in progress.

    • Succeeded: Recovery succeeded.

    • Errored: Recovery failed.


    The Error Recovery Jobs page shows the filter icon and Time Window list. Error Recovery Jobs is displayed in the upper right corner. Below this is the Recovery Jobs table, with columns for Job Id, Created, Received, Succeeded, and Errored.

View Errors By Integration and Connection

You can view errors by integration and connection on the Errors page.

  1. In the navigation pane, click Observability, then Errors.

  2. From the drop-down list at the top, select an option:
    • To view errors by integration, select Errors by integration.
    • To view errors by connection, select Errors by connection.

    List options are Errors, Errors by integration, Errors by connection, and Error recovery jobs.

  3. If you selected Errors by integration or Errors by connection, click Filter Filter icon to show errors alphabetically by name or by error count in descending order.
  4. Click the error count for an integration or connection to invoke the Errors page and view all errored-out instances for the given integration or connection.
  5. Hover over an integration:

    • Click RetryRetry icon to resubmit errors.

    • Click AbortAbort icon to discard errors.

View the Business Identifiers Used in Failed Integration Instances

You can view the business identifiers used in failed integration instances.

  1. In the navigation pane, click Observability, then Errors.
  2. Click the business identifier of the failed integration instance.

    The fileName: invoke_2000.csv business identifier is being clicked.

    The integration instance and the Activity Stream panel are displayed.

  3. Click Business Identifiers Business identifiers icon above the activity stream to display all the defined business identifiers and values for the integration.

    Business Identifiers dialog with Business Identifiers (which is selected) and Configuration columns.

  4. Click Configuration.
  5. Click Actions Actions icon to show the input sources for the business identifiers.

    The Input Sources section is displayed on the left. This section includes the Sources tree for business identifiers. To the right is the content for the Configuration tab. The primary business identifier name and value are displayed. The clear icon and switch to developer view icon are displayed to the right of the Business Identifier field.

See Assign Business Identifiers and Track Integration Instances.