1. Troubleshooting Guide
  2. Troubleshooting Application Workflows
  3. Oracle Banking Electronic Data Exchange for Corporates – Subdomains List
  4. Call is Failing in OBRH

D.1.2 Call is Failing in OBRH

This topic provides the troubleshooting information about the call is Failing in Oracle Banking Routing Hub (OBRH).

If any call is failing in Oracle Banking Routing Hub, open the CMC_RH_AUDIT_EVENT_LOG for getting Gateway response (SUCCESS or FAILED).

Select the following query to verify results.

Query: select * from CMC_RH_AUDIT_EVENT_LOG

Figure D-11 CMC_RH_AUDIT_EVENT_LOG


Description of Figure D-11 follows
Description of "Figure D-11 CMC_RH_AUDIT_EVENT_LOG"

Code Error in GCS Side

If there is any error in GCS side codes, use java de-complier to debug the error.

404 Error

The possible causes for 404 error are as follows:

  • Check service is not running on Eureka.
  • Check service is not deployed in WebLogic.

500 Internal Error

The possible causes for 500 Internal error are as follows:
  • Issue with Plato entries
  • Issue with Eureka
  • Issue with any peace of code

The server-side debugging is needed for the above-mentioned issues, if it is not captured in logs.

Parent topic: Oracle Banking Electronic Data Exchange for Corporates – Subdomains List