Re: pga workarea and ora-04030

2004-01-20 Thread Jonathan Lewis
PM Aan: Multiple recipients of list ORACLE-L Onderwerp: Re: pga workarea and ora-04030 I think what you've demonstrated is that pl/sql tables are not limited by pga-aggregate target, and that a pl/sql table can grow until it has taken up all the available memory on your machine. I'd

Re: pga workarea and ora-04030

2004-01-20 Thread Connor McDonald
on HPUX? Regards, Jeroen -Oorspronkelijk bericht- Van: Jonathan Lewis [mailto:[EMAIL PROTECTED] Verzonden: Saturday, January 10, 2004 6:54 PM Aan: Multiple recipients of list ORACLE-L Onderwerp: Re: pga workarea and ora-04030 I think what you've demonstrated

RE: pga workarea and ora-04030

2004-01-12 Thread Jeroen van Sluisdam
:[EMAIL PROTECTED] Verzonden: dinsdag 6 januari 2004 16:49 Aan: Multiple recipients of list ORACLE-L Onderwerp: Re: pga workarea and ora-04030 The workarea_policy stuff does not apply to things like pl/sql tables, only to tuneable memory. Given that you don't have the problem when you disable

Re: pga workarea and ora-04030

2004-01-10 Thread Jonathan Lewis
PROTECTED] Verzonden: dinsdag 6 januari 2004 16:49 Aan: Multiple recipients of list ORACLE-L Onderwerp: Re: pga workarea and ora-04030 The workarea_policy stuff does not apply to things like pl/sql tables, only to tuneable memory. Given that you don't have the problem when you disable

Re: pga workarea and ora-04030

2004-01-10 Thread Ryan
' || uitleg ); end; end; -Oorspronkelijk bericht- Van: Jonathan Lewis [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 6 januari 2004 16:49 Aan: Multiple recipients of list ORACLE-L Onderwerp: Re: pga workarea and ora-04030 The workarea_policy stuff does not apply to things

Re: pga workarea and ora-04030

2004-01-10 Thread Jonathan Lewis
In the UGA, I should think (which also means the SGA if you are running MTS). It can't be in the PGA (ignoring the fact that the UGA is in the PGA for non-MTS) or you couldn't have global pl/sql tables that persist across database calls. Regards Jonathan Lewis http://www.jlcomp.demon.co.uk

Re: pga workarea and ora-04030

2004-01-10 Thread Ryan
I have seen people bulk collect into pl/sql tables so much data that you cannot even connect to the server. So I'm assuming that ones the UGA fills up, Oracle will allocate whatever unused memory is left on the server for pl/sql tables? - Original Message - To: Multiple recipients of list

RE: pga workarea and ora-04030

2004-01-10 Thread Bobak, Mark
. -Original Message- From: Ryan [mailto:[EMAIL PROTECTED] Sent: Sat 1/10/2004 4:34 PM To: Multiple recipients of list ORACLE-L Cc: Subject:Re: pga workarea and ora-04030 I have seen people bulk collect into pl/sql tables so much data that you cannot even connect to the server

Re: pga workarea and ora-04030

2004-01-10 Thread Tim Gorman
PROTECTED] Verzonden: dinsdag 6 januari 2004 16:49 Aan: Multiple recipients of list ORACLE-L Onderwerp: Re: pga workarea and ora-04030 The workarea_policy stuff does not apply to things like pl/sql tables, only to tuneable memory. Given that you don't have the problem when you disable p_a_t

RE: pga workarea and ora-04030

2004-01-09 Thread Jeroen van Sluisdam
; -Oorspronkelijk bericht- Van: Jonathan Lewis [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 6 januari 2004 16:49 Aan: Multiple recipients of list ORACLE-L Onderwerp: Re: pga workarea and ora-04030 The workarea_policy stuff does not apply to things like pl/sql tables, only to tuneable memory. Given

Re: pga workarea and ora-04030

2004-01-06 Thread Jonathan Lewis
The workarea_policy stuff does not apply to things like pl/sql tables, only to tuneable memory. Given that you don't have the problem when you disable p_a_t and w_p, it may be that there is some buggy event occurring where the workarea_policy code is being infringed by an abuse of pga memory.

Re: pga workarea and ora-04030

2004-01-06 Thread Tanel Poder
When I increase the pga_aggregate_target to 2Gb and the smm_max_size also the program fails around the following numbers from pgastat I'm not advocating fiddling with hidden parameters here, but there is one more parameter which limits PGA usage, it's _pga_max_size and defaults to 200M.