Increase Query timeout in Dashboard

Hi,
When we add a query through query browser in dashboard after certain time the connection gets timed out if the system is idle . Normally we can increase time out for webi reports but where could we increase the time for the Bex Queries to get timed out.
Thanks&Regards,
Krishna

Hi Hari,
I hope its not possible, Nothing can be done on query browser timeout. Please a raise a discussion on this in the below link.
SAP BusinessObjects Dashboards: Ideas
--SumanT

Similar Messages

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

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

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 issue

I have some large queries that update databases that are
timing out before they are done. Is there a way to set the
particular query timeout to be endless?
TIMEOUT="milliseconds" = ????endless????

It is now clear, much more from your explanation than from
your query, that the business of reading the file, parsing it and
looping with cfoutput to insert the data into the database all
contribute to the bottle-neck. I am surprised by the suggestion
that reading and parsing a text file costs more time than if you
split it into smaller files.
In any case, experiment by replacing the cfoutput loop with
cfloop. (Then apply cfoutput where the pound signs occur). Also
increase the request timeout setting in the Coldfusion
Administrator. Use the getTickCount function to find out piecewise
which code blocks take the most time. Its usage is as follows
cfset beginCount = GetTickCount()>

<cfset endCount = GetTickCount()>
Execution time of code block: <cfoutput>#endCount -
beginCount#</cfoutput> milliseconds
edit: "than" in place of "that"

Query timeout expired and Invalid object name

I have a program that processes data (dequeues) and polls about every 2.5 seconds - normally there are several records to process per second - it does this constantly 24/7. The program runs fine at about 100 sites. At 2 sites the following error occurs
about once per day. Typically the table has less than 10 records that get processed ie read then deleted. DataObjects are used ie the data is read, connection closed, processed, deleted using T-SQL from ADO - ie transactions are as short as possible.
Error#-2147217871 Query timeout expired. SQL:SELECT RealID, RxerID, PhoneID, Min(ServerDtTm), min(ID) FROM dbo.tblPreReceiver GROUP BY RealID, RxerID, PhoneID ORDER BY Min(ServerDtTm), min(ID)
Inner exception Error No. -2147217865. Error Desc:Invalid object name 'dbo.tblPreReceiver'.. Native Error:208 Source:Microsoft OLE DB Provider for SQL Server SQL State:42S02.
SQL Server 2008R2 (Express at one site and Standard another).
The program then runs again 2.5 seconds later without error.
Can anyone explain why?
I suspect it is a blocking error but the error message does not suggest this at all. There is another application which writes to this queue, this does not report the error.

Yes, blocking can be the cause. The default command timeout is 30 sec and if the table is locked by an other process, the command waits until the table is accessable ... or the timeout raises. You could increase the timeout value or you could perform "dirty
read" = ignoring lock, but I don't want to suggest to do it.
Olaf Helper
[ Blog] [ Xing] [ MVP]

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.

Report burst:To increase query performance in xcelsius

Is there anyway to increase query performance in xcelsius by using report bursting

Fremlin,
Report bursting is only for distributing your reports to your end users.
You can improve performance only by following the [Best practices|https://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/a084a11c-6564-2b10-79ac-cc1eb3f017ac] in xcelsius.
-Anil

11.1.1.5 - How can we increase the timeout of BPM Workspace ?

Hi ,
I am facing an issue where the BPM Workspace times out after every 5 mins or so.
I read in another post that we need to edit some workspace.properties file - where can I find it.
I tried using http://technology.amis.nl/blog/13768/increase-the-timeout-of-oracle-bpm-worklist-app/comment-page-1#comment-481839 but ran into some issues (should be there as my comment) where the timeout became too high.
Appreciate your help.
Thanks

I got this resolved. Added a different variable for the weblogic.xml timeout and teh web.xml timeout (Btw the digits after the timeout props are not needed if you donot need too many variables).
Also My config root was pointing to the wrong war. I changed it to point to a correct .war (relative location can be used too) & it worked just fine after that !
Thanks

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.

Refresh Query Button in Dashboard

Hello,
We have created a dashboard where we have used a BEx Query.
Refresh Query Button is added to the Dashboard.
The issue is:
We have two Query Prompt selectors in the Dashboard and these are Query variables used.
In the Dashbaord preview, when I select Calendar Year in the prompt selector, all the data for that year is shown.
Now, when I further select Calendar Month, the data is shown for that selected year and month.
But, when I just want to select another year without any month selected, it does not happen as the month is already selected.
In this scenario, if I click on Refresh button, all the selections in the prompt selectors should be removed and the dashboard should return to the First Display, but it is not doing so....
Can anyone let me know how to clear the values selected in the prompt selectors or how the refresh query button works....
Note: We have not used excel for any data display or calculations, everything is directly connected to BEx Queries.
Thanks
Lavanya

Hi
plz try RESET BUTTON
the reset button does
all the selections in the prompt selectors get removed and the dashboard return to the First Display.
Refresh query button
it refer only the query not the dashboard to refresh dashboard we have to use reset button .

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.

Increase Query timeout in Dashboard

Similar Messages

Maybe you are looking for