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 due to the limitation of Oracle Integration Cloud.
Synchronous Flow Error Handling
As part this error handler the errors are sent back to global fault handler and the respective system via Common Error Handler flow.
Technical Fault
This fault occurs when there is a data mismatch 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 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 business fault occurs in the target system due to invalid data. When this error occurs, the fault is sent back to the respective system as part of immediate response.
Asynchronous Flow Error Handling
Technical Fault
This fault occurs when there is a data mismatch 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 via Common Error Handler flow.
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: Event Outcome
Type of error
Action
Notification Type
Retry
Technical or Remote Fault
 
Example: OUAI object storage is not accessible
• Send FAILURE ackType to DERMS
• Process Stop
Email
Resend message from DERMS
Business Fault
N/A
 
 
 
Integration Process: Enrollment Sync (applies to OIC flows FTP and OS)
Type of error
Action
Notification Type
Retry
Business errors
N/A
 
 
Technical Fault
 
Example: Source FTP or Source Object storage is not accessible
Process Stop
Error Email
Next scheduled run will pick up the files from DACS source content server or manually run the OIC process
Partial processing
 
Example: Network connection issue, OUAI object storage not accessible
Process Stop
Error Email
 
Process Complete Email (includes list of files not transferred
Next scheduled run will pick up the files not transferred from DACS source content server or manually run the OIC process
 
Integration Process: Load Reduction Forecast
Type of error
Action
Notification Type
Retry
Technical Fault
 
Example: OUAI object storage is not accessible
• Send FAILURE ackType to DERMS
• Process Stop
Error Email
Resend message from DERMS
Business Fault
N/A
 
 
 
Integration Process: Enrollment Sync Acknowledgment
Type of error
Action
Notification Type
Retry
Technical or Remote Fault
 
Example: OUAI object storage is not accessible
Process Stop
Error Email
Rerun or schedule the integration process
Business Fault
N/A
 
 
Technical Fault
 
(DACS returns Status 401 or 500)
Process Stop
Email
Integration fix: Rerun or reschedule the integration process
Technical Fault
 
(DACS returns Status 400)
Process Continue
N/A
DACS throws 400 error when a duplicate request is found with syncrequestid. OIC will suppress this kind of error as this is already been sync from Oracle Utilities Analytics Insights to Oracle Utilities Digital Asset Cloud Service
 
Resubmitting the Error Instances in Oracle Integration Cloud
In this integration, the flows initiated by Oracle Utilities Analytics Insights are asynchronous flows. The Resubmit option is available only for asynchronous flows.
To resubmit the error instances in Oracle Integration Cloud:
1. Login to Oracle Utilities Analytics InsightsOracle Integration Cloud.
2. Navigate to Integrations > Monitoring > Errors.
3. Select the integration to resubmit.
4. Click the Resubmit icon.