Application exception - error message does not contain OceanBase error code

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

To help you quickly identify the root cause of such issues and efficiently resolve them, this topic summarizes a clear and practical troubleshooting process for application exceptions where the error message does not contain an OceanBase error code. The 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 but the error message does not contain an OceanBase error code.

Process

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

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

• If yes, search for relevant information in Knowledge Base and refer to the troubleshooting process.

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

  • If yes, use methods such as debugging the program code and network packet capture (for example, using tcpdump) to analyze the program code and determine the cause of the error, thereby clarifying the troubleshooting direction.

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

Case studies

References

• Use tcpdump to capture packets