dbms_stats on BIG Table giving error out of process memory when trying to al

Links

Frequent Oracle Errors

•	TNS:could not resolve the connect identifier specified
•	Backtrace message unwound by exceptions
•	invalid identifier
•	PL/SQL compilation error
•	internal error
•	missing expression
•	table or view does not exist
•	end-of-file on communication channel
•	TNS:listener unknown in connect descriptor
•	insufficient privileges
•	PL/SQL: numeric or value error string
•	TNS:protocol adapter error
•	ORACLE not available
•	target host or object does not exist
•	invalid number
•	unable to allocate string bytes of shared memory
•	resource busy and acquire with NOWAIT specified
•	error occurred at recursive SQL level string
•	ORACLE initialization or shutdown in progress
•	archiver error. Connect internal only, until freed
•	snapshot too old
•	unable to extend temp segment by string in tablespace
•	Credential retrieval failed
•	missing or invalid option
•	invalid username/password; logon denied
•	unable to create INITIAL extent for segment
•	out of process memory when trying to allocate string bytes
•	shared memory realm does not exist
•	cannot insert NULL
•	TNS:unable to connect to destination
•	remote database not found'>ora-02019
•	exception encountered: core dump
•	inconsistent datatypes
•	no data found
•	TNS:operation timed out
•	PL/SQL: could not find program
•	existing state of packages has been discarded
•	maximum number of processes exceeded
•	error signaled in parallel query server
•	ORACLE instance terminated. Disconnection forced
•	TNS:packet writer failure
•	see ORA-12699
•	missing right parenthesis
•	name is already used by an existing object
•	cannot identify/lock data file
•	invalid file operation
•	quoted string not properly terminated

dbms_stats on BIG Table giving error out of process memory when trying to al

dbms_stats on BIG Table giving error out of process memory when trying to al

2005-08-19 - By Paul Drake

On 8/19/05, VIVEK_SHARMA <VIVEK_SHARMA@(protected)> 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 (See ORA-12801.ora-code.com): error signaled in parallel query server P000
>
> ORA-04030 (See ORA-04030.ora-code.com): out of process memory when trying to allocate 1049100 bytes
>
> (callheap,kllcqas:kllsltba)
>
> ORA-06512 (See ORA-06512.ora-code.com): at "SYS.DBMS_STATS", line 9375
>
> ORA-06512 (See ORA-06512.ora-code.com): at "SYS.DBMS_STATS", line 9389
>
> ORA-06512 (See ORA-06512.ora-code.com): 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.

 <div>On 8/19/05, VIVEK_SHARMA <<a href="mailto:VIVEK_SHARMA@(protected)">VIVEK_SHARMA
@(protected)</a>> wrote:<blockquote class="gmail_quote" style="border
-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:
1ex;">

<div>

 

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 (See ORA-12801.ora-code.com): error signaled in parallel query server P000

ORA-04030 (See ORA-04030.ora-code.com): out of process memory when trying to allocate
1049100 bytes

(callheap,kllcqas:kllsltba)

ORA-06512 (See ORA-06512.ora-code.com): at "SYS.DBMS_STATS", line 9375

ORA-06512 (See ORA-06512.ora-code.com): at "SYS.DBMS_STATS", line 9389

ORA-06512 (See ORA-06512.ora-code.com): at line 1</div></blockquote><div> 
<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? 
 
</div>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 
 <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204,
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>
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

 

</div>

<table><tbody><tr><td bgcolor="#ffffff">****************
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*** 
</td></tr></tbody></table>
</blockquote></div> -- #/etc/init.d/init.cssd stop
 # f=ma, divide by 1, convert to moles.