Application exception -- error message does not contain OceanBase error code

Databases often encounter various exceptions during operation, such as application errors, database connection errors, database permission issues, database resource problems, and network issues. One such scenario is an application exception where the error message does not contain an OceanBase error code. This can make it difficult to determine the relevance to OceanBase Database, leading to unclear troubleshooting directions.

To help you quickly identify the root cause and efficiently resolve such issues, we have summarized a clear and practical troubleshooting process for application exceptions where the error message does not contain an OceanBase error code. This process provides detailed steps to enhance troubleshooting efficiency and minimize business impact, supporting your routine O&M work.

The following figure shows the troubleshooting process for an application that reports an exception and the error message does not contain an OceanBase error code.

Process

When an application exception occurs and the error message does not contain an OceanBase error code, you can follow this process to troubleshoot the issue.

Analyze the error logic on the application side to determine if it is a disconnection exception:

• If no, check if the exception can be reproduced:

  • If yes, use methods such as debugging the program code and network packet capture (e.g., tcpdump) to analyze the cause of the program code error, thereby clarifying the analysis direction.

  • If no, use the existing information and the application's own logic to speculate on the cause of the error, thereby clarifying the analysis direction.

Case studies

References

• Use tcpdump to capture packets