17.2.1 Handling errors
In the first part of the troubleshooting process, you identify the source of the error. After identifying the source, you then take the appropriate action to resolve the error. The following figure explains the process of identifying the source of an error.
After identifying the source of the error based on this flow chart, use the following table to find out what action to take.
No. |
State |
Handling procedure |
---|---|---|
1 |
State A An error occurred in an application or the driver manager. |
Perform the following steps:
|
2 |
State B An error occurred in the driver manager. |
Same as the handling procedure for No.1. |
3 |
State C An error or warning occurred in the ODBC driver. |
Perform the following steps:
|
4 |
State D An error or warning occurred in the ODBC driver. |
Perform the following steps:
|
5 |
State E The connection with the HADB server has not been established. |
The HADB server might not be accessible. You need to identify the part of the access route where access fails. First, perform the following steps:
If the error still occurs despite all these settings being correct, enable the output of ODBC traces, HADB ODBC driver trace information, and SQL trace information. Then, reproduce the error and analyze the information output in each trace. If there is no error message and nothing is output in the BI tool or ODBC module, the issue might be with the BI tool or ODBC module. |
6 |
State F An error occurred in the HADB client. |
Check the error cause code and investigate the cause of the error. For details about the error cause code, see 19.8 Return values of the CLI functions. Potential causes include a path being specified incorrectly in an environment variable or the client definition, or not having the required privileges. |
7 |
State G An error or warning occurred in the HADB server or HADB client. |
Check the message output by HADB, and investigate the cause of the error or warning. |
8 |
State H The connection with the HADB server has been established. |
The HADB server is accessible. Perform troubleshooting by analyzing the SQL statements and the messages output to the message log file. If you want to acquire detailed information, enable the output of ODBC traces, HADB ODBC driver trace information, and SQL trace information. Then, reproduce the error and analyze the information output in each trace. If there is no error message and nothing is output in the BI tool or ODBC module, the issue might be with the BI tool or ODBC module. |
The following figure shows the flow of processing when using the HADB ODBC driver to access the HADB server from a BI tool or ODBC module.
If you resolve the error and a different error then occurs, begin the troubleshooting process again starting from identification of the source.