Query timeout alternative

Hi:
I am using VB6.0 to call an Oracle8.1.7 Java package function using OraOLEDB. Everything works fine with the exception that sometimes the stored procedure call takes too much time and I would like to kill the query. The problem is that OraOLE does not support the query timeout property. Does anyone know how to override this problem ? Is there some oracle database provider that supports both query timeout and calling java packages ?
Greetings

No such option.

Similar Messages

Unable to access the data from Data Management Gateway: Query timeout expired

Hi,
Since 2-3 days the data refresh is failing on our PowerBI site. I checked below:
1. The gateway is in running status.
2. Data source is also in ready status and test connection worked fine too.
3. Below is the error in System Health -
Failed to refresh the data source. An internal service error has occurred. Retry the operation at a later time. If the problem persists, contact Microsoft support for further assistance.
Error code: 4025
4. Below is the error in Event Viewer.
Unable to access the data from Data Management Gateway: Query timeout expired. Please check 1) whether the data source is available 2) whether the gateway on-premises service is running using Windows Event Logs.
5. This is the correlational id for latest refresh failure
is
f9030dd8-af4c-4225-8674-50ce85a770d0
6.
Refresh History error is –
Errors in the high-level relational engine. The following exception occurred while the managed IDataReader interface was being used: The operation has timed out. Errors in the high-level relational engine. The following exception occurred while the
managed IDataReader interface was being used: Query timeout expired.
Any idea what could have went wrong suddenly, everything was working fine from last 1 month.
Thanks,
Richa

Never mind, figured out there was a lock on SQL table which caused all the problems. Once I released the lock it PowerPivot refresh started working fine.
Thanks.

Powerpivot Report 2010 - OLE DB or ODBC error: Query timeout expired; HYT00

0
I have report already developed by someone in powerpivot 2010 and deployed to sharepoint in powerpivot gallery library. The data source for this report is SQL Server 2008 r2. I have set the refresh options in sharepoint to run after business hours during
week end. When I check the refresh history it shows this error message "OLE DB or ODBC error: Query timeout expired; HYT00. An error occurred while processing the 'xxx' table. The current operation was cancelled because another operation in the
transaction failed..
I have tried to run the "Also refresh as soon as possible " just to check but same error message is shown.
This is the detailed error message details:
03/02/2014 21:06:55 03/02/2014 22:08:15 01:01:20 Failed
OLE DB or ODBC error: Query timeout expired; HYT00. An error occurred while processing the 'xxx' table. The current operation was cancelled because another operation in the transaction failed
Could anyone guide me on this issue? Truly appreciate your help in advance.

Hi asritha,
I would suggest you take a look at the following articles regarding how to configure PowerPivot data refresh in SharePoint Server:
Configure and Use Stored Credentials for PowerPivot Data Refresh:
http://technet.microsoft.com/en-us/library/ee210671(v=sql.105).aspx
Configure and Use the PowerPivot Unattended Data Refresh Account:
http://technet.microsoft.com/en-us/library/ff773327(v=sql.105).aspx
Note: Please ensure that the account have sufficient permission access to your data source.
In addition, please elaborate your PowerPivot data soure with more detail. If you are using SSAS cube, please try to increase "ExternalConnectionTimeout" property default value to see if this helps. Here is the similar thread for your reference,
please see:
http://social.technet.microsoft.com/Forums/en-US/35b26c06-9e6d-41e5-ae44-bfb1233510ac/ssas2008-ole-db-error-ole-db-or-odbc-error-query-timeout-expired-hyt00?forum=sqldatamining
Regards,
Elvis Long
TechNet Community Support

Query Timeout on stored procedure executed from Access 2010

I am trying to delete old jobs from a SQL 2008 R2 database. I created a stored procedure on the server that deletes all Jobs over 1 year old. The delete can take several minutes to run as it deletes record on several related tables. I am getting a error
"2147217871 - [Microsoft][ODBC SQL Server Driver]Query timeout expired". The query runs fine on the Server. I have tried setting Client timeout to 300 sec but it times out way before 5 min. I am not sure what else I
can do to fix this problem. I am hoping someone has seen this and figured out a fix.
Here is there code
Public Sub Cleanup_Database()
On Error GoTo CleanUp_Err
    Dim cmd As ADODB.Command
    Set cmd = New ADODB.Command
    ODBC_conn = "ODBC;Description=testbox2;DRIVER=SQL Server;" & _
                "SERVER=O2GMSAPPTEST\SQL122DEVL;Trusted_Connection=Yes;" & _
                "APP=Microsoft Office 2010;DATABASE=IMB_TraceData;StatsLog_On=Yes"
    cmd.ActiveConnection = ODBC_conn
    cmd.CommandType = adCmdStoredProc
    cmd.CommandText = "DataBase_Cleanup"
    cmd.Execute
CleanUp_Err:
    Dim i As Long
    Dim str As String
    str = ""
    For i = 0 To Errors.Count - 1
        str = str & Errors(i).Number & "-" & Errors(i).Description & " " & vbNewLine
    Next i
    If str = "" Then
        str = Err.Number & " - " & Err.Description
    End If
    MsgBox str, , "Trace Update"
End Sub


You didn't say how you were setting the client timeout, but this has worked for me in an adp.
'Temporarily increase query timeout, which is an application-wide setting
'CurrentProject.Connection.CommandTimeout = 60 'Too late to change this setting- no effect
Const cstrTimeoutOptionName As String = "OLE/DDE Timeout (Sec)"
Const clngTimeoutSecondsForQuery As Long = 300
strQueryTimeOutOriginal = Application.GetOption(OptionName:=cstrTimeoutOptionName)
Application.SetOption cstrTimeoutOptionName, CStr(clngTimeoutSecondsForQuery)
Paul

Jdbc driver creates new thread for each statement with a query timeout set

I am profiling a web application that is using the Microsoft JDBC driver, version 1.1 to connect to a sql server 2005 database. Each java.sql.Statement that is created, within the application, gets a query timeout value set on it ( statement.setQueryTimeout(...) ).
I have discovered that the JDBC driver creates a new thread to monitor each Statement and the query timeout value. When the application is under load these threads are getting created faster then they are being destroyed and I am concerned that this will cause a performance problem in production.
One option I have is to remove the query timeout value and the monitor threads will not be created, another is to change JDBC drivers.
I'm curious is there any way to control this behavior so that these threads are not created or are managed more efficiently. Is there a workaround that anyone is aware of? Is this considered a bug?
I have found a similar bug here for the 2000 driver:
http://support.microsoft.com/default.aspx/kb/894552
Cheers

Hi,
Thank you for using the Microsoft SQL Server JDBC driver. You are correct that a new thread is started to monitor the query timeout when a statement is executed. This is a potential performance issue that we may look at addressing in the upcoming v1.2 release. The current behavior is not configurable. The only workaround with the v1.1 driver is to limit your use of query timeouts to only those statements which you reasonably might expect to actually time out.
We do take customer feedback very seriously, so if anyone else is concerned about this particular issue, please chime in and we will be able to give it appropriate weight.
--David Olix [MSFT]

Error [hyt00] [microsoft][odbc sql server driver] query timeout expired

I have the below network setup:-
1. Its a simple network at my father's office at a small town called Ichalkaranji (District - Kolhapur, Maharashtra).
2. We are using private network range 192.168.1.xxx with two Windows Server 2003 Enterprise Edition with SP2 licensed copies and 15 local Windows 7 clients who are only using Server A.
3. The network is having a TP-Link Braodband Router Connected to internet with the IP 192.168.1.1.
4. Both there Windows Server 2003 Enterprise Edition with SP2 are running separate SQL Server 2005 Express with Advanced Services, you can treat them as Server A (Problematic Server with IP of 192.168.1.2)
and Server B (this is not having any issue with IP of 192.168.1.3).
5. Server A is also being used by 6 Remote users from our Kolkata office using DDNS facility through the NO IP client software which installed separately on both the servers. Kolkata remote users
do not use OR access the Server B.
6. Server B is being used by only 2 Remote users from our Erode office (Under Salem District, Tamilnadu) using DDNS facility through the NO IP client software which installed separately on both
the servers. Erode remote users do not use OR access the Server A.
7. The front end application which running separately on both the servers have been developed in VB by a local vendor at Ichalkaranji (District - Kolhapur, Maharashtra).
8. Both Servers are having the same database structure in terms of design and tables format. Only difference is that both the servers are being used separately.
9. This error OR problem is only related to Server A, where on the clients we get the message "error [hyt00] [microsoft][odbc sql server driver] query timeout expired" every now and then.
10. We have to frequently reboot the server whenever we get this message on the client machines. May be after rebooting every thing works perfectly for 2 hours / 5 Hours / may be one full day but
the the error will come back for sure.
11. Current Database back up size on Server A is around 35 GB and take around 1 hour 15 minutes daily to take the back up.
12. Current Database back up size on Server B is around 3 GB and take around 5 to 10 minutes daily to take the back up.
13. One thing I have noticed is that when ever we reboot Server A, for some time sqlsrvr.exe file will show memory usage of 200 to 300 MBs but it will start using slowly, what i understand is that
this is the way SQL Server works.
14. Both the Servers are also running Quick heal Antivirus Server Edition separate licensed copies also.
15. Server B is also running Tally ERP 9 Licenses copy which is being used locally by 15 users of Ichalkaranji (District - Kolhapur, Maharashtra) same users
Can any one help to resolve this issue. Any help will be highly appreciated.

The error message "query timeout expired" occurs, because by default many APIs, including ODBC only waits for 30 seconds for SQL Server to send any output. If no data has been seen for this period of time, they tell SQL Server to cancel execution
and return this error to the caller.
This timeout could be seen as a token that the query is taking too long time to execute and this needs to be fixed. But it can also be a pain in the rear parts, if you are content with a report taking five minutes, because you only run it once a day.
The simplest way to get rid of the error is to set the timeout to zero, which means "wait forever". This is something your vendor would have to do. This may, however, not resolve the problem, as the users may just find that the application is hanging.
To wit, there are two reasons why the query takes more than 30 seconds to complete. One is that there is simply that much work to do. This can be reduced by adding indexes or by doing other tuning, if the execution time is not acceptable. The other possibility
is blocking. That is, there is a process blocking this query from completing. This is much more likely to require attention.
It is not clear to me, whether the vendor has developed the database part as well. In this case, you should probably call the vendor's support desk to have them to sort this out.
Finally, I am little puzzled. You say that you are using Express Edition, but one of the databases is 35 GB in size. 35 GB is far above the limit for Express Edition.
Erland Sommarskog, SQL Server MVP, [email protected]

Can we set the query timeout value in a global control place?

hi everyone,
We use the FullTextSqlQuery class to do query stuff, but we have the query timeout issue, the query sometimes timeout, sometimes is normal. I know there is a property from Query class called Timeout, and the default
time is 15 seconds, but we have lots of code involving FullTextSqlQuery.
I want to know is there a gloabal place like the web.config or regedit or somewhere to set the timeout value?
Thanks

Did you ever get an answer? I'm in the same boat...the only way I can seem to not charge tax to my wholesale clients is to set "tax never applies". But I got over 300 products...how can I do it "en mass"???
Anybody??
I tried creating a special tax code at 0% but that didn't do it either.
thanks in advance,
Scot.

JDBC & setQueryTimeout - or is there another way to set query timeout?

I am trying to set query timeout for TimesTen using jdbc library. But it seems like TimesTen jdbc library does not support setQueryTimeOut. Is there a way to set it without having to set it statically in the DNS?
I tried to set the SqlQueryTimeout in the connection string but it doesn't work either:
     Connection connection = DriverManager.getConnection(
     "jdbc:timesten:client:TTC_SERVER=bleh;TCP_PORT=17013;TTC_Server_DSN=blah;TTC_Timeout=0;SqlQueryTimeout=5;");
Thanks for your help!

Thanks for replying. I don't know have good knowledge on Cache Connect. I will have to read on that first.
It seems like TimesTen does not support jdbc setQueryTimeout. Calling this method on TimesTen jdbc library will return false: supportsQueryTimeout().
I created a test class for testing the SqlQueryTimeout. I set the TTC_Timeout to 400 seconds and SqlQueryTimeOut to 5 seconds. So after 5 seconds it should time out.
The way I test it is by putting a break point before executing the query, do a route add DBServer to an un-connectible gateway to simulate the network delay/connection problem and then continue after I added the route.
After executing the query, instead of timing out after 5 second, it will wait for a few minutes before timing out.
The code for testing the timeout is as follow:
public class TTTest {
     public static void main(String[] args) throws ClassNotFoundException {
     Class.forName("com.timesten.jdbc.TimesTenDriver");
     try {
     Connection connection = DriverManager.getConnection(
     "jdbc:timesten:client:TTC_SERVER=server;TCP_PORT=17013;TTC_Server_DSN=server_dns;"
     + "TTC_Timeout=400;SqlQueryTimeout=5;");
     System.out.println(connection.getClass().getName());
     Statement stmt = connection.createStatement();
     //com.timesten.jdbc.JdbcOdbcStatement stmt = (JdbcOdbcStatement)connection.createStatement();
     System.out.println(stmt.getClass().getName());
     System.out.println("Query started " + new Date());
// Pause here, put a route add and continue
     ResultSet rs = stmt.executeQuery("select count(*) from mse");
     rs.next();
     System.out.println("there are " + rs.getInt(1) + " rows");
     rs.close();
     stmt.close();
     connection.close();
     } catch (Exception x) {
     x.printStackTrace(System.err);
     System.err.println(new Date());
}

Anomaly when query timeout in Data buffer

Hello experts
I'm using MII12.2 and query buffered (allow buffering flag) on a database with several tables locks.
When I get a query timeout (LastErrorMessage of the query is "Response timed out, request terminated"), the query is not queued in the buffer.
Just if I send the query to the buffer setting a wrong used id in the dataserver, then the manager works properly (when I restore the used id, the query completes its logic when the lock is released)
If anybody wants to replicate the enviroment, the query for table lock in SQL Server is
     BEGIN TRANSACTION
     SELECT * FROM [your table name] WITH (TABLOCKX, HOLDLOCK);
     WAITFOR DELAY '00:10:00'
     ROLLBACK TRANSACTION
You have to run it in SQL Manager, not in MII
Sequence:
- Create in MII a generic query with SELECT * FROM [your table name], and enable "allow buffering"
- Call it in a transaction (if you want, with exception handler)
- Run the lock query in SQL Server
- Run the transaction (while the table is locked by SQL Server query) and wait transaction/query error
- Check data buffer: the MII query is not buffered
Is it normal?
Is there any patch?
Thanks
Regards
Fabio

Hi Fabio,
I think the query does not gets buffered because no communication error happened.
MII would buffer an external call if there is a communication error.
But in your case the communication happened fine and the DB did not gave the response and thus time out happened. One more scenario of this type is if we write a query with syntax error. Here also the communication will happen with the DB but the DB will give the error thus MII will not buffer the query.
Regards,
Rohit Negi.

Setting query timeout in TopLink 10g

The 10g version of OAAM uses TopLink 10g Release 3 (10.1.3.1.0) (Build 061004) and Oracle JDBC Driver 10.2.0.2.0. We are not using TopLink Essentials. I'm trying to make it so that our queries will timeout and throw an exception if they take too long. I have tried several things, but haven't had any luck so far. I have tried each of the following:
* Adding <property name="javax.persistence.query.timeout" value="1"/> to the <login> element in sessions.xml.
* Setting the query policy in my descriptors like this:
<opm:querying xsi:type="toplink:query-policy">
<opm:timeout>1</opm:timeout>
</opm:querying>
* Calling DatabaseQuery.setQueryTimeout(1).
* Calling setProperty("javax.persistence.query.timeout") on the database login, server session, client session, and unit of work.
In each case, I tried to update a locked table, and the application simply hung until I unlocked the table. I also tried executing select queries that take around 15 seconds to run, and those completed normally. I want to make the application throw a database exception instead. How can I make this work?
I ran this test to eliminate the JDBC driver as a suspect:
java.util.Properties props = new java.util.Properties();
Class.forName("oracle.jdbc.driver.OracleDriver");
props.setProperty("user", "teng_oaam");
props.setProperty("password", "******");
java.sql.Connection conn = java.sql.DriverManager.getConnection("jdbc:oracle:thin:@******:1521:brsadb", props);
System.out.println(conn.getMetaData().getDriverName() + " " +conn.getMetaData().getDriverVersion());
java.sql.Statement stmt = conn.createStatement();
stmt.setQueryTimeout(1);
System.out.println(stmt.getClass());
System.out.println(new java.util.Date());
try {
// this query takes about 20 seconds to execute
java.sql.ResultSet rs = stmt.executeQuery("select * from vcrypt_ip_location_map where from_ip_addr<=1160157297 and to_ip_addr>=1160157297");
} catch (Exception ex) {
ex.printStackTrace();
System.out.println(new
java.util.Date());
The query fails with ORA-01013, which is what I expect to happen, so the problem is not in my JDBC driver.
Thanks,
Josh Davis

public static Integer executeUpdate(TopLinkDBMgr topLinkDBMgr, BharosaDBQuery dbQuery) throws BharosaDBException {
DataModifyQuery query = null;
List args = Collections.EMPTY_LIST;
long startTime = System.currentTimeMillis();
try {
AbstractSession session = (AbstractSession) topLinkDBMgr.beginSession(); +// creates a ClientSession and calls session.beginTransaction()+
query = new DataModifyQuery();
query.setCall(new SQLCall(dbQuery.getQueryString().replace(':', '#'))); +// we still have some SQL queries we haven't changed since we used Hibernate+
Vector arguments = bindArgumentsForRawSql(dbQuery, query);
args = arguments;
query.setQueryTimeout(1);
Object result = session.executeQuery(query, arguments);
return converter.toInteger(result);
} catch (BharosaDBException ex) {
throw ex;
} catch (Exception e) {
throw BharosaDBException.createDBObjectQueryException(dbQuery.getQueryString(), e);
} finally {
topLinkDBMgr.endSession(); +// calls session.endTransaction() on the ClientSession+
long time = System.currentTimeMillis() - startTime;
Level level = getLogLevelForElapsedTime(time);
if (logger.isEnabledFor(level)) {
String message = buildPerformanceMessage(query, args);
logPerformance(level, time, message);
For my test, I lock a table in SQL*Plus, and there is a background process that uses this method to update that table. That process hangs until I release the lock in SQL*PLus.
This is a corner case, though. Most of our updates are done with the UnitOfWork class, so I need to be able to make the queries that it generates time out also.
Thanks,
Josh

Query timeout in ADF BC

Hi all,
I had a quick look, but couldn't find the answer: is there any way to set a query timeout for ADF Business Components queries, such that if a VO query takes more than x seconds, we will time out?
John

Hi all,
Upon further research - the query timeout is actually not what was causing the problem in the UI... I thought I'd summarize my findings here (I have a VO with a query that will take hours to run and I programatically set the timeout to 1 millisecond):
1). The Business Components Browser correctly reports "long-running query cancelled" exception when I access the VO
2). (this was the cause of the original "ADF Faces app says 'loading' forever) - The way that setQueryTimeout works on the VO is *not* by setting the query timeout on the underlying JDBC statement; it works by creating a monitor thread which will wake up and issue "cancelQuery" on the VO if it takes too long to execute. That causes a problem in the getEstimatedRowCount() call, which takes a long long time. If the af:table is set for lazy delivey, this delay happens on a PPR request, and thus the "loading" message is there forever.
3). If I over-ride getEstimatedRowCount to return 1000, the query timeout happens (in executeQueryForCollection) and displays a stack trace. If the af:table is lazy-loaded, the stack trace comes during PPR request, if af:table is immedate-loading, the stack trace happens during the initial request. In neither case is the query timeout exception displayed in the UI.
It seems to me that it would be a great benefit to use the setQueryTimeout method on the JDBC statement so that if the query timeout is set on the VO, then both executing the VO and calling getEstimatedRowCount would timeout. It also seems to me that it would be very beneficial for the timeout exception to be captured and displayed in the UI.
John
<bump/>

Query Timeout

Hi There !
We are using straight JDBC to talk to Oracle (no SQLJ or anything like that). I am wandering if there is a way in standard (or Oracle specific) JDBC to set default Query Timeout, so one does not need to call setQueryTimeout() on every Statement.
This is somewhat similar to what SQLJ Connection Context can do.
I would appreciate some help
Thank you

No such option.

Query timeout on 10g thin driver

I'm using the Statement.setQueryTimeout(...) method, but it doesn't seem to work when the server is shutdown.
I do the following:
1) create the statement and set the query timeout to 30 seconds
2) run a query that gets stuck waiting for a lock (ie select for update...)
Now, if I let it run normally I do see the following exception:
ORA-01013: user requested cancel of current operation
However, if I run the same query, but shutdown the database server before releasing the lock I see the client application hang indefinitely. The 30 second timeout never occurs.
If I take a thread dump I see my client is stuck on a socket read, which will never come because the db server was shutdown.
Why isn't the jdbc driver honoring the 30 second timeout if it can't communicate with the server? Does this mean that the timeout is actually controlled on the server-side?
any info is appreciated,
Brett

You didn't say how you were setting the client timeout, but this has worked for me in an adp.
'Temporarily increase query timeout, which is an application-wide setting
'CurrentProject.Connection.CommandTimeout = 60 'Too late to change this setting- no effect
Const cstrTimeoutOptionName As String = "OLE/DDE Timeout (Sec)"
Const clngTimeoutSecondsForQuery As Long = 300
strQueryTimeOutOriginal = Application.GetOption(OptionName:=cstrTimeoutOptionName)
Application.SetOption cstrTimeoutOptionName, CStr(clngTimeoutSecondsForQuery)
Paul

Setting Query timeout

Is there anyway to set the ODBC query timeout value? We use SQL Server 7.0?
If not, how do you cancel a long running statement to the DB?

I would have disconnected and reconnected, instead of just clicking New Query.
"Premature optimization is the root of all evil." - Knuth
If I provoked thought, please click the green arrow
If I provoked Aha! please click Propose as Answer

Query timeouts in ABAP

Hello all,
We are running Business Objects 4.0 SP2 and have some users running queries to our ERP system. They say they are running them in the background, but they are still timing out after 10 minutes with an ST22 stating they are exceeding the 600 second timeout limit.
"The program "%_T008C0" has exceeded the maximum permitted runtime without
interruption, and has therefore been terminated."
Is there something they can do differently or an extra selection they need to make to avoid these query timeouts? I do not want to extend the timeout using profile param "rdisp/max_wprun_time" in a production system...
I am looking for another solution besides telling them to query less data.
Any help would be appreciated.
Thanks.

Hello Aman,
We adjusted param "rdisp/max_wprun_time" to extend timeouts across the system. However, eventually the functional team worked to re-write the query so it would not run beyond the standard 10 minute timeout.

Query timeout alternative

Similar Messages

Maybe you are looking for