I recently upgrade to the Microsoft hive odbc driver version 2.01.05.1006, released 12/8/2016. My code was working with the previous version (1.0) of the driver. Now when running my code I keep getting the following error.
ERROR [HY000] [Microsoft][Hardy] (72) Query execution timeout expired.
I have tried changing the timeout settings for the ODBC driver, but it still times out. Does anybody have any other suggestions?
Related
We use Logi info studio for reporting purposes. we are right now using Logi info version 12.6. prior to this version we were using 14.1 and we had to roll back as we had many issues with it. The problem here was we never roll back the scheduler versio when we roll back the version on logi info studio. we sorted that out by rolling the scheduler version as well. But we are facing errors when we schedule reports. the error pasted above is a generic error and i am havng a hard time why the reports are falling if the version of the scheduler is compatibler with the version on logi infoAny . To make sure the reports do not timeout i increased the timeout time that can be specified in the -settngs file. What i need help on is a guidance to where i should look for an error that is less generic than the one we are gertting or anything that can fix the issue.
I made the version of the scheduler and the version of log info compatible . Also i increased the timeout as the reports that we are running are rather larger reports and i wanted to make sure this reports are not just failling just because it is timing out.
For few days I am getting an issue with SQL Server 2019 Express Installation. When installing SQL Server I get an error and the server won't work. I've tried repairing it but I've got also an error here.
The following error is :
Feature: Database Engine Services
Status: Failed
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84B40002
Error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
Error help link: (Link that doesn't work)
My SQL Server Management Studio 2018 also don't work. I've tried uninstalling and installing SQL Server but it doesn't help. I've even tried uninstalling and installing Windows but nothing to do.
I fixed the issue:
If you run into that error, try creating a Virtual Hard Drive with Disk Manager. Then install SQL Server 2019 on it and it should maybe resolve the problem. If not, read all the comments and check if something helps.
Edit: When you shut down your computer, if you restart it, the virtual disk disappears. You have to mount it again and start the database engine manually. I recommend creating a script that does this for you.
While running hive on windows server 2012 I am getting an error of class cast type. Searched about it but can not find the concrete solution if anyone can help. Sharing the screen shot might help analyzing the situation.
Hadoop & beeline is install and running well but connection to hive can not be done.
I'm establishing an ODBC connection to our AS/400 in an app I'm developing. It simply does a DELETE and then an INSERT. Nothing crazy or complicated. Everything works great on my 64-bit Windows 7 Pro desktop (UPDATE: no longer true) but when I try to run the app on my 32-bit laptop for a presentation, I get the following error:
ERROR [S1C00] [Micro Focus][Rumba Data Access][S1023934]Driver not
capable. SQLSetConnectOption ERROR [IM006] [Microsoft][ODBC Driver
Manager] Driver's SQLSetConnectAttr failed ERROR
[01000][Microsoft][ODBC Driver Manager] The driver doesn't support the
version of ODBC behavior that tha pplication requested (see
SQLSetEnvAttr). ERROR [08004][Micro Focus][RUMBA Data
Access][S1023934]Data source rejected establishment of connection.
APPC Primary RC = Allocation_Error; Secondary RC =
Allocation_Failure_No_Retry.
I'm not sure what's going on. I may have messed something up when setting up the DSN on the 32-bit laptop but it looks exactly the same as what I set up on the 64-bit desktop... Is there something different between the 32-bit and 64-bit versions or is there something else going on?
Thanks!
EDIT: I just tried it on another 64-bit desktop and I got the same error. There must be something wrong with how I'm setting up the DSN since I set it up on my machine months ago and could be forgetting something.
EDIT2: I ran Windows Update on the desktop where everything worked on and now it doesn't work there either. Is it possible a buggy Windows Update could be causing my issues?
EDIT3: I was asked in the comments to enable tracing and see what happens. Skimming through it, here are a few notable messages:
EXIT SQLDriverConnectW with return code -1 (SQL_ERROR)
and:
EXIT SQLGetDiagRecW with return code 100 (SQL_NO_DATA_FOUND)
Everything else looks like it exits with a status of 0 (SQL_SUCCESS)
The issue was resolved by installing this Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package MFC Security Update.
According to Microsoft,
A security issue has been identified leading to a vulnerability in MFC applications that are built with Visual Studio 2005 and ship the Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package.
Why installing a security patch (rather than a bug fix patch) solved this is beyond me...
Using ODBC Administrator, turn on tracing. Try your application and look at the log file for SQL_ATTR_ODBC_VERSION. You should see something like this:
odbct32w fc0-1ad0 ENTER SQLSetEnvAttr
SQLHENV 0x007A1DE0
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 3 <SQL_OV_ODBC3>
SQLINTEGER 0
odbct32w fc0-1ad0 EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 0x007A1DE0
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 3 <SQL_OV_ODBC3>
SQLINTEGER 0
The difference will be that yours is returning SQL_ERROR instead of success. Check what the third parameter is (in my case SQL_OV_ODBC3). Most likely whatever version your application is setting is newer that what your ODBC driver supports. You'll need to refrain from using newer ODBC features or upgrade your driver to something one that supports a higher level of ODBC.
I have some trouble to get impala jdbc driver working with Pentaho Designer.
I got the jdbc driver from cloudera website. After extracting the drivers and put them under lib/jdbc, I set up connection via Generic Database.
The custom connection url is: jdbc:hive2://example.com:21050/;auth=noSasl
The custom driver class name is: org.apache.hive.jdbc.HiveDriver
I tried a simple query like "SELECT count(*) FROM table_1;", and got an error: "ParentException:
java.sql.SQLException: Method not supported"
Any ideas?
Matt from Pentaho submitted pull request to apache repository on github: https://github.com/apache/hive/pull/9
This pull request contains implementation of all needed methods in JDBC driver for Pentaho tools. I fetched his commit, built jar and copied it into libext/JDBC directory instead of jar from Cloudera website. Driver still misses lot of methods, but is able to perform basic operations on Impala.
Pentaho does not support impala in previous versions. If you are using 4.4.2 PDI,you can use it for instaview.
Impala will be officially support in pentaho 5.0 and its already been released.