Re: ORA-04030 During Export

Hi,

Please check the following:

1]- The rule of thumb is that swap space should be 3 * RAM Is that the case ? you may be running out of swap space though (if some other process(es) has grabbed lots). The way to check is to look at the console (or it's log - /var/log/console), and check for "out of swap space errors".

2]- The ONLY OTHER thing this could be is process ulimits. In the Korn shell, type: ulimit -a
Check the vmemory limit. If it's not unlimited, he needs to think about increasing it (in the UNIX kernel)

3]- The most likely cause of ORA-7324 is the data segment trying to grow into the base of the SGA. Suggested solutions are to relocate the attach address for the SGA. Other suggestions include reducing the sort_area_size and the sort_area_retained_size.

4]- Need to up SHHMAX to well above SGA size.

Best Regards

"The Views expressed here are my own and not necessarily those of Oracle Corporation"

Eric Fenderbosch <efender_at_ix.netcom.com> wrote in message news:7u7bqi$rhj$1_at_nntp5.atl.mindspring.net...
> Executing the following export command in a cron job on a "OSF1 alpha2
V4.0
> 878 alpha" system gives an ORA-04030 error.
>
> exp system/manager file=prod.dmp log=prod.log full=y direct=y consistent=y
> >/dev/null 2>&1
>
> ORA-04030: out of process memory when trying to allocate 532504 bytes
> (session heap, kllcq queue unaligned chunk of slots)
> Followed by:
> ORA-07324: smpall: malloc error while allocating pga
>
> The system has 1 GB RAM and the db_block_buffers and shared_pool are about
> 170 MB and 85 MB, respectively. The same export command completed
> successfully in our TEST instance with 85 MB db buffers and 43 MB shared
> pool. The cronjob runs during 3rd shift, when database activity should be
> pretty low, so I don't really expect much overhead from the consistent=y
> flag.
>
> The Oracle help says:
> ORA-04030: out of process memory when trying to allocate num bytes str,str
> Cause: Operating system process private memory has been exhausted.
> Action: See the database administrator or operating system administrator
to
> increase process memory quota. There may be a bug in the application that
> causes excessive allocations of process memory space.
>
> I checked "ulimit -a" and "ulimit -H -a" and get:
> time(seconds) unlimited
> file(blocks) unlimited
> data(kbytes) 131072
> stack(kbytes) 2048
> memory(kbytes) 1021984
> coredump(blocks) unlimited
> nofiles(descriptors) 4096
> vmemory(kbytes) 104857
>
> time(seconds) unlimited
> file(blocks) unlimited
> data(kbytes) 1048576
> stack(kbytes) 32768
> memory(kbytes) 1021984
> coredump(blocks) unlimited
> nofiles(descriptors) 4096
> vmemory(kbytes) 1048576
>
> Am I even looking at the correct parameters? How can I change the ulimit
> for memory permanently? I'm not very familiar with DEC-UNIX, I know HP-UX
> and AIX much better. I can change it temporarily, but I can't find how to
> change the system wide default. Any help would be appreciated.
>
> Thanks,
>
> Eric
> efender at dpai dot com
>
>
Received on Fri Oct 15 1999 - 13:30:18 CDT