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

During database operation, various exceptions may occur, such as application errors, database connection errors, database privilege issues, database resource limitations, and network problems. One such exception is an application exception where the error message does not contain an OceanBase error code. This makes 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 this issue, 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 step-by-step guidance to enhance troubleshooting efficiency and minimize business impact, supporting your daily O&M work.

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

Process

When an application reports an exception but the error message does not contain an OceanBase error code, you can troubleshoot the issue using the following process.

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

• If yes, refer to the knowledge base for troubleshooting.

• 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 and thus identify the analysis direction.

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

Case studies

References

• Use tcpdump to capture packets

• TCP communication between OceanBase Database and applications