Troubleshooting the Technical Accelerator

Integration Errors (across OIC Integrations)

A notification email will be sent by the Oracle EXT_SYS ATP Error Message Handler integration for various errors caught by error scope and caught by the global fault handlers across integrations. The error causes and error resolutions are detailed in the sections below.

For all error scenarios, the err_status column in the configuration table will be Y.
To restart the flow and set the err_status to N after fixing the error, it is required to MANUALLY call the Integration Oracle REST REST Error Flag Reset to restart business event processing.

Integration: Oracle Hospitality ATP Capture BE

Error Cause 1: Invoke (insert business events proc)

Error Resolution:

If ATP is down, contact the sys admin.
If timeout, check if business events are inserted into the ATP table OHIP_OIC_BUSINESS_EVENTS_Q_TAB.

If not inserted, the payload is secured in {FTP_location}.

Note:

To gain access to the FTP location and to host files in the directory, developer privileges must be granted to the user account.

Note:

If a failure occurs: After ATP is up and running, the payload must be manually recovered from the FTP location and the API of the Oracle Hospitality ATP Capture BE integration must be used to add the event data into ATP in sequence. The timestamp associated with the insert of the backed-up data must be maintained in the server location.

Error Cause 2: Invoke (proc for getting data from config table)

Error Resolution: If ATP is down, contact the sys admin.

Error Cause 3: Invoke (entry logic + loop for each external system)

Error Resolution: For that {EXTERNAL_SYSTEM}, manually change call_parent_int flag to 'Y' in the configuration table: OHIP_OIC_EXT_SYS_CONFIG_TAB

Error Cause 4: Invoke (Orchestration) — nested scope

Error Resolution: Integration not active, please activate.

Integration: Oracle ATP REST Orchestration

Error Cause 1: Invoke (proc to retrieve group_id and change status to 'L')

Error Resolution:

If ATP is down, contact the sys admin.
If events have been locked for {external_system}, the BE status OHIP_OIC_BUSINESS_EVENTS_Q_TAB must be reset to 'N' and call_parent_int flag in the config table: OHIP_OIC_EXT_SYS_CONFIG_TAB to 'Y'.

Error Cause 2: Invoke (producer integration)

Error Resolution: Integration not active, please activate.

Integration: Oracle REST ATP Producer

Error Cause 1: Invoke (proc for change status to P)

Error Resolution:

If ATP is down, contact the sys admin.
If events have been marked 'P' for \{external_system\}, the BE status\[Q table\] must be reset to N and call_parent_int flag\[config table\] to Y.

Error Cause 2: Invoke (dispatcher integration)

Error Resolution: Integration not active, please activate.

Integration: Oracle ATP REST Dispatcher

Error Cause 1: Invoke (proc to fetch aggregated events for a group in a CLOB format (5 mb limit))

Error Resolution:

ATP is down, contact sys admin.
If timeout, the BE status\[Q table\] must be reset to N and call_parent_int flag\[config table\] to Y.

Error Cause 2: Invoke (external system integration - consumer)

Error Resolution:

The endpoint for {EXTERNAL_SYSTEM} has not been configured in the OHIP_OIC_EXT_SYS_CONFIG_TAB. Please update the ext_sys_endpoint and set call_parent_int flag in this config table to 'Y' to process.
If the endpoint is configured for {EXTERNAL_SYSTEM}, then ensure integration is activated.
Please check if there is a mismatch in the payload that is being accepted in the target system.

Integration: Oracle EXT_SYS ATP Dispatcher Log Status Update

Error Cause 1: Invoke (proc for change status to C)

Error Resolution:

If ATP is down, contact the sys admin.
If events have been marked 'C' for {external_system} and call_parent_int flag in the config table OHIP_OIC_EXT_SYS_CONFIG_TAB to be set to 'Y'.
If ATP call failed, update the status to 'C' manually, and the flag should be reset to Y.

Error Cause 2: Group of invokes (proc for exit logic, proc for integration status, int for calling orchestration)

Error Resolution:

If ATP is down, contact the sys admin.
If any of the invokes fail, reset call_parent_int to 'Y' manually in OHIP_OIC_EXT_SYS_CONFIG_TAB.
Nested scope handler — Used for calling orchestration.
Integration is not active, please activate.

Manually Call Integration: Oracle REST REST Error Flag Reset

Manually call this integration after the error is fixed to restart the processing of business events. This Integration calls the procedure OHIP_OIC_RESET_DATA_SP that resets the error flags after the error is resolved. It subsequently calls the Capture Business Events Integration Flow to continue the processing of business events.

This integration must be called manually each time an error occurs by logging into the OIC instance with the Service.invoker role and passing the parameter of the external system id for which the error was fixed.

OR

Alternately, the following Rest endpoint URL can be called via a rest client of your choice, such as postman, or by using a curl command with the payload mentioning the errored external system id with the Service.invoker access privilege.

Rest Endpoint: https://oichostname:port/ic/api/integration/v1/flows/rest/ORCL-TA-REST_REST_ERROR_FLAG_RES/1.0/Hospitality/ResetData.

Payload(JSON): 
{   
  "External_System_id": "Your_External_System_id_for_which_error_resolved"
}