ora-04030 [message #336176] |
Fri, 25 July 2008 02:11 |
srini_thiru
Messages: 133 Registered: May 2008
|
Senior Member |
|
|
Hi to all,
I am using oracle 10.2.0.4.0 on windows platform. Ram size is 8GB. We have 2 databases one is production and other is test.
The problem is when we try to run one report in production database through application we receive the below error.
ORA-04030: out of process memory when trying to allocate 28 bytes (kxs-heap-w,kxsclb in kxscfreg)
We we run the query used by this report in sqlplus we receive the same error, But the same query is working good in other plants.
Size of the Memory parameters:
SGA_TARGET=2648M
SGA_MAX_SIZE=2648M
PGA_AGGREGATE_TARGET=2500M
What i have to do solve this error. Waiting for the response
Thanks in Advance,
Seenu.
|
|
|
|
|
|
|
Re: ora-04030 [message #336205 is a reply to message #336187] |
Fri, 25 July 2008 03:19 |
srini_thiru
Messages: 133 Registered: May 2008
|
Senior Member |
|
|
Michel Cadot wrote on Fri, 25 July 2008 02:24 | This is an OS error belonging to your process limit, not an Oracle one.
check ulimit
Regards
Michel
|
Please tell me how to check the ulimit parameter in windows platform and what i have to change in the ulimit parameter.
Thanks in Advance,
Seenu
|
|
|
Re: ora-04030 [message #336710 is a reply to message #336205] |
Mon, 28 July 2008 14:26 |
sunil_v_mishra
Messages: 506 Registered: March 2005
|
Senior Member |
|
|
Using automatic PGA memory management will help reduce the possibility of ORA-4030 errors. Please note that PGA_AGGREGATE_TARGET is NOT supported on OpenVMS in Oracle 9i, but it is in Oracle 10g.
|
|
|
|
Re: ora-04030 [message #337585 is a reply to message #337580] |
Thu, 31 July 2008 05:42 |
|
Michel Cadot
Messages: 68716 Registered: March 2007 Location: Saint-Maur, France, https...
|
Senior Member Account Moderator |
|
|
Quote: | how to turn on the automatic PGA memory management
|
Just set PGA_AGGREGATE_TARGET parameter.
But read documentation about this and make tests before, this will change the behaviour of your instance and maybe execution plan of your statements.
In addition, it will not change anything if the error comes from PL/SQL collections.
Regards
Michel
[Updated on: Thu, 31 July 2008 05:42] Report message to a moderator
|
|
|