Description
Troubleshooting ODBC driver issues
Problem
This article guides you through the process of troubleshooting ODBC driver issues. It provides steps to help you eliminate common causes for your problem by verifying that the configuration of your networking is correct.
Symptoms
Symptoms may include the following:
- Cannot connect to the instance
- Error message received during processing
- Instance runs out of memory during processing
- Queried information lost
- Precision errors received
- Connection dropped
Resolution
Determine whether any of the troubleshooting steps below are true for your environment. Each step provides a link to an article that will help you eliminate possible causes and take corrective action as necessary.
- Before you begin the next steps in the troubleshooting path, review the ODBC troubleshooting checklist to eliminate those common causes. For more information, see ODBC Troubleshooting Checklist.
- Verify that your instance is running the latest ODBC version. For more information, see KB0538945: Determining if you have the latest ODBC driver version.
- Verify that the ODBC driver is working correctly by testing smaller queries and excluding 3rd party applications. For more information, see KB0538948: Determining if your ODBC driver is working correctly.
- Determine if the instance has run out of memory due to large result sets. For more information, see KB0538950: Determining if ODBC processing has failed due to low memory.
- Determine if the correct time zone is used during ODBC processing. For more information, see KB0538951: Determining the time zone for ODBC processing.
- Determine if precision errors are causing issues with queries. For more information, see KB0538953: Determining if precision errors are causing issues with ODBC queries and see KB0542327: Resolving Precision Errors in Web Service SUM Functions.
- Determine if field type is causing issues with queries. For more information, see KB0542651: Determining if field type is causing issues with ODBC queries.
- Determine if missing values in queries are causing issues with queries. For more information, see KB0542664: Determining if table fields are missing values in ODBC queries.
- Determine if data in ODBC cannot be viewed due to user role. For more information, see KB0542667: Determining if user is missing query role to view ODBC data.
- Determine if a third party tool is causing issues with ODBC queries. For more information, see KB0542682: Determining if a third party tool is causing issues with ODBC queries.
- Determine if a secondary view is causing issues with ODBC database tables. For more information, see KB0542671: Determining if a secondary view is causing issues with ODBC database tables.
- Determine if custom integration is causing issues with ODBC query. For more information, see KB0542676: Determining if custom integration is causing issues with ODBC queries.
- Determine if an upgrade is required to fix ODBC query issues. For more information, see KB0542680: Determining if an upgrade is needed for ODBC.
- Determine if the client is unable to load the driver due to a large JVM heap size. For more information, see KB0538982: Determining if your client application was unable to load the driver.
- Determine if a parallel query is failing. For more information, see KB0551938: ODBC driver fails to get data or connect when invoking multiple or parallel connections.
If the problem still exists after following these steps, gather as much detail as you can about the problem before contacting Customer Support. Questions to ask yourself before submitting incident include:
- Did you try to connect in different environments (that is, did you try it at work and at home)?
- Did you have any co-workers try it on their machines?
- Did you try different Operating Systems?
- Have you been able to successfully connect in the past?
- If so, when did it stop working and can you think of anything that may have changed?
- Is it possible for you to try on a brand new install machine for testing?
| Note: If your problem still exists after trying the steps in this article: Submit an incident to Customer Support and note this Knowledge Base article ID (KB0538943) in the problem description. For more information, see Submitting an Incident in product documentation. |