Interesting you asked about it. When we first encountered the problem, the Cursor Sharing was already set to FORCE both in the Oracle database and ar.conf. The DBA then changed it to be EXACT in the database while we kept it FORCE in ar.conf. This change has improved the performance noticeably, especially for the user to refresh Assigned Work table on the Incident Management console. But the change didn't eliminate the timeout problem.
-----Original Message----- From: patchsk [mailto:[email protected]] Sent: Sunday, January 23, 2011 1:08 PM Subject: Re: Strange ARS Timeout Problem ** What is the value for cursor sharing at the db level and on ar.conf file. Try to make it to Forced and see if it fixes this issue. _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
