First level issues

D.1.1 First level issues

This topic describes the possible issues that may occur during the basic investigation.

Error Message not shown

If there are any improper calls, check the ERTB_MSGS table of the respective schema to understand the cause of the error.

Query: SELECT * FROM ERTB_MSGS WHERE ERR_CODE=’GCS_AUTH-03’

Figure D-4 Error Code

Setting Log file path

Log generation path needs to be defined in PLATO_LOGGER_PARAM_CONFIG table of PLATO schema.

Query: Select * from PLATO_LOGGER_PARAM_CONFIG;

Figure D-5 PLATO_LOGGER_PARAM_CONFIG

Dynamic log generation issues

For generating dynamic service logs, insert the data to PLATO_DEBUG_USERS table.

Query: Select * from PLATO_DEBUG_USERS;

Figure D-6 Service Logs

Figure D-7 PLATO_DEBUG_USERS

Call is failing in Gateway

If any API call is failing in Gateway, hit the same API endpoint without passing through api-gateway via the postman.

Figure D-8 API Gateway

Note:

Restart the specific services if required.

Exact error through exception log

If there is an exact error through the exception log, log in to WINSCP and check the server logs with NIS credentials.

The path is /scratch/obvam/app_logs/UserLogs.

Figure D-9 Exception Error Log

Logs are not generated

If you are not getting logs, put the loggers across API, hit through postman, and test again.

Figure D-10 Postman

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