Yes, We tried materialized view, but of no use. The time outs are coming no matter what. All dbs run on oracle itself. And one observation we have found is that the admin users get less number of time outs, but for normal users it throws lot number of time outs-infact it wouldn't let do the operations itself. All SQL tuning and indexing things were tried out but of no use. The funny thing is that all the queries whihc happens when tried through backend directly would execute without no issues in a jiffy. Does anyone have more inputs to this.
Thank you!!! Grooms, Frederick W wrote: > > I see you state Oracle... What about using a materialized view to pull > the data for the menu to your local database? You would then make the SQL > menu just a local SQL menu. > > Fred > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of NNMN > Sent: Friday, August 27, 2010 7:24 AM > To: [email protected] > Subject: Time out Error in External Db Access > > Hi Folks! > > So here is the thing about the time out error I am getting. The error that > I > am recieving is > "ARERR [93] Timeout during data retrieval due to busy server -- retry the > operation " > > Now a small detail on the operations i am performing on the background. > 1. A simple SQL Menu where values are fetched from an External db through > a > db link.(This is one place where the same time out occurs.) > 2. An active link which runs on a button click. Now here, the time out > occurs only on the actions where there is access to this external db > using > the same db link which was used above. These actions are simple SQL select > statements which retrieve a single row and insert of one record into the > external tables and so are not huge time intensive queries. > > The db link which we tried using at first was a normal db link. At this > time > we had lots of time out being thrown. Now we tried with a public database > link after that, although we know that there is no performance difference > between both. Now the time out frequency has come down. Can anyone suggest > ways to avoid these time outs completely. These queries which ran from the > workflows where tested from Oracle client by connecting to the aradmin db > using the same db links and it seems to run pretty fine without > considerable > delays. The Server logs and client logs also doesn't suggest much, as in > client logs the error thrown were just something which says -error while > performing filter action- on the correspoding action where the time out > occurs(which only happens in one of the action where the external db is > accessed) and there is nothing from SQL, filter logs, arerrr logs etc. > > Any suggestions and solutions are appreciated!!!! > > Thanks in advance :) > > > ----- > With Warm Regards, > Naveen > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" > > ----- With Warm Regards, Naveen -- View this message in context: http://old.nabble.com/Time-out-Error-in-Externla-Db-Access-tp29552047p29688637.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
