My DBA's are having a real problem with setting cursor-sharing parameter for the entire instance. Evidently is cause some problems in the other table spaces. Is there a means of setting the parameter for just the ars session? Something like the following when the server is started? ALTER SESSION set CURSOR_SHARING = FORCE;" -Rob Tucker
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Axton Sent: Tuesday, February 13, 2007 10:41 AM To: arslist@ARSLIST.ORG Subject: Re: Oracle LOB relocation ** Slightly OT, but you may want to instruct your dba's to set the oracle instance parameter 'cursor_sharing' to similar or force. This will greatly reduce the size requirements of oracle's shared pool and greatly reduce hard parses. This whitepaper covers some of the details: http://documents.bmc.com/supportu/documents/78/31/67831/67831.pdf My favorite quote from this doc: "Any application that uses all literals without cursor sharing enabled is not a very scalable application." Axton Grams On 2/13/07, Tucker, Rob <[EMAIL PROTECTED]> wrote: ** Thanks Axton. As always, great information -Rob ________________________________ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG ] On Behalf Of Axton Sent: Monday, February 12, 2007 5:34 PM To: arslist@ARSLIST.ORG Subject: Re: Oracle LOB relocation ** Manage the log storage through the ardb.conf file. Don't let the dba do it directly on the db. This will cause endless headaches for you and them. Probably the best approach would be: - set up the server - create the ardb.conf file to define the log storage - have the dba's manually move the lobs while arserver is stopped - start arserver You will more than likely need to experiment with the ardb.conf and some test forms to make sure you get the syntax right. Taking this approach (the best I can see at the moment) has several advantages: - installer gets to run as it normally would - dba's feel cozy because they witnessed the relocation of the lobs - the lobs will be managed on an ongoing basis by the ardb.conf file Some things to keep in mind: - you will need to update the ardb.conf every time a new lob is added (prior to adding the lob); failure to do so will cause the lob to be stored in the same tablespace as tables/indexes - the ardb.conf file had some issues in 6.0.1 with length limitations on the clauses (300 something characters). I am not sure if this issue exists in the later releases Some other things your dba's may want to look into as far as performance tuning if you go this route (these are possible using the ardb.conf file as well): - index storage - table/index partitioning Axton Grams On 2/12/07, Tucker, Rob < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: ** We are getting ready to stand up ITSM 7 on Oracle 10G. My DBA's want to relocated all the lobs in particularly HPD:Help Desk I grew up with SQL Server and am not: * Sure what it is they are wanting to do * Sure that Remedy will allow them to do what they are planning to do Is there anyone out there who would shout "NO! GO BACK! DO NOT PASS GO!" or this something perfectly reasonable and doable? Thanks, -Rob ____________________________________________ Rob Tucker New Edge Networks ARS Administration and Development [EMAIL PROTECTED] Vancover,Washington tel: 360-759-9670 fax:360-693-9997 __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
