Pga_aggregate_target and sort_area_size

Hi. all.
when using pga_aggregate_target, sort_area_size is meaningless?
Or, I have to set sort_area_size=0??
- pga_aggregate_target=500M
- workarea_size_policy=auto
- sort_area_size=65536
Thanks and regards.

May be this can help you understand in more detail.
PGA_AGGREGATE_TARGET specifies the target aggregate PGA memory available to all server processes attached to the instance.
Setting PGA_AGGREGATE_TARGET to a nonzero value has the effect of automatically setting the WORKAREA_SIZE_POLICY parameter to AUTO. This means that SQL working areas used by memory-intensive SQL operators (such as sort, group-by, hash-join, bitmap merge, and bitmap create) will be automatically sized. A nonzero value for this parameter is the default since, unless you specify otherwise, Oracle sets it to 20% of the SGA or 10 MB, whichever is greater.
Setting PGA_AGGREGATE_TARGET to 0 automatically sets the WORKAREA_SIZE_POLICY parameter to MANUAL. This means that SQL workareas are sized using the AREASIZE parameters.
Oracle attempts to keep the amount of private memory below the target specified by this parameter by adapting the size of the work areas to private memory. When increasing the value of this parameter, you indirectly increase the memory allotted to work areas. Consequently, more memory-intensive operations are able to run fully in memory and less will work their way over to disk.
When setting this parameter, you should examine the total memory on your system that is available to the Oracle instance and subtract the SGA. You can assign the remaining memory to PGA_AGGREGATE_TARGET.

Similar Messages

Pga_aggregate_target and hash_join cost (anomalies)

Hi,
I've got some performance issues with queries using bind variables (BVP + histograms = evil).
I did some test cases in test environment where the only difference with PROD was pga_aggregate_target .
And was able to make plan changes w/o changing query .
Whole test was:
alter session set workarea_size_policy=manual;
alter session set hash_area_size=11131000;
and with that settings optimizer choose:
TABLE ACCESS FULL with HJ
over
nested loop with index Range Scan.
My question is can query plan depend on current hash_area_size value derivered from PAT parameter (is that dynamic during session life) ?
I can imagine that session can have different hash_area_size in different point in time when workarea_size_policy=auto,
because the amount of allocated memory depends on whole system load.
But this leads to anonalies in plans is that possible ?
During my test, query was reparsed because of hash_area_size change, nothing more.
DB 9.2.0.8 EE
Regards.
GG
Edited by: user10388717 on May 29, 2009 6:25 AM

But this leads to anonalies in plans is that possible ?Yes, it may affect plans in runtime. There are different causes to not shared cursors due to some changes besides query text change. It may be checked through [V$SQL_SHARED_CURSOR|http://download.oracle.com/docs/cd/B10501_01/server.920/a96536/ch3199.htm#1125735] view.

ORA-12500 and sort_area_size value

Hi,
I've hit an ORA-12500 'listener failed to start a dedicated server process' error after the increase of sort_area_size from 250M to 500M. DB server has plenty of RAM which would easily accomodate additinal memory for PGA. Has anyone experinced that before? Thanks.

There's (normally) no need to set SORT_AREA_SIZE, when a PGA is configured. From the parameter reference:
Oracle does not recommend using the SORT_AREA_SIZE parameter unless the instance is configured with the shared server option. Oracle recommends that you enable automatic sizing of SQL working areas by setting PGA_AGGREGATE_TARGET instead. SORT_AREA_SIZE is retained for backward compatibility.
Werner

PGA and SORT_AREA_SIZE

Hi,
I have one sql query with sort operation (select * from table order by col1,col2,col3,col4) and I have measured the pga,uga and direct temp statistics of this session (from other session).
When I set up SORT_AREA_SIZE to be very large (about 1GB) and workarea_size_policy to 'MANUAL' I have expected that all sort will be done entirely in memory because my table is not large to much (about 40000 rows), so I expected:
physical reads direct temporary tablespace = 0
physical writes direct temporary tablespace = 0
1) It is true when I am testing on 10.1.0.4.0 oracle database (Linux 2.6.9-55.0.0.0.2.ELsmp i686)
2) When I am testing on 10.2.0.4.0 database (Linux 2.6.18-53.el5 x86_64) I get output like this:
physical reads direct temporary tablespace 2377
physical writes direct temporary tablespace 2377
I asked myself how it is possible to see this physical reads/writes (because I have already executed my sort operation, before, so this is soft parse and I have setup the SORT_AREA_SIZE to be 1GB).
Best regards,
Dragan

There were some bugs related to setting session parameters (don't remember what versions affected). Try to repeat your test case, but with double executing each ALTER SESSION, i.e.
alter session set sort_area_size=1073741824;
alter session set sort_area_size=1073741824;
alter session set workarea_size_policy=manual;
alter session set workarea_size_policy=manual;

When to use PGA_AGGREGATE_TARGET and when to use temporary table space?

Hi, all.
I am a little confused with regard to when to use pga work area, and
when to use temporary tablespace?
Is there any one who could give me an advice or a document?
Thanks in advance.
Best Regards.
Message was edited by:
user507290

You are more than a little confused... What has one to do with the other, do you think?
All Oracle documentation is at http://tahiti.oracle.com - I suggest you start with the Concepts manual of your version

How to increase the size of sort_area_size

How to increase the size of sort_area_size and what size should be according to the PROD database
Thanks

user10869960 wrote:
Hi,
Many Thanks Charles
Oracle does not recommend using the SORT_AREA_SIZE parameter unless the instance is configured with the shared server option. Oracle recommends that you enable automatic sizing of SQL working areas by setting PGA_AGGREGATE_TARGET instead. SORT_AREA_SIZE is retained for backward compatibility."
--How can i know the instance is configured with the shared server option or not?This might be a tough question to answer. A shared server configuration may be enabled, but the clients may still connect using dedicated sessions, in which case PGA_AGGREGATE_TARGET would still apply.
From
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/dynviews_2088.htm
V$SESSION includes a column named SERVER which will contain one of the following for each of the sessions: DEDICATED, SHARED, PSEUDO, or NONE. As a quick check, you could query V$SESSION to see if any sessions are connected using a shared server connection.
From:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/manproc.htm
There are several parameters which are used to configure shared server support, as well as several views to monitor shared server.
As Robert mentioned, when the WORKAREA_SIZE_POLICY is set to AUTO, the SORT_AREA_SIZE setting is not used, unless a shared server configuration is in use.
--What default value is WORKAREA_SIZE_POLICY and SORT_AREA_SIZE ?From:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams157.htm
"Setting PGA_AGGREGATE_TARGET to a nonzero value has the effect of automatically setting the WORKAREA_SIZE_POLICY parameter to AUTO. This means that SQL working areas used by memory-intensive SQL operators (such as sort, group-by, hash-join, bitmap merge, and bitmap create) will be automatically sized. A nonzero value for this parameter is the default since, unless you specify otherwise, Oracle sets it to 20% of the SGA or 10 MB, whichever is greater."
Actually I am facing performence issue since long time till now i did not get the solution even i have raised SRs but i could not.When the issue occur system seems hang.what i monitored whenever hdisk0 and hdisk1 use 100% the issue occur.
Regards,
SajidWhen you say that you have had a performance issue for a long time, is it a performance problem faced by a single SQL statement, a single user, a single application, or everything on the server? If you are able to identify a single user, or SQL statement that is experiencing poor performance, I suggest starting with a 10046 trace at level 8 (wait events) or level 12 (wait events and bind variables) to determine why the execution appears to be slow. If you have not yet determined a specific user or SQL statement that is experiencing performance problems, you might start with either a Statspack Report or an AWR Report (AWR requires a separate license).
If you believe that temp tablespace usage may be a contributing factor to the performance problem, you may want to periodically run this query, which will indicate currently in use temp tablespace usage:
{code}
SELECT /*+ ORDERED */
TU.USERNAME,
S.SID,
S.SERIAL#,
S.SQL_ID,
S.SQL_ADDRESS,
TU.SEGTYPE,
TU.EXTENTS,
TU.BLOCKS,
SQL.SQL_TEXT
FROM
V$TEMPSEG_USAGE TU,
V$SESSION S,
V$SQL SQL
WHERE
TU.SESSION_ADDR=S.SADDR
AND TU.SESSION_NUM=S.SERIAL#
AND S.SQL_ID=SQL.SQL_ID
AND S.SQL_ADDRESS=SQL.ADDRESS;
{code}
The SID and SERIAL# returned by the above could then be used to enable a 10046 trace for a session. The SQL_ID (and CHILD_NUMBER from V$SESSION in recent releases) could be used with DBMS_XPLAN.DISPLAY_CURSOR to return the execution plan for the SQL statement.
You could also take a look in V$SQL_WORKAREA_ACTIVE to determine which, if any, SQL statement are resulting in single-pass, or multi-pass executions, which both access the temp tablespace.
Charles Hooper
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.

How to set sort_area_size

hello
I’m dealing with a query in which almost 100 inner joins involved. I will post query if needed. Basically it is insert statement but I run only it selection part it take 40 minutes. When I run ASH REPORT during execution I found direct path read temp, direct path write temp in top user event , buffer busy waits, control file sequential read,. I’m using 11g with automatic memory management 9Gb assign to memeory_target, and memeory_max_target,. My workarea_size_policy is auto and sort_area_size
is default 64k. all sory take palce in temp almost 10 to 15 GB temp use when I executes this select statement. I know it is very difficult to sorry all in memory but it should not done all in temp. I wanted to change workarea_size_policyto manual and set sort_area_size. What would be the size of sort_area_size ? I was reading a BOOK of Jonathan Lewis COST based oracle fundamental in which he told us the way to sizing the sort_area_size. But he did not show how he calculated this size and he did only for one table in my case five table join with one table. How I calculate size
Here is John Example
After using the dbms_stats.gather_table_stats procedure, I can check view user_tables
to confirm that the table fills 2,753 blocks, and holds 1,048,576 rows with an avg_row_len of
14 bytes, and that the avg_col_len for column sortcode is 7 bytes (the v2, v3 columns are there
simply to avoid the possibility of some funny boundary conditions appearing). These 7 bytes
include the 1 byte that holds the column length itself, so we can work out that the total volume
of data sorted must be 6MB, and that my memory allocation of 1MB is not going to be sufficient
for an in-memory (optimal) sort.

Oracle Studnet wrote:
I know it is very difficult to sorry all in memory but it should not done all in temp. I wanted to change workarea_size_policyto manual and set sort_area_size. What would be the size of sort_area_sizeIn 11g you can check for a long running query in V$SQL_PLAN_MONITOR how much memory each workarea execution consumed (just to check if your automatic workarea_size_policy seems to be an issue).
You can run your query with DBMS_XPLAN.DISPLAY_CURSOR get the estimated memory requirements for optimal and single pass executions in the columns "OMem", "1Mem" and "Used-Mem" of the DISPLAY_CURSOR output.
More information about using the DISPLAY_CURSOR function properly can be found here:
http://jonathanlewis.wordpress.com/2006/11/09/dbms_xplan-in-10g/
http://structureddata.org/2007/11/21/troubleshooting-bad-execution-plans/
http://rwijk.blogspot.com/2008/03/dbmsxplandisplaycursor.html
Christian Antognini points out that the TEMPSEG_SIZE information of DISPLAY_CURSOR is using the wrong units: http://antognini.ch/2009/05/wrong-information-about-temporary-space-usage/
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

"contains" and "order by" does not work in Oracle 9i

Hello All.
I have next query:
select q.*
from
(SELECT v.id, o.longname as name, v.dord,
TP.longname as TYPE_NAME, v.actualfl, o.NORD, v.version
FROM R_ORD O, R_VORD V, R_TPORD TP, R_BODY b
WHERE TP.ID = o.tp_id and v.ORD_ID = o.ID
and v.ID = b.ID(+) and v.actualfl = '1'
and CONTAINS( o.longname, 'bank%', 1) > 0
) q
ORDER BY name
It's work perfect in Oracle 8.1.7, but I can not get result of the query in Oracle 9.
If I comment
-- ORDER BY name
or
-- and CONTAINS( o.longname, 'bank%', 1) > 0
then the query return a result.
Please help.
Thanks in advance.
P.S. I use Oracle 9i SR1 and
sort_area_size = 524288
sort_area_retained_size = 0
Victor Zogin.

Description Cost Cardinality Byte
SELECT STATEMENT, GOAL = CHOOSE               6     1     1260
SORT ORDER BY               6     1     1260
COUNT
NESTED LOOPS OUTER               4     1     1260
NESTED LOOPS               8     1     1247
NESTED LOOPS               3     61     11895
TABLE ACCESS BY INDEX ROWID     OMEGA     R_TPORD     1     1     140
INDEX RANGE SCAN     OMEGA     PK_R_TPORD     1     1
TABLE ACCESS BY INDEX ROWID     OMEGA     R_VORD     2     149     8195
INDEX RANGE SCAN     OMEGA     IDX_R_VORD_ACT     1     149
TABLE ACCESS BY INDEX ROWID     OMEGA     R_ORD     8     1     1052
DOMAIN INDEX     OMEGA     CK_ORD_IDX     4     1
INDEX UNIQUE SCAN     OMEGA     PK_R_BODY          22437     291681

Addm recommendations and solution

i had recommendations from addmrpt from oracle support.please help to do step by step procedure steps
my envirom
prod-windows
two node rac
version10.2.0.4
recommendations are as follows
=== ODM Issue Verification ===
addmrpt_1_45161_45283.txt
DETAILED ADDM REPORT FOR TASK 'TASK_107501' WITH ID 107501
Analysis Period: from 19-JUN-2011 00:00 to 21-JUN-2011 13:00
Database ID/Instance: 107658090/1
Database/Instance Names: OSONDEMA/osondemand1
Host Name: INFO-IWW-COM-06
Database Version: 10.2.0.4.0
Snapshot Range: from 45161 to 45283
Database Time: 69659 seconds
Average Database Load: .3 active sessions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FINDING 1: 100% impact (221542 seconds)
Wait class "Cluster" was consuming significant database time.
NO RECOMMENDATIONS AVAILABLE
FINDING 2: 100% impact (69659 seconds)
Significant virtual memory paging was detected on the host operating system.
RECOMMENDATION 1: Host Configuration, 100% benefit (69659 seconds)
ACTION: Host operating system was experiencing significant paging but no
particular root cause could be detected. Investigate processes that
do not belong to this instance running on the host that are consuming
significant amount of virtual memory. Also consider adding more
physical memory to the host.
RECOMMENDATION 2: DB Configuration, 100% benefit (69659 seconds)
ACTION: Total PGA memory used was above the specified
"pga_aggregate_target" value for 29% of the time. Consider increasing
your current "pga_aggregate_target". Note that the sum of
"pga_aggregate_target" and SGA size should be less than the physical
memory available on the host.
RATIONALE: The value of parameter "pga_aggregate_target" was "5000 M"
during the analysis period.
FINDING 3: 45% impact (31322 seconds)
The SGA was inadequately sized, causing additional I/O or hard parses.
RECOMMENDATION 1: DB Configuration, 45% benefit (31322 seconds)
ACTION: Increase the size of the SGA by setting the parameter
"sga_target" to 8960 M.
ADDITIONAL INFORMATION:
The value of parameter "sga_target" was "5120 M" during the analysis
period.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Wait class "User I/O" was consuming significant database time.
(35% impact [24184 seconds])
solution
Hi,
Addm report shows the OS memory utilization very high and Host operating system was experiencing significant paging.
The timeframe for the report is very large from 19-JUN-2011 00:00 to 21-JUN-2011 13:00
Windows 32 bit would have limitation to memory ..
Please use below metalink note to validate the memory configuration :
Windows Memory Configuration: 32-bit and 64-bit (Doc ID 873752.1)
my friend suggested solution as follows
Please find the observations as below:
1.     Load balancing need to be done properly as report is showing the inadequate size of SGA for Node1 but not prominently for Node2
2.     Need to monitor wait class of Global services and do the tuning as required.
3.     Need to increase to SGA_TARGET after closing above two points and analysis the ADDM report and AWR report of later snap shots
please suggest me plan and steps to do above
thanks for reply

ok aman
leave all the above steps
can you guide me to do step by step procedure for below points
Please find the observations as below:
1.     Load balancing need to be done properly as report is showing the inadequate size of SGA for Node1 but not prominently for Node2
2.     Need to monitor wait class of Global services and do the tuning as required.
3.     Need to increase to SGA_TARGET after closing above two points and analysis the ADDM report and AWR report of later snap shots
Oracle Support - June 29, 2011 10:27:13 PM GMT+05:30 [Notes]
Generic Note
Hi,
Addm report shows the OS memory utilization very high and Host operating system was experiencing significant paging.
The timeframe for the report is very large from 19-JUN-2011 00:00 to 21-JUN-2011 13:00
Windows 32 bit would have limitation to memory ..
Please use below metalink note to validate the memory configuration :
Windows Memory Configuration: 32-bit and 64-bit

DBCA templates - PGA and SGA using "percentageMemTOSGA" parameter

Hi all,
I am trying to configure a DBCA template to perform silent database creations on servers at our client sites. The amount of RAM could vary from server to server. For this reason, I am specifying the following parameters:
customSGA=false
percentageMemTOSGA=70In principle, this works pretty well - my DB is created with a suitable value for SGA_TARGET based on the RAM available on the server. However, the value that it uses for PGA_AGGREGATE_TARGET is too small for our needs. From experience, we can get by with a smaller SGA, but we need a relatively large PGA.
I have tried specifying the parameter "pga_aggregate_target" in the template (and thus trying to "override" the decision of DBCA) but DBCA ignores my "hard-coded" value for this and sets pga_aggregate_target according to (presumably) some calculation based on:
- The amount of RAM available
- The value of "percentageMemTOSGA"
- Some "other" value which tells DBCA how to divide up the %age memory it will take between SGA and PGA
So, my question is:
Does anybody know how to effectively use both "percentageMemTOSGA", and:
EITHER:
* tell DBCA how to split the memory that it will use from RAM (in this case 70%) between pga_aggregate_target and sga_target (some parameter maybe like "percent_to_pga" and "percent_to_sga")
OR (not as useful but better than no control):
* specify explicitly a value (or percentage) for pga_aggregate_target, but leave the value of sga_target to be decided based on the percentageMemTOSGA
I hope I've explained that well enough...
Regards,
Ados

I've checked the help for dbca (I'm currently running from the command prompt in "silent" mode) and don't see anything about recording the creation - how would I do that? Or are you referring to using the GUI, creating a database, and then saving the template? If it's that, that's what I did first, then editing the template for my tests - I don't see the parameter(s) that I'm looking for in the template.Ados,
I did the same what you did. Run dbca in GUI mode and generate template only now in template file I see there is a parameter to set these value. For your reference I am posting the content of that file:
<?xml version = '1.0'?>
<DatabaseTemplate name="orcl" description="" version="10.2.0.3.0">
<CommonAttributes>
<option name="ISEARCH" value="false"/>
<option name="OMS" value="false"/>
<option name="JSERVER" value="true"/>
<option name="SPATIAL" value="true"/>
<option name="ODM" value="true">
<tablespace id="SYSAUX"/>
</option>
<option name="IMEDIA" value="true"/>
<option name="XDB_PROTOCOLS" value="true">
<tablespace id="SYSAUX"/>
</option>
<option name="ORACLE_TEXT" value="true">
<tablespace id="SYSAUX"/>
</option>
<option name="SAMPLE_SCHEMA" value="true"/>
<option name="CWMLITE" value="true">
<tablespace id="SYSAUX"/>
</option>
<option name="EM_REPOSITORY" value="true">
<tablespace id="SYSAUX"/>
</option>
<option name="HTMLDB" value="false"/>
</CommonAttributes>
<Variables/>
<CustomScripts Execute="false"/>
<InitParamAttributes>
<InitParams>
*<initParam name="pga_aggregate_target" value="808" unit="MB"/>*
<initParam name="processes" value="150"/>
<initParam name="db_recovery_file_dest_size" value="1024" unit="MB"/>
<initParam name="control_files" value="("{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/control01.ctl", "{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/control02.ctl", "{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/control03.ctl")"/>
<initParam name="sga_target" value="1536" unit="MB"/>
<initParam name="compatible" value="10.2.0.3.0"/>
<initParam name="background_dump_dest" value="{ORACLE_BASE}/admin/{DB_UNIQUE_NAME}/bdump"/>
<initParam name="job_queue_processes" value="10"/>
<initParam name="db_name" value="orcl"/>
<initParam name="user_dump_dest" value="{ORACLE_BASE}/admin/{DB_UNIQUE_NAME}/udump"/>
<initParam name="dispatchers" value="(PROTOCOL=TCP) (SERVICE={SID}XDB)"/>
<initParam name="audit_file_dest" value="{ORACLE_BASE}/admin/{DB_UNIQUE_NAME}/adump"/>
<initParam name="db_domain" value=""/>
<initParam name="open_cursors" value="300"/>
<initParam name="db_block_size" value="8" unit="KB"/>
<initParam name="db_recovery_file_dest" value="{ORACLE_BASE}/flash_recovery_area"/>
<initParam name="undo_tablespace" value="UNDOTBS1"/>
<initParam name="core_dump_dest" value="{ORACLE_BASE}/admin/{DB_UNIQUE_NAME}/cdump"/>
<initParam name="remote_login_passwordfile" value="EXCLUSIVE"/>
<initParam name="undo_management" value="AUTO"/>
<initParam name="db_file_multiblock_read_count" value="16"/>
</InitParams>
<MiscParams>
<databaseType>MULTIPURPOSE</databaseType>
<maxUserConn>20</maxUserConn>
<percentageMemTOSGA>40</percentageMemTOSGA>
<customSGA>true</customSGA>
<archiveLogMode>false</archiveLogMode>
<initParamFileName>{ORACLE_BASE}/admin/{DB_UNIQUE_NAME}/pfile/init.ora</initParamFileName>
</MiscParams>
<SPfile useSPFile="true">{ORACLE_HOME}/dbs/spfile{SID}.ora</SPfile>
</InitParamAttributes>
<StorageAttributes>
<DataFiles>
<Location>{ORACLE_HOME}/assistants/dbca/templates/Seed_Database.dfb</Location>
<SourceDBName>seeddata</SourceDBName>
<Name id="1" Tablespace="SYSTEM" Contents="PERMANENT" Size="480" autoextend="true" blocksize="8192">{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/system01.dbf</Name>
<Name id="2" Tablespace="UNDOTBS1" Contents="UNDO" Size="25" autoextend="true" blocksize="8192">{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/undotbs01.dbf</Name>
<Name id="3" Tablespace="SYSAUX" Contents="PERMANENT" Size="240" autoextend="true" blocksize="8192">{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/sysaux01.dbf</Name>
<Name id="4" Tablespace="USERS" Contents="PERMANENT" Size="5" autoextend="true" blocksize="8192">{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/users01.dbf</Name>
</DataFiles>
<TempFiles>
<Name id="1" Tablespace="TEMP" Contents="TEMPORARY" Size="20">{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/temp01.dbf</Name>
</TempFiles>
<ControlfileAttributes id="Controlfile">
<maxDatafiles>100</maxDatafiles>
<maxLogfiles>16</maxLogfiles>
<maxLogMembers>3</maxLogMembers>
<maxLogHistory>1</maxLogHistory>
<maxInstances>8</maxInstances>
<image name="control01.ctl" filepath="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/"/>
<image name="control02.ctl" filepath="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/"/>
<image name="control03.ctl" filepath="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/"/>
</ControlfileAttributes>
<RedoLogGroupAttributes id="1">
<reuse>false</reuse>
<fileSize unit="KB">51200</fileSize>
<Thread>1</Thread>
<member ordinal="0" memberName="redo01.log" filepath="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/"/>
</RedoLogGroupAttributes>
<RedoLogGroupAttributes id="2">
<reuse>false</reuse>
<fileSize unit="KB">51200</fileSize>
<Thread>1</Thread>
<member ordinal="0" memberName="redo02.log" filepath="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/"/>
</RedoLogGroupAttributes>
<RedoLogGroupAttributes id="3">
<reuse>false</reuse>
<fileSize unit="KB">51200</fileSize>
<Thread>1</Thread>
<member ordinal="0" memberName="redo03.log" filepath="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/"/>
</RedoLogGroupAttributes>
</StorageAttributes>
</DatabaseTemplate>
Regards.

Help needed for hash_area_size setting for Datawarehouse environment

We have an Oracle 10g Datawarehousing environment , running on 3 - node RAC
with 16 GB RAM & 4 CPUs each and roughly we have 200 users and night jobs running on this D/W .
We find that query performance of all ETL Processes & joins are quite slow .
How much should we increase the value of hash_area_size parameter for this Datawarehouse environment ? This is a Production database, with Oracle Database 10g Enterprise Edition Release 10.1.0.5.0.
We use OWB 10g Tool for this D/W and we need to change the hash_area_size to increase the performance of the ETL Processes.
This is the Oracle init parameter settings used, as shown below : -
Kindly suggest ,
Thanks & best regards ,
===========================================================
     ORBIT
__db_cache_size     1073741824
__java_pool_size     67108864
__large_pool_size     318767104
__shared_pool_size     1744830464
optimizercost_based_transformation     OFF
active_instance_count
aq_tm_processes     1
archive_lag_target     0
asm_diskgroups
asm_diskstring
asm_power_limit     1
audit_file_dest     /dboracle/orabase/product/10.1.0/rdbms/audit
audit_sys_operations     FALSE
audit_trail     NONE
background_core_dump     partial
background_dump_dest     /dborafiles/orbit/ORBIT01/admin/bdump
backup_tape_io_slaves     TRUE
bitmap_merge_area_size     1048576
blank_trimming     FALSE
buffer_pool_keep
buffer_pool_recycle
circuits
cluster_database     TRUE
cluster_database_instances     3
cluster_interconnects
commit_point_strength     1
compatible     10.1.0
control_file_record_keep_time     90
control_files     #NAME?
core_dump_dest     /dborafiles/orbit/ORBIT01/admin/cdump
cpu_count     4
create_bitmap_area_size     8388608
create_stored_outlines
cursor_sharing     EXACT
cursor_space_for_time     FALSE
db_16k_cache_size     0
db_2k_cache_size     0
db_32k_cache_size     0
db_4k_cache_size     0
db_8k_cache_size     0
db_block_buffers     0
db_block_checking     FALSE
db_block_checksum     TRUE
db_block_size     8192
db_cache_advice     ON
db_cache_size     1073741824
db_create_file_dest     #NAME?
db_create_online_log_dest_1     #NAME?
db_create_online_log_dest_2     #NAME?
db_create_online_log_dest_3
db_create_online_log_dest_4
db_create_online_log_dest_5
db_domain
db_file_multiblock_read_count     64
db_file_name_convert
db_files     999
db_flashback_retention_target     1440
db_keep_cache_size     0
db_name     ORBIT
db_recovery_file_dest     #NAME?
db_recovery_file_dest_size     2.62144E+11
db_recycle_cache_size     0
db_unique_name     ORBIT
db_writer_processes     1
dbwr_io_slaves     0
ddl_wait_for_locks     FALSE
dg_broker_config_file1     /dboracle/orabase/product/10.1.0/dbs/dr1ORBIT.dat
dg_broker_config_file2     /dboracle/orabase/product/10.1.0/dbs/dr2ORBIT.dat
dg_broker_start     FALSE
disk_asynch_io     TRUE
dispatchers
distributed_lock_timeout     60
dml_locks     9700
drs_start     FALSE
enqueue_resources     10719
event
fal_client
fal_server
fast_start_io_target     0
fast_start_mttr_target     0
fast_start_parallel_rollback     LOW
file_mapping     FALSE
fileio_network_adapters
filesystemio_options     asynch
fixed_date
gc_files_to_locks
gcs_server_processes     2
global_context_pool_size
global_names     FALSE
hash_area_size     131072
hi_shared_memory_address     0
hpux_sched_noage     0
hs_autoregister     TRUE
ifile
instance_groups
instance_name     ORBIT01
instance_number     1
instance_type     RDBMS
java_max_sessionspace_size     0
java_pool_size     67108864
java_soft_sessionspace_limit     0
job_queue_processes     10
large_pool_size     318767104
ldap_directory_access     NONE
license_max_sessions     0
license_max_users     0
license_sessions_warning     0
local_listener
lock_name_space
lock_sga     FALSE
log_archive_config
log_archive_dest
log_archive_dest_1     LOCATION=+ORBT_A06635_DATA1_ASM/ORBIT/ARCHIVELOG/
log_archive_dest_10
log_archive_dest_2
log_archive_dest_3
log_archive_dest_4
log_archive_dest_5
log_archive_dest_6
log_archive_dest_7
log_archive_dest_8
log_archive_dest_9
log_archive_dest_state_1     enable
log_archive_dest_state_10     enable
log_archive_dest_state_2     enable
log_archive_dest_state_3     enable
log_archive_dest_state_4     enable
log_archive_dest_state_5     enable
log_archive_dest_state_6     enable
log_archive_dest_state_7     enable
log_archive_dest_state_8     enable
log_archive_dest_state_9     enable
log_archive_duplex_dest
log_archive_format     %t_%s_%r.arc
log_archive_local_first     TRUE
log_archive_max_processes     2
log_archive_min_succeed_dest     1
log_archive_start     FALSE
log_archive_trace     0
log_buffer     1167360
log_checkpoint_interval     0
log_checkpoint_timeout     1800
log_checkpoints_to_alert     FALSE
log_file_name_convert
logmnr_max_persistent_sessions     1
max_commit_propagation_delay     700
max_dispatchers
max_dump_file_size     UNLIMITED
max_enabled_roles     150
max_shared_servers
nls_calendar
nls_comp
nls_currency     #
nls_date_format     DD-MON-RRRR
nls_date_language     ENGLISH
nls_dual_currency     ?
nls_iso_currency     UNITED KINGDOM
nls_language     ENGLISH
nls_length_semantics     BYTE
nls_nchar_conv_excp     FALSE
nls_numeric_characters
nls_sort
nls_territory     UNITED KINGDOM
nls_time_format     HH24.MI.SSXFF
nls_time_tz_format     HH24.MI.SSXFF TZR
nls_timestamp_format     DD-MON-RR HH24.MI.SSXFF
nls_timestamp_tz_format     DD-MON-RR HH24.MI.SSXFF TZR
O7_DICTIONARY_ACCESSIBILITY     FALSE
object_cache_max_size_percent     10
object_cache_optimal_size     102400
olap_page_pool_size     0
open_cursors     1024
open_links     4
open_links_per_instance     4
optimizer_dynamic_sampling     2
optimizer_features_enable     10.1.0.5
optimizer_index_caching     0
optimizer_index_cost_adj     100
optimizer_mode     ALL_ROWS
os_authent_prefix     ops$
os_roles     FALSE
parallel_adaptive_multi_user     TRUE
parallel_automatic_tuning     TRUE
parallel_execution_message_size     4096
parallel_instance_group
parallel_max_servers     80
parallel_min_percent     0
parallel_min_servers     0
parallel_server     TRUE
parallel_server_instances     3
parallel_threads_per_cpu     2
pga_aggregate_target     8589934592
plsql_code_type     INTERPRETED
plsql_compiler_flags     INTERPRETED
plsql_debug     FALSE
plsql_native_library_dir
plsql_native_library_subdir_count     0
plsql_optimize_level     2
plsql_v2_compatibility     FALSE
plsql_warnings     DISABLE:ALL
pre_page_sga     FALSE
processes     600
query_rewrite_enabled     TRUE
query_rewrite_integrity     enforced
rdbms_server_dn
read_only_open_delayed     FALSE
recovery_parallelism     0
remote_archive_enable     TRUE
remote_dependencies_mode     TIMESTAMP
remote_listener
remote_login_passwordfile     EXCLUSIVE
remote_os_authent     FALSE
remote_os_roles     FALSE
replication_dependency_tracking     TRUE
resource_limit     FALSE
resource_manager_plan
resumable_timeout     0
rollback_segments
serial_reuse     disable
service_names     ORBIT
session_cached_cursors     0
session_max_open_files     10
sessions     2205
sga_max_size     3221225472
sga_target     3221225472
shadow_core_dump     partial
shared_memory_address     0
shared_pool_reserved_size     102760448
shared_pool_size     318767104
shared_server_sessions
shared_servers     0
skip_unusable_indexes     TRUE
smtp_out_server
sort_area_retained_size     0
sort_area_size     65536
sp_name     ORBIT
spfile     #NAME?
sql_trace     FALSE
sql_version     NATIVE
sql92_security     FALSE
sqltune_category     DEFAULT
standby_archive_dest     ?/dbs/arch
standby_file_management     MANUAL
star_transformation_enabled     TRUE
statistics_level     TYPICAL
streams_pool_size     0
tape_asynch_io     TRUE
thread     1
timed_os_statistics     0
timed_statistics     TRUE
trace_enabled     TRUE
tracefile_identifier
transactions     2425
transactions_per_rollback_segment     5
undo_management     AUTO
undo_retention     7200
undo_tablespace     UNDOTBS1
use_indirect_data_buffers     FALSE
user_dump_dest     /dborafiles/orbit/ORBIT01/admin/udump
utl_file_dir     /orbit_serial/oracle/utl_out
workarea_size_policy     AUTO

The parameters are already unset in the environment, but do show up in v$parameter, much like shared_pool_size is visible in v$parameter despite only sga_target being set.
SQL> show parameter sort
NAME TYPE VALUE
sortelimination_cost_ratio integer 5
nls_sort string binary
sort_area_retained_size integer 0
sort_area_size integer 65536
SQL> show parameter hash
NAME TYPE VALUE
hash_area_size integer 131072
SQL> exit
Only set hash_area_size and sort_area_size should only be set when not using automatic undo, which is not supported in EBS databases.
Database Initialization Parameters for Oracle Applications 11i
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=216205.1

Creating database problem with ORA-01519: error while processing file '' ne

Dear all,
I am having rough time with creating database manually. can anyone help me with the following errors.
ALERT LOGFILE:-
Sun May 31 12:00:39 2009
Errors in file d:\oracle\product\10.1.0\admin\oracle5\udump\oracle5_ora_3444.trc:
ORA-01501: CREATE DATABASE failed
ORA-01519: error while processing file '%ORACLE_HOME%\RDBMS\ADMIN\SQL.BSQ' near line 5744
ORA-00604: error occurred at recursive SQL level 1
ORA-01119: error in creating database file 'D:\oracle\product\10.1.0\oradata\ORACLE5 \datafile\undotbs1.dbf'
ORA-27040: file create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Error 1519 happened during db open, shutting down database
USER: terminating instance due to error 1519
Sun May 31 12:00:39 2009
Errors in file d:\oracle\product\10.1.0\admin\oracle5\bdump\oracle5_reco_3416.trc:
ORA-01519: error while processing file '' near line
CREATE DATABASE SCRIPT:-
create database ORACLE5
user sys identified by bala
user system identified by bala
logfile
group 1 ('D:\oracle\product\10.1.0\oradata\ORACLE5\logfile\redo01.log') SIZE 50M,
group 2 ('D:\oracle\product\10.1.0\oradata\ORACLE5\logfile\redo02.log') SIZE 50M,
group 3 ('D:\oracle\product\10.1.0\oradata\ORACLE5\logfile\redo03.log') SIZE 50M
maxlogfiles 5
maxlogmembers 5
maxloghistory 1
maxdatafiles 50
maxinstances 1
datafile 'D:\oracle\product\10.1.0\oradata\ORACLE5\datafile\system01.dbf' size 200m autoextend on maxsize unlimited extent management local
undo tablespace UNDOTBS1 datafile 'D:\oracle\product\10.1.0\oradata\ORACLE5 \datafile\undotbs1.dbf' size 10m autoextend on maxsize unlimited
sysaux datafile 'D:\oracle\product\10.1.0\oradata\ORACLE5\datafile\sysaux01.dbf' size 100m autoextend on maxsize unlimited
default temporary tablespace temp tempfile 'D:\oracle\product\10.1.0\oradata\ORACLE5 \datafile\temp01.dbf' size 10m autoextend on maxsize unlimited
character set US7ASCII
NATIONAL CHARACTER SET AL16UTF16
INIT.ORA FILE:-
# Copyright (c) 1991, 2001, 2002 by Oracle Corporation
# Archive
log_archive_format=ARC%S_%R.%T
# Cache and I/O
db_block_size=8192
db_cache_size=25165824
db_file_multiblock_read_count=16
# Cursors and Library Cache
open_cursors=300
# Database Identification
db_domain=""
db_name=oracle5
# Diagnostics and Statistics
background_dump_dest=D:\oracle\product\10.1.0\admin\oracle5\bdump
core_dump_dest=D:\oracle\product\10.1.0\admin\oracle5\cdump
user_dump_dest=D:\oracle\product\10.1.0\admin\oracle5\udump
# File Configuration
#db_create_file_dest=D:\oracle\product\10.1.0\oradata
db_recovery_file_dest=D:\oracle\product\10.1.0\flash_recovery_area
db_recovery_file_dest_size=2147483648
# Job Queues
job_queue_processes=10
# Miscellaneous
compatible=10.1.0.2.0
# Pools
java_pool_size=50331648
large_pool_size=8388608
shared_pool_size=83886080
# Processes and Sessions
processes=150
# Security and Auditing
remote_login_passwordfile=EXCLUSIVE
# Shared Server
dispatchers="(PROTOCOL=TCP) (SERVICE=oracle5XDB)"
# Sort, Hash Joins, Bitmap Indexes
pga_aggregate_target=25165824
sort_area_size=65536
# System Managed Undo and Rollback Segments
undo_management=AUTO
undo_tablespace=UNDOTBS1
control_files=("D:\ORACLE\PRODUCT\10.1.0\ORADATA\ORACLE5\CONTROLFILE\control01.CTL", "D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORACLE5\CONTROLFILE\control02.CTL")

Hi,
undo tablespace UNDOTBS1 datafile 'D:\oracle\product\10.1.0\oradata\ORACLE5 \datafile\undotbs1.dbf' size 10m autoextend on maxsize unlimited
After ORACLE5 there is a space character. Typo? Create proper directory or delete this character.
Bartek

Error message when creating new database

Hi, i am trying to create a new database for the first time but keep getting an error. Ive been through the create statement several times and it all looks good to me.Any help would be greatly appreciated !
The error im getting is :
ORA-00604: error occurred at recursive SQL level 2
ORA-00942: table or view does not exist
Fri Dec 9 22:54:10 2011
Errors in file /u03/app/oracle/admin/OPS/udump/ops_ora_59850.trc:
ORA-01501: CREATE DATABASE failed
ORA-01519: error while processing file '?/rdbms/admin/sql.bsq' near line 5608
ORA-00604: error occurred at recursive SQL level 2
ORA-00942: table or view does not exist
Fri Dec 9 22:54:10 2011
Error 1519 happened during db open, shutting down database
USER: terminating instance due to error 1519
Instance terminated by USER, pid = 59850
ORA-1092 signalled during: CREATE DATABASE OPS
Here is my create database statement:
CREATE DATABASE OPS
USER SYS IDENTIFIED BY pz6r58
USER SYSTEM IDENTIFIED BY y1tz5p
LOGFILE GROUP 1 ('/u98/oradata/OPS/redo01.log') SIZE 30M,
GROUP 2 ('/u98/oradata/OPS/redo02.log') SIZE 30M
MAXLOGFILES 5
MAXLOGMEMBERS 5
MAXLOGHISTORY 1
MAXDATAFILES 100
MAXINSTANCES 1
CHARACTER SET US7ASCII
NATIONAL CHARACTER SET AL16UTF16
DATAFILE '/u02/oradata/OPS/system01.dbf' SIZE 30M REUSE
EXTENT MANAGEMENT LOCAL
SYSAUX DATAFILE '/u02/oradata/OPS/sysaux01.dbf' SIZE 30M REUSE
DEFAULT TABLESPACE tbs01
DATAFILE '/u07/oradata/OPS/tbs01.dbf' SIZE 325M REUSE
DEFAULT TEMPORARY TABLESPACE temp01
TEMPFILE '/u07/oradata/OPS/temp01.dbf'
SIZE 20M REUSE
UNDO TABLESPACE undotbs01
DATAFILE '/u07/oradata/OPS/undotbs01.dbf'
Size 50m reuse;
Here is my pfile
db_block_size=8192
db_cache_size=25165824
db_file_multiblock_read_count=16
open_cursors=300
db_domain=world
db_name=OPS
background_dump_dest=/u03/app/oracle/admin/OPS/bdump
core_dump_dest=/u03/app/oracle/admin/OPS/cdump
timed_statistics=TRUE
user_dump_dest=/u03/app/oracle/admin/OPS/udump
control_files=("/u02/oradata/OPS/control01.ctl", "/u05/oradata/OPS/control02.ctl", "/u06/oradata/OPS/control03.ctl")
rollback_segments = (RBS01,RBS02,RBS03)
os_authent_prefix = ""
instance_name=OPS
compatible=10.2.0.0.0
#hash_join_enabled=TRUEa = obsolete in 10.2
query_rewrite_enabled=FALSE
star_transformation_enabled=FALSE
java_pool_size=0
large_pool_size=0
#large_pool_size=8388608
#shared_pool_size=36700160
shared_pool_size=76700160
#large_pool_size=8388608
#java_pool_size=150000000
#shared_pool_size=187928166
streams_pool_size=50331648
processes=150
session_max_open_files=20
fast_start_mttr_target=300
remote_login_passwordfile=EXCLUSIVE
pga_aggregate_target=25165824
sort_area_size=65536
rollback_segments = (RBS01,RBS02,RBS03)
undo_management=auto
undo_tablespace=UNDO_TS
#undo_retention=10800
Many thanks

Refer this MOS ID *CREATE DATABASE Statement Fails With ORA-1501 ORA-1519 ORA-604 ORA-942 Errors [ID 434557.1]*
Increase the size of SYSAUX tablespace in the CREATE DATABASE statement.
The SYSAUX tablespace needs to be at least 240 MB at the time of database creation. The space requirements of the SYSAUX tablespace will increase after the database is fully deployed
Also the size of the system tablespace should be more and not to 30 MB as in your case

Oracle 9i running out of memory

Folks !
I have a simple 3 table schema with a few thousand entries each. After dedicating gigabytes of hard disk space and 50% of my 1+ GB memory, I do a few simple Oracle Text "contains" searches (see below) on these tables and oracle seems to grow some 25 MB after each query (which typically return less than a dozen rows each) till it eventually runs out of memory and I have to reboot the system (Sun Solaris).
This is on Solaris 9/Sparc with Oracle 9.2 . My query is simple right outer join. I think the memory growth is related to Oracle Text index/caching since memory utilization seems pretty stable with simple like '%xx%' queries.
"top" shows a dozen or so processes each with about 400MB RSS/SIZE. It has been a while since I did Oracle DBA work but I am nothing special here. Databse has all the default settings that you get when you create an Oracle database.
I have played with SGA sizes and no matter how large or small the size of SGA/PGA, Oracle runs out of memory and crashes the system. Pretty stupid to an Enterprise databas to die like that.
Any clue on how to arrest the fatal growth of memory for Oracle 9i r2?
thanks a lot.
-Sanjay
PS: The query is:
SELECT substr(sdn_name,1,32) as name, substr(alt_name,1,32) as alt_name, sdn.ent_num, alt_num, score(1), score(2)
FROM sdn, alt
where sdn.ent_num = alt.ent_num(+)
and (contains(sdn_name,'$BIN, $LADEN',1) > 0 or
contains(alt_name,'$BIN, $LADEN',2) > 0)
order by ent_num, score(1), score(2) desc;
There are following two indexes on the two tables:
create index sdn_name on sdn(sdn_name) indextype is ctxsys.context;
create index alt_name on alt(alt_name) indextype is ctxsys.context;

I am already using MTS.
Atached is the init.ora file below.
may be I should repost this article with subject "memory leak in Oracle" to catch developer attention. I posted this a few weeks back in Oracle Text groiup and no response there either.
Thanks for you help.
-Sanjay
# Copyright (c) 1991, 2001, 2002 by Oracle Corporation
# Cache and I/O
db_block_size=8192
db_cache_size=33554432
db_file_multiblock_read_count=16
# Cursors and Library Cache
open_cursors=300
# Database Identification
db_domain=""
db_name=ofac
# Diagnostics and Statistics
background_dump_dest=/space/oracle/admin/ofac/bdump
core_dump_dest=/space/oracle/admin/ofac/cdump
timed_statistics=TRUE
user_dump_dest=/space/oracle/admin/ofac/udump
# File Configuration
control_files=("/space/oracle/oradata/ofac/control01.ctl", "/space/oracle/oradata/ofac/control02.ctl", "/space/oracle/oradata/ofac/control03.ctl")
# Instance Identification
instance_name=ofac
# Job Queues
job_queue_processes=10
# MTS
dispatchers="(PROTOCOL=TCP) (SERVICE=ofacXDB)"
# Miscellaneous
aq_tm_processes=1
compatible=9.2.0.0.0
# Optimizer
hash_join_enabled=TRUE
query_rewrite_enabled=FALSE
star_transformation_enabled=FALSE
# Pools
java_pool_size=117440512
large_pool_size=16777216
shared_pool_size=117440512
# Processes and Sessions
processes=150
# Redo Log and Recovery
fast_start_mttr_target=300
# Security and Auditing
remote_login_passwordfile=EXCLUSIVE
# Sort, Hash Joins, Bitmap Indexes
pga_aggregate_target=25165824
sort_area_size=524288
# System Managed Undo and Rollback Segments
undo_management=AUTO
undo_retention=10800
undo_tablespace=UNDOTBS1

Oracle 11g - Memory used for sorting

Hi everyone,
I would like to know how I could analyze memory used for sorting in Oracle 11g. When I run the below query, it returns 1531381.
select value from v$sysstat where name like 'sorts (memory)';But when I check sort_area_size parameter from v$parameter, it returns 65536. Does it mean my database is using more memory for sorting than sort_area_size. Or is the way I interpret v$sysstat view and sort_area_size wrong? What is the best way to monitor the memory usage for sorting? Thanks in advance.
Regards,
K.H
Edited by: K Hein on Apr 5, 2012 8:16 PM

check the valuse of pga_aggregate_target
http://docs.oracle.com/cd/B19306_01/server.102/b14237/initparams157.htm
Note:
Oracle does not recommend using the SORT_AREA_SIZE parameter unless the instance is configured with the shared server option. Oracle recommends that you enable automatic sizing of SQL working areas by setting PGA_AGGREGATE_TARGET instead. SORT_AREA_SIZE is retained for backward compatibility.
What is the best way to monitor the memory usage for sorting? try v$sort_usage
or v$tempseg_usage
col sid_serial for a44
col size for a22
col SID_SERIAL for a22
SELECT b.tablespace,
        ROUND(((b.blocks*p.value)/1024/1024),2)||' MB' "SIZE",
        a.sid||','||a.serial# SID_SERIAL,
        a.username,a.osuser,
        a.program
   FROM sys.v_$session a,
        sys.v_$sort_usage b,
        sys.v_$parameter p
WHERE p.name = 'db_block_size'
    AND a.saddr = b.session_addr
ORDER BY b.blocks;

Pga_aggregate_target and sort_area_size

Similar Messages

Maybe you are looking for