1. Troubleshooting Guide
  2. Troubleshooting Functional Workflows
  3. Log Analysis

4.1 Log Analysis

This topic describes the possible issues to use logs to analyze issues in a transaction using logs.

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.

  1. Press F12 to open the Networks.
  2. Check the error code in the response.

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

Figure 4-2 Error Code


Description of Figure 4-2 follows
Description of "Figure 4-2 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 4-3 PLATO_LOGGER_PARAM_CONFIG


Description of Figure 4-3 follows
Description of "Figure 4-3 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 4-4 Service Logs


Description of Figure 4-4 follows
Description of "Figure 4-4 Service Logs"

Figure 4-5 PLATO_DEBUG_USERS


Description of Figure 4-5 follows
Description of "Figure 4-5 PLATO_DEBUG_USERS"

Logs are not generated

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

Figure 4-6 Postman


Description of Figure 4-6 follows
Description of "Figure 4-6 Postman"

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.

Menu Missing/Functional Activity Issues

403 Error - User Role issues

Make sure that the required Role and User Applications are mapped to the user. Refer Security Management System User Guide to create Role/User.

Dashboard Issues

Dashboard not loading

User access is one of the reasons if you are not able to view the Data in the Dashboard. Make sure that the required Role and User Applications are mapped to the user. Refer Security Management System User Guide to create Role/User.

Improper display of data in the Dashboard
Data not getting published to the Report Schema is the reason for improper display of data in the Dashboard. Follow the below steps to resolve the issue:
  1. Examine the report logs of OBSCF/OBSCFCM for more information.
  2. Restart the Report services or Kafka, if they are down.
  3. Verify that the Currency is maintained correctly.
  4. If there are technical problems, additional analysis is necessary.

Parent topic: Troubleshooting Functional Workflows