Error Handling
This section provides information about the different ways used to handle errors in the integration and also resubmitting the instances after rectifying the errors.
Error Handling Ways
In this integration, the errors are handled in different ways in Oracle Integration Cloud.
Synchronous Flow Error Handling
As part of this error handler the errors are sent back to the respective source system in the same flow.
Technical Fault
This fault occurs when there is a data mismatch in DVM or any Xpath related error. On this error, the flow immediately goes to global fault handler and the fault is sent back to the respective system.
Remote Fault
This fault occurs when there is a connectivity issue. For example, the target system is down. When this error occurs the flow immediately goes to global fault handler and the fault is sent back to the respective system.
Business Fault
This fault occurs only when the error occurs in the target system due to invalid data. When this error occurs the fault is thrown to the respective source system.
Asynchronous Flow Error Handling
Technical Fault
This fault occurs when there is a data mismatch in DVM or any Xpath related error. When this error occurs, the flow immediately goes to global fault handler and an optional email to the respective user is sent.
Remote Fault
This fault occurs when the target system is down. When this error occurs, the flow immediately goes to global fault handler and an optional email is sent to the respective user.
Business Fault
This fault occurs only when the business fault occurs in the target system due to invalid data. When this error occurs the flow immediately goes to global fault handler and an optional email is sent to the respective user.
Summary of Integration Error Handling
Integration Process: Oracle Utilities OCI Stream linkChannel
Type of Error
Action
Notification Type
Retry
Source Stream is down
The process is not invoked.
No Notification
Once Source Stream is up, the poller picks up the messages on the stream run.
Technical or Remote (CCB or Target Stream is unreachable)
Message is published to Source Stream (Rolling back the messages)
Email (optional)
Poller picks up the messages on the next run.
 
Note: Inactivate this integration process until all applications (CCB, Stream) are up to avoid the continuous reprocessing of messages that would fail.
 
Integration Process: Oracle Utilities NMS OCI Stream Notif Upload
Type of Error
Action
Notification Type
Retry
NMS DB down/unavailable
The process is not invoked.
No Notification
Once DB connection is successful, the poller picks up the XML records from MYC_CSS_PARAM_VIO_TEXT with CSS_NOTIFIED='N'.
Technical or Remote (Source OCI Stream is unreachable)
NMS table MYC_CSS_PARAM_VIO_TEXT is updated with CSS_NOTIFIED='E'.
Email (optional)
Retry/Resubmission should be performed at NMS DB level. Retry by marking the CSS_NOTIFIED flag to 'N' from 'E' for the errored violation id. 'E' means the transaction has been marked as faulted and its retriable.
 
Integration Process: Oracle Utilities OCI Stream Responsys Notif Send
Type of Error
Action
Notification Type
Retry
Not 401 or 500 error status when Responsys API is invoked
Error messages from each invoke in a batch for a particular Oracle Responsys instance, along with account ID, template name and delivery channel is collected in a collection.
A separate email is sent for errors in each Oracle Responsys instance.
These notification messages cannot be recovered.
Error status that is 500 or 401 when Responsys API is invoked
Error messages from each invoke in a batch for a particular Oracle Responsys instance, along with account ID, template name and delivery channel is collected in a collection.
A separate email is sent with error collection of each Responsys instance.
These notification messages are republished back to TargetNotificationStream, until the issue is resolved.
Note: If the resolution takes a while, inactivate the process to avoid receiving emails and republishing.
Technical or Remote (TargetNotificationStream OCI Stream is unreachable)
During polling, if the OCI Stream is unreachable, the OIC instance is not instantiated.
Email (optional)
Poller will pick up the messages on next try.
Invalid delivery channel or Oracle Responsys instance
Error messages from each invoke in a batch for a particular Oracle Responsys instance, along with account ID, template name and delivery channel is collected in a collection.
An email is sent with the error collection for each batch.
These notification messages cannot be recovered.
 
Integration Process: Oracle Utilities CCB OCI Stream Notif Upload
Type of Error
Action
Notification Type
Retry
Technical or Remote (Target Stream is unreachable)
• Fault is logged in the OIC Instance.
• Fault is rethrown to Global handler.
No Notification
CCB must resend the notification outbound message to OIC.
Any Global
Fault is rethrown back to CCB.
Email (Optional)
CCB must resend the notification outbound message to OIC.
Resubmitting the Error Instances in Oracle Integration Cloud
In this integration, the flows initiated by Oracle Utilities Network Management System are asynchronous flows, and the resubmit option is available only for asynchronous flows.
To resubmit the error instances in Oracle Integration Cloud:
1. Login to Oracle Integration Cloud.
2. Navigate to Integrations > Monitoring > Errors.
3. Select the integration to resubmit.
4. Click the Resubmit icon.
Note: Retry or Resubmission error instance from the OIC Monitoring page may not be applicable for the Oracle Utilities NMS OCI Stream Notif Upload integration flow. Refer to the Summary of Integration Error Handling section on how to retry/resubmitted errored transactions/record.