Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: dbms_stats on BIG Table giving error out of process memory when trying to allocate 1049100 bytes

Re: dbms_stats on BIG Table giving error out of process memory when trying to allocate 1049100 bytes

From: Paul Drake <bdbafh_at_gmail.com>
Date: Fri, 19 Aug 2005 12:10:19 -0400
Message-ID: <910046b4050819091031f242e9@mail.gmail.com>


On 8/19/05, VIVEK_SHARMA <VIVEK_SHARMA_at_infosys.com> wrote:
>
> SQL> alter session set sort_area_size=500000000
>
> SQL> exec
> dbms_stats.gather_table_stats('TBAADM','HIST_TRAN_DTL_TABLE',degree=>4,estimate_percent=>30);
>
>
> ERROR at line 1:
>
> ORA-12801: error signaled in parallel query server P000
>
> ORA-04030: out of process memory when trying to allocate 1049100 bytes
>
> (callheap,kllcqas:kllsltba)
>
> ORA-06512: at "SYS.DBMS_STATS", line 9375
>
> ORA-06512: at "SYS.DBMS_STATS", line 9389
>
> ORA-06512: at line 1
>

<borrowed>
Patient: "Doctor, It hurts when I do this (makes motion)". Doctor: "Don't do that."

parallel query slaves are each going to allocate private areas in memory. this system configuration does not have enough memory for what you are attempting to do.

Q1: workarea_size_policy [AUTO | MANUAL] for the instance, session? If the workarea_size_policy=AUTO, it doesn't matter what you set the sort_area_size to, as its not being used.

Q2: what are the existing settings for the following parameters: pga_aggregate_target
workarea_size_policy
shared_pool_size
large_pool_size
java_pool_size
db_cache_size
sga_max_size

Q3: if in fact, at least for the session, the workarea_size_policy=MANUAL, if 4 parallel query slaves each threw 512 MB of memory, you'd be well over the process limit. Have you attempted this with smaller values for the sort_area_size, say 64 MB and had it complete?

Q4: is this a 32 bit of 64 bit version of solaris, oracle? (not that you'd want to run 64 bit with only 2 GB of physical memory - I don't see the point there)

Q5: did you examine v$sgastat at the time to see how the memory in the sga was allocated?

that's a start.

Paul

Existing Pointers :-
>
> Sometimes decreasing the size of your sort_area_size will remedy this
> problem.
>
> Another thought is that if you are using parallel query on this view,
> perhaps the amount of memory required for the number of slaves handling the
> query is growing too big.
>
> Qs ANY OTHER POINTERS PLEASE?
>
> Server info:-
>
> ----------------
>
> Server 2 GB memory
>
> 2 CPUs
>
> Solaris 9
>
> Oracle 9i
>
> THANKS INDEED
>
> **************** CAUTION - Disclaimer *****************
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended
> solely for the use of the addressee(s). If you are not the intended
> recipient, please notify the sender by e-mail and delete the original
> message. Further, you are not to copy, disclose, or distribute this e-mail
> or its contents to any other person and any such actions are unlawful. This
> e-mail may contain viruses. Infosys has taken every reasonable precaution to
> minimize this risk, but is not liable for any damage you may sustain as a
> result of any virus in this e-mail. You should carry out your own virus
> checks before opening the e-mail or attachment. Infosys reserves the right
> to monitor and review the content of all messages sent to or from this
> e-mail address. Messages sent to or from this e-mail address may be stored
> on the Infosys e-mail system.
> ***INFOSYS******** End of Disclaimer ********INFOSYS***
>

-- 
#/etc/init.d/init.cssd stop
# f=ma, divide by 1, convert to moles.

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Aug 19 2005 - 11:12:25 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US