RE: Quick question on cursor resource use

2003-03-12 Thread Grant Allen
Yeah, OK, the 50 figure was just to provoke some responses :-). I'll go ahead and watch the various v$ views as I increase the cursor level, and see if there's anything nasty there (I'm not expecting any problems). Ciao Fuzzy :-) -Original Message- Sent: Tuesday, March 11, 2003 16:5

Re: Quick question on cursor resource use

2003-03-11 Thread Bjørn Engsig
I wouldn't hesitate to set it to 500 or a even 1000 if your appliation really needs this many.  But if you think about 10's of thousands, I would start really looking af the application to understand if it were written correctly.  The major memory is not allocated by setting the parameter, but

RE: Quick question on cursor resource use

2003-03-11 Thread Grant Allen
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of DENNIS > WILLIAMS > Sent: Monday, March 10, 2003 15:45 > To: Multiple recipients of list ORACLE-L > Subject: RE: Quick question on cursor resource use > > > Fuzzy >Wha

RE: Quick question on cursor resource use

2003-03-10 Thread Stephane Faroult
>Hi all, > >I'm trying to determine the resource footprint of a >cursor - we're fiddling >with open_cursors in init.ora, and I want to get an >idea of the possible >impact on memory, etc., if I bump this up from 100 >to 500. > >As these are allocated per session, I assume they >probably consume sta

RE: Quick question on cursor resource use

2003-03-10 Thread DENNIS WILLIAMS
Fuzzy What is prompting you to increase OPEN_CURSORS? Is your application currently receiving an error from running out of cursors? Dennis Williams DBA, 40%OCP, 100% DBA Lifetouch, Inc. [EMAIL PROTECTED] -Original Message- Sent: Monday, March 10, 2003 7:59 AM To: Multiple recipients

Quick question on cursor resource use

2003-03-10 Thread Grant Allen
Hi all, I'm trying to determine the resource footprint of a cursor - we're fiddling with open_cursors in init.ora, and I want to get an idea of the possible impact on memory, etc., if I bump this up from 100 to 500. As these are allocated per session, I assume they probably consume stack or heap