DBLINK status check or query timeout through it

I am accessing some values through DB links in my triggers.The problem is if the remote db is down , the trigger much time (around 75sec) to give me error 12535, 00000, "TNS:operation timed out". I want to reduce this time , i tried changing in listener.ora
listener.ora:CONNECT_TIMEOUT_DB = 10
but no change.
I want to do this because it is impacting the speed of my insert/update on which i have created this trigger.
Is it possible to check the status of dblinks before proceeding with trigger ?
I tried putting select dummy from dual@dblink
but obviously it is still taking same time for the results.

Apologies for my noviceness. I am not able to understand what you said.
I tried googling for "asynchronous trigger" but am not able to find anything relevant.
Your trigger writes all the rowid / PK values that it needs to process.
yes.
A listener process wakes at suitable intervals and attempts to process the records, first checking the DB link...
How to to this ?

Similar Messages

How to get System status Check Boxes into Query selection screen

Dear experts,
Pleas help in knowing how to get System status Check Boxes into quick view query (SQVI), selectionscreen.
Regards
Jogeswara Rao
Edited by: K Jogeswara Rao on Jul 6, 2010 7:26 PM

Problem solved through other Forum
(Checkboxes not possible, some alternative solution to my requirement found)

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

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]

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.

Hung queries, and Oracle thin driver query timeout implementation

We are seeing occasional instances of stuck threads, where the code is in Oracle thin XA driver code waiting for a socket read for a response from the database. Usually only one thread at a time. The connection never terminates and we have to shut down WebLogic to clear it. The DBAs tell us that all connections to the 11g RAC cluster members from our hosts are idle, with no hung or long-running transactions.
This happens every few days across two WebLogic 10.3.5 clustered instances in our QA environment, usually not the same time on two servers (one had four incidents, the other had only one, in the last 15 or so days). Sometimes it has resulted in a hung server, as the driver is holding a lock that blocks other threads (today we had numerous threads block in a TX rollback).
I'm guessing our WebLogic instance somehow is not getting the connection close from the remote host. BTW, there is no firewall between us and the DB. I have not got any strong suspect for the cause (although we are running Linux on a VMWare 4.0 VM, which always worries me).
Ordinarily I'd either ask the application to set a query timeout, or set the query timeout parameter for the connection pools as a workaround (we are using a MultiDatasource), so the transaction would at least abort and the application can handle it. However, while the Oracle driver does support java.sql.Statement.setQueryTimeout(), some brief investigation on my part leads me to believe the timeout is implemented on the server side and not the client side - so that if it is indeed the case that WebLogic does not see the close on the connection, it also would never see the timeout.
Two questions:
1. Is my suspicion about server-side implementation of timeout for Oracle 11g correct?
2. If so, is there some property I can set for the driver that will implement a socket timeout? Is this "safe"?
Thanks for any help!
[ Oracle WebLogic 10.3.5, HotSpot 64 bit JVM 1.6.0_29 on RHEL 5.6 on VMWare; Oracle Thin XA driver bundled with WebLogic; Oracle RAC 11g (three-node cluster)]
Edited by: SteveElkind on Dec 3, 2012 5:25 AM

Thanks, Joe.
My investigations were heading in this direction (e.g., http://docs.oracle.com/cd/B28359_01/java.111/b31224/apxtblsh.htm#CHDBBDDA). However, for WebLogic, is it as simple as adding the following property in the Datasource Connection properties edit box in the WebLogic console?
oracle.net.READ_TIMEOUT=300000
or do I have to edit the connection URL?
I've tried this, and the Datasource restarts OK after the change, but I have no way right now to check whether it actually "works".
(we have some long-running queries; five minutes seems to be a "safe" limita for now)

Query timeout limits

How is it possible to implement limits on query timeouts, so that excessive query runtimes are avoided?
We want to automatically stop queries that have executed for more than ten minutes.
Regards,
Frederick

Hi ,
check this link ..
https://www.sdn.sap.com/irj/scn/advancedsearch?adv=true&cat=sdn_all&cat=sdn_library&query=bex&start=41&searchmode=similar&similardocsuri=/forumsrm/1_category/4_category/134_forum/5968_thread/29457_message
http://help.sap.com/saphelp_nw04/helpdata/en/f3/790555c806491fa772ad46543255ed/frameset.htm
regards,
shikha

Result recording(QM) - Status check error

Hi Friends,
I can not perform Result recording(QE01) due to "status Check Error".
Inspection lot was created through GR. And then i tried to do Result recording. But i am getting error "status check error-This function you selected cannotbe carried out".
Appreciate your help.
Thanks

hi
If no Inspection Plan is found,
1. Inspection Plan is not available. Check in QP03 for the material/plant combination the availability of plan. If not available, create it using QP01.
2. The date of creation of Plan is later that date of creation of Inspection Lot. In this case, in QA02 give the key date as before the date of creation of plan.
Next, you can do the Result Recording (from QA32 screen or use QE51N)
Once all results are entered and saved, the status become INSP.
Now, do the Usage Decision (QA32 / QA11) and here give the acceptace code and post the stock into Unrestricted stock
regards
kunal

EJB Transaction timeout and Statement Query Timeout

I am looking for some details on how statement query timeout is set when statement execution is part of the session bean transaction. I have done some test in webshere 6.1. and JBoss 5.0 and not getting the desired behavior. My understanding is following
- DB is Oracle 11g
- EJB transaction is set to 5 mins.
- Query time out setting is set to default vaule (not sure what is the default value)
- Session bean is updating say customer record using PreparedStatement
- Prior to calling session bean method I am locking the customer record using external/db tool and holding the lock.
- Call session bean method. Method waits endlessly for the lock to be acquired. No transaction rollback after 5 mins.
- After 10 minutes commit the transaction in the external db tool
- Session bean methods throws transaction rollback.
My understanding was that query timeout is set based on transaction "time to live". Please share out thoughts.
Edited by: hdjava on Jun 18, 2010 1:06 PM
Edited by: hdjava on Jun 18, 2010 1:07 PM

The following configuration seems working:
version: OC4J (9.0.3.0.0) (build 020927.1699)
AM deployment:
- bc4j.xcfg: <jbo.ejb.txntimeout>30000</jbo.ejb.txntimeout>
- orion-ejb-jar.xml: <session-deployment name="..." timeout="0"/>
OC4J config:
- data-source: inactivity-timeout="30000"
This keeps connection open for more than default 30 mins of inactivity (30000 secs configured).
Although, oc4j console prints multiple warnings:
DriverManagerConnectionPoolConnection not closed, check your code!
Looks like this is not an intended usage - but working.
Notice that it was a test, not a production environment.
Also pls see 9033: AM as EJB Session bean: pooled connection lost for new txn
I would be thankful for any experience in running AM Session EJB w/o timeout.

Can we assign a T-ode to Query ( Created through SQVi , QuickViewer)

Hi!
Can we assign a T-code and transport the same in differnt -2 clients for the query craeted through QuickViewer ( SQVI )
What i need to do so , Please guide .
Regards
Sheetal

Hi Farrukh Khan
1>go to SQVI t code and enter your query name and press enter
2>In the menu path select Quick view--> additional functions-->Generate Program
3>After Generating the program In the menu path select Quick view--> additional functions-->Display report Name
4>Now in se38 enter the report name in Program field and execute
5>You will get the Initial Selection screen of the report . Go to Menu of System -->Status
6> Note down the Program name and Screen number
7>Go to SE93 and Create a Z tcode for the query, Enter the description and importantly you have to select the 2nd Option radio Button Program and Selection Screen (Report Transaction) and Press enter
8>In the next screen enter the Report name In Program field and enter the screen number
9>In the classification Section select Professional user Transaction
10>In GUI support section select all the options i.e SAPGUI for HTML,Java,Windows
and save
the system will ask for Package select your package if not there then select local object
now execute the Z tcode your report will run sucessfully
Regards
Vijay hebbal

Cannot get asscess to order status, does my order go through?

I cannot get asscess to order status, does my order go through?

Please update to version 24.0
Please try to clear cache and cookies:
Many site issues can be caused by corrupt cookies or cache. In order to try to fix these problems, the first step is to clear both cookies and the cache.
Note: ''This will temporarily log you out of all sites you're logged in to.''
To clear cache and cookies do the following:
#Go to Firefox > History > Clear recent history or (if no Firefox button is shown) go to Tools > Clear recent history.
#Under "Time range to clear", select "Everything".
#Now, click the arrow next to Details to toggle the Details list active.
#From the details list, check ''Cache'' and ''Cookies'' and uncheck everything else.
#Now click the ''Clear now'' button.
Further information can be found in the [[Clear your cache, history and other personal information in Firefox]] article.
Did this fix your problems? Please report back to us!
Thank you.

Query disable status in bex query designer

hi all,
when i opened query in query designer for PA_PA cube it is in disabled mode.iam unabled to restrict or do any changes.and giving error like "the dependent objects are in different transport orders."i installed this particular queries in BI content also.please help me in this issue.
Regards
Vamshi D Krishna

Hi Vamshi,
go to rsa1 - transport connection and select ur query and drag & drop into third screen
u can see the locked request no. of ur query ..
u can take that no. and go to se03 -- give that request no. & execute unlock..
now, again come back to ur transport connection, now u can see under ur query no transport request has been assigned.. select the truck symbol..
It will ask u for the new request no. assign a new request no. of urs and check the query at the designer level. u can able to change the query ..
Hope it helps.
If u have any doubt reply to this message.
Thanks & Regards,
V. Vijay Kumar.

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

ALV Report to display the status of the requests raised through ESS

Hi All,
We have to develop a ALV report to display the status of the requests raised through ESS
for Leave, Travel & Event Management, Travel and Appraisal workflows.
ESS Travel, ESS TEM, ESS Apraisal workflows are associted with SAP Business Objects.
we are using the function module SWI_WORKITEMS_OF_OBJTYPE_GET to get
the top level work item id's by passing the object type like PDRELA_025, BUS2089.
By using SWP_WORKFLOW_LOG_READ function we are getting the workflow log
by passing top level work item id's as imort parameter.
The report output should have the following fields
Initiator, Initiator Personal No, Request Type( Leave, Travel etc.. )
Date of application of the request, Status ( Approved by RM, Rejected etc )
Name of the Approver, Approved / Rejected Date.
The logic should be work for all the above ESS workflows and should be generalized.
Can any one please let me know the procedure to get the required information from the workflow log.
It would be great if any one suggest on the same how to proceed further to get the information as mentioned above.
Thanks & Regards,
Jagadeeswara Rao Balla.

Hello,
You can get most of that information from fm SAP_WAPI_GET_HEADER, input is workitem_id.
regards
Rick Bakker
Hanabi Technology

DBLINK status check or query timeout through it

Similar Messages

Maybe you are looking for