exa-Nico
Community Manager
Community Manager

Table of Contents

Scope

When executing a query, you might receive an internal server error. This article will show you what information you need to investigate it.

Diagnosis

An Internal Server error has occurred if you receive one of the following error messages:

[40005] Successfully reconnected after internal server error, transaction was rolled back.
[42000] Internal server error. Please report this. Transaction has been rolled back. 

 

Explanation

Internal Server Errors are difficult to determine the exact cause without looking into the logs. The exact cause of the internal server error could be something that is reproducible or not. Since the error message does not state the exact problem, you can try various things to remove the error message, for example:

  • Re-writing the query
  • Restarting the database
  • Re-creating affected objects

These can all be difficult to perform, however, so for these reasons, usually, the best course of action is to prepare logs for Exasol support to investigate. 

Recommendation

To further investigate the cause, please open a support ticket and include the following information:

  • Session ID that got the error
  • SQL text of that session ID
  • If the error is reproducible or not? If so, how? 
  • DDL of the tables and views used in the query so that we can reproduce it. 
  • SQL/Server Logs for the day that it happened

If we need additional information, we will let you know in the ticket. Once we have investigated, we will let you know of any potential workarounds and fixes.

Additional References

 

We're happy to get your experiences and feedback on this article below! 

Version history
Revision #:
1 of 1
Last update:
‎08-04-2021 04:05 PM
Updated by:
 
Contributors