We have two systems - both on Solaris logical servers, both on the same box. Both have remote Oracle databases. (7.1 001 for Solaris w/Oracle, IM 7.03) Dev = faster response time (saving an Incident takes 9 seconds) QA = very slow response time (saving an Incident takes 65 seconds). These two systems are - as far as we know - identical. However, when debugging the system we have found that the fast (dev) system is executing the following oracle server side parameters during a save: ALTER SESSION set CURSOR_SHARING = EXACT ALTER SESSION set CURSOR_SHARING = FORCE
This is NOT happening on the QA server. Both servers have the "Oracle-Cursor-Sharing: FORCE" parameter set in the ar.conf file and the corresponding appropriate setting is established in Oracle (and we've checked these like 9000 times). Anyone know what setting/config would make Remedy do this to Oracle? William Rentfrow, Principal Consultant [EMAIL PROTECTED] C 701-306-6157 O 952-432-0227 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
