Resizing resize db_cache_size parameter

Hi
i'm facing problem of IO and taking statspack report and analyzing it from statspackanalyzer they are advising me to increase db_cache_size to avoid many full table scans. could you help me on how to check an appropriate value of my db_cache_size as my configuration is below:
OS RHEL 4
RAM: 4 Gb
CPU: 8 X Intel(R) Xeon(TM) CPU 3.20GHz
Oracle dabatsae server 9.2.0.4
My actual SGA is
SQL> sho sga
Total System Global Area 957945792 bytes
Fixed Size 452544 bytes
Variable Size 150994944 bytes
Database Buffers 805306368 bytes
Redo Buffers 1191936 bytes
db_cache_size = 805306368
shared_pool_size = 50331648
log_buffer = 1048576
And the v$db_cache_size_advice show me the below output.
80 10010 1.3576 1442537193
160 20020 1.3063 1387963597
240 30030 1.2798 1359825236
320 40040 1.2475 1325527521
400 50050 1.2078 1283381091
480 60060 1.164 1236834685
560 70070 1.115 1184781753
640 80080 1.0636 1130102023
720 90090 1.0224 1086346464
768 96096 1 1062540512 (Current)
800 100100 .9814 1042794822
880 110110 .9547 1014390821
960 120120 .9343 992724772
1,040 130130 .8642 918284631
1,120 140140 .7784 827123440
1,200 150150 .767 814920392
1,280 160160 .7597 807265044
1,360 170170 .7539 801045972
1,440 180180 .7493 796205111
1,520 190190 .7456 792210522
1,600 200200 .7414 787812228
Thanks for your help.

Background Wait Events for DB: GABON Instance: gabon Snaps: 12 -13
-> ordered by wait time desc, waits desc (idle events last)
Avg
Total Wait wait Waits
Event Waits Timeouts Time (s) (ms) /txn
control file parallel write 1,155 0 434 375 0.5
db file scattered read 222 0 47 212 0.1
control file sequential read 773 0 25 33 0.4
db file sequential read 77 0 3 40 0.0
log file parallel write 3,246 2,812 0 0 1.5
db file parallel write 3,104 0 0 0 1.4
rdbms ipc reply 2 0 0 21 0.0
db file single write 4 0 0 11 0.0
log buffer space 6 0 0 4 0.0
log file single write 2 0 0 6 0.0
log file sequential read 2 0 0 4 0.0
direct path read 1,692 0 0 0 0.8
direct path write 440 0 0 0 0.2
latch free 6 1 0 0 0.0
LGWR wait for redo copy 38 0 0 0 0.0
rdbms ipc message 16,736 5,965 19,462 1163 7.6
pmon timer 1,432 1,432 3,562 2488 0.6
smon timer 12 11 3,330 ###### 0.0
SQL ordered by Gets for DB: GABON Instance: gabon Snaps: 12 -13
-> End Buffer Gets Threshold: 10000
-> Note that resources reported for PL/SQL includes the resources used by
all SQL statements called within the PL/SQL code. As individual SQL
statements are also reported, it is possible and valid for the summed
total % to exceed 100
CPU Elapsd
Buffer Gets Executions Gets per Exec %Total Time (s) Time (s) Hash Value
16,712,841 1 16,712,841.0 37.0 771.56 2430.22 2643858346
Module: sqlservr.exe
SELECT max(startdate) maxstartdate FROM in_cdr
1,628,702 1 1,628,702.0 3.6 308.91 429.15 3952595216
Module: TOAD 8.6.0.38
select trunc(startdate) reportdate, count(*) calls, sum(duration
) actualsecs, sum(cost) revenue, sum(balancebefore-balanceafter)
calculated_revenue from in_cdr partition(incdr_2010_0401) grou
p by trunc(startdate) union select trunc(startdate) reportdate,
count(*) calls, sum(duration) actualsecs, sum(cost) revenue, sum
1,529,024 1 1,529,024.0 3.4 93.13 567.55 1639719688
Module: sqlservr.exe
SELECT max(startdate) maxstartdate FROM voucher_cdr
952,565 303 3,143.8 2.1 31.82 264.22 485362562
Module: sqlldr@cdranalysis (TNS V1-V3)
INSERT INTO IN_CDR (ANUMBER,BNUMBER,STARTDATE,TIMEZONE,DURATIO
N,CURRENCYTYPE,COST,DEDICATEDACCUSED,BALANCEAFTER,TRAFFICCASE,TE
LESERVICECODE,LOCATION,DATAVOLUME,NUMBEROFEVENTS,FAFINDICATOR,NE
TWORKID,SERVICEPROVIDERID,SERVICECLASS,ACCOUNTGROUPID,SERVICEOFF
ERINGS,SELECTEDCOMMUNITYID,BALANCEBEFORE,BALANCEDEDICATEDAFTER,B
773,681 3 257,893.7 1.7 30.16 477.10 1041979289
Module: SQL*Plus
begin processairdata; end;
679,361 1 679,361.0 1.5 80.05 124.50 4241315052
Module: sqlservr.exe
Select * from SYSADM.subscriberdump where trunc(startdate)= t
runc(sysdate)-1
612,387 1 612,387.0 1.4 36.62 91.01 3058615587
Module: sqlservr.exe
select startdate,ServiceclassID,subscriberidmsisdn from Subscrib
erDump where startdate = to_date('2010-06-07','YYYY-MM-DD') and
subscriberimsi is not null and accountactivatedflag=1
292,140 32,640 9.0 0.6 11.84 419.64 1609964435
Module: SQL*Plus
INSERT INTO ADJUSTMENT_CDR ( NOMINALAMOUNT, MSISDN, S
ERVICECLASSID, ORIGINNODEID, ORIGINOPERATORID, DESCRIPTION
, DESCRIPTION2, AMOUNTDA1, AMOUNTDA2, AMOUNTDA3, AMOUNT
DA4, AMOUNTDA5, startdate, sequencenumber, FILEID )
VALUES ( :b15 , :b14 , :b13 , :b12 , :b11 , :b10 ,
194,749 3 64,916.3 0.4 5.11 5.42 2839087957
Module: SQL*Plus
SELECT ACDR.transactionamount , ACDR.accountnumber ,
SQL ordered by Gets for DB: GABON Instance: gabon Snaps: 12 -13
-> End Buffer Gets Threshold: 10000
-> Note that resources reported for PL/SQL includes the resources used by
all SQL statements called within the PL/SQL code. As individual SQL
statements are also reported, it is possible and valid for the summed
total % to exceed 100
CPU Elapsd
Buffer Gets Executions Gets per Exec %Total Time (s) Time (s) Hash Value
ACDR.serviceclasscurrent , ACDR.originhostname ,
ACDR.originoperatorid , ACDR.externaldata1, ACDR.ex
ternaldata2, ACDR.origintimestamp , ACDR.localsequ
encenumber, ACDR.ADJUSTMENTAMOUNTDEDICATED1, ACDR.
184,394 34,508 5.3 0.4 5.96 5.96 2453141568
Module: SQL*Plus
DELETE from AIR_CDR where ROWID = :b1
141,583 39 3,630.3 0.3 3.03 3.93 169629744
Module: sqlldr@cdranalysis (TNS V1-V3)
INSERT INTO AIR_CDR (ORIGINNODETYPE,ORIGINHOSTNAME,ORIGINFILEI
D,ORIGINTRANSACTIONID,ORIGINOPERATORID,ORIGINTIMESTAMP,HOSTNAME,
LOCALSEQUENCENUMBER,TIMESTAMP,SERVICECLASSCURRENT,TRANSACTIONTYP
E,TRANSACTIONCODE,TRANSACTIONAMOUNT,TRANSACTIONAMOUNTDEDICATED1,
TRANSACTIONAMOUNTDEDICATED2,TRANSACTIONAMOUNTDEDICATED3,TRANSACT
111,639 1 111,639.0 0.2 4.89 121.06 1973241403
Module: SQL*Plus
select * from msi_space
84,898 3 28,299.3 0.2 2.47 2.57 1562134355
Module: SQL*Plus
SELECT ACDR.subscribernumber , ACDR.origintimestamp ,
ACDR.VOUCHERSERIALNUMBER , ACDR.transactionamount,
ACDR.RECHARGEAMOUNTMARKET, ACDR.VOUCHERGROUP, ACDR
.localsequencenumber, ACDR.FILEID from AIR_CDR ACDR where
ACDR.INSERTED = 'N' and ACDR.originnodetype IN ( 'IVR', 'UGW'
63,675 8,205 7.8 0.1 2.49 2.19 4143084494
select privilege#,level from sysauth$ connect by grantee#=prior
privilege# and privilege#>0 start with grantee#=:1 and privilege
#>0
50,394 1 50,394.0 0.1 3.07 9.26 4130194716
Module: sqlservr.exe
select trunc(startdate)Days,serviceclass,datavolume,nano,bnumber
,cost from in_cdr partition (incdr_2010_0607) where teleservicec
ode in ('5','6')
40,714 1 40,714.0 0.1 1.40 5.42 5349178
Module: SQL*Plus
update infiles set records_loaded = 1072 where filename = '09101
6-0234-Ccn1CDRFile-100607-1951-503848-7395-08062010130806-MINSAT
.txt20100608'
40,714 1 40,714.0 0.1 1.55 2.94 203676107
Module: SQL*Plus
update infiles set records_loaded = 984 where filename = '091016
-0234-Ccn1CDRFile-100607-1917-503784-7274-08062010123948-MINSAT.

Similar Messages

Resizing db_cache_size parameter

Hi all,
i have database performance problem, the server is slow because the RAm is used in 100%, taking statspack report i got the folowing output in instance efficiency:
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer Nowait %: 100.00 Redo NoWait %: 100.00
Buffer Hit %: 14.15 In-memory Sort %: 99.98
Library Hit %: 98.60 Soft Parse %: 95.77
Execute to Parse %: 74.71 Latch Hit %: 99.99
Parse CPU to Parse Elapsd %: 72.98 % Non-Parse CPU: 99.90
Shared Pool Statistics Begin End
Memory Usage %: 84.61 89.19
% SQL with executions>1: 4.97 5.09
% Memory for SQL w/exec>1: 14.23 16.09
The Buffer Hit is 14 which seems very slow, from statspack analyzer they are advising to resize the DB_CACHE_SIZE parameter following the DB_CACHE_ADVICE view output below:
80 10010 1.631 4847378181
160 20020 1.4917 4433425952
240 30030 1.4153 4206245775
320 40040 1.3496 4011022458
400 50050 1.2544 3727968097
480 60060 1.1851 3522007360
560 70070 1.1305 3359950649
640 80080 1.0732 3189644899
720 90090 1.0296 3060020775
768 96096 1 2972013360
800 100100 .9785 2908132320
880 110110 .8999 2674444052
960 120120 .8683 2580516085
1,040 130130 .8366 2486253576
1,120 140140 .6408 1904428818
1,200 150150 .569 1691134670
1,280 160160 .556 1652315333
1,360 170170 .5489 1631483768
1,440 180180 .5448 1619113935
1,520 190190 .5421 1611045498
1,600 200200 .5388 1601383512
can anybody help me on what is the right size of my db_cache_size as i have 4 Gb of RAM and the SGA_MAX_SIZE is set to 2Gb and pga_aggregate_target is set to 0.
thanks
Lucien

Hi Jonathan,
here is my entire statspack report, please help.
SQL ordered by Reads for DB: GABON Instance: gabon Snaps: 51 -52
-> End Disk Reads Threshold:    1000
                                                     CPU      Elapsd
Physical Reads Executions Reads per Exec %Total Time (s) Time (s) Hash Value
         77,007            2       38,503.5    0.9     5.17      5.25 3171232606
Module: sqlservr.exe
select trunc(DATELOADED) STARDATE,FILENAME, RECORDS_IN_FILE,
RECORDS_LOADED ,filenameid,ABS(RECORDS_IN_FILE-RECORDS_LOADED) D
ELTA from sysadm.infiles   where to_char(DATELOADED,'YYYYMMDD
')='20100617'   and (RECORDS_IN_FILE <> RECORDS_LOADED OR RECOR
DS_LOADED=0)and ABS(RECORDS_IN_FILE-RECORDS_LOADED)>1 ORDER BY
         42,729            1       42,729.0    0.5     1.13      1.10 220927140
Module: SQL*Plus
select distinct 'Exists' from infiles where filename = '091016-0
234-Ccn1CDRFile-100629-1140-552795-0670-29062010114304-MINSAT.tx
t20100629'
         42,729            1       42,729.0    0.5     1.23      1.21 319703435
Module: SQL*Plus
update infiles set records_loaded = 952 where filename = '091016
-0234-Ccn1CDRFile-100629-1140-552797-0677-29062010114405-MINSAT.
txt20100629'
         42,729            1       42,729.0    0.5     1.11      1.08 398750951
Module: SQL*Plus
select distinct 'Exists' from infiles where filename = '091016-0
234-Ccn1CDRFile-100629-1142-552799-0700-29062010114905-MINSAT.tx
t20100629'
         42,729            1       42,729.0    0.5     5.05      5.00 585333435
Module: sqlservr.exe
select * from sysadm.infiles   where to_char(DATELOADED,'YYYYM
M')='201006'
         42,729            1       42,729.0    0.5     1.23      1.20 670820997
Module: SQL*Plus
update infiles set records_loaded = 809 where filename = '091016
-0234-Ccn1CDRFile-100629-1142-552799-0700-29062010114905-MINSAT.
txt20100629'
         42,729            1       42,729.0    0.5     1.25      1.22 712766486
Module: SQL*Plus
update infiles set records_loaded = 1011 where filename = '09101
6-0234-Ccn1CDRFile-100629-1138-552792-0668-29062010114246-MINSAT
.txt20100629'
         42,729            1       42,729.0    0.5     1.25      1.22 1267800290
Module: SQL*Plus
update infiles set records_loaded = 928 where filename = '091016
-0234-Ccn1CDRFile-100629-1142-552798-0690-29062010114841-MINSAT.
txt20100629'
         42,729            1       42,729.0    0.5     1.24      1.22 1311160266
Module: SQL*Plus
update infiles set records_loaded = 959 where filename = '091016
-0234-Ccn1CDRFile-100629-1139-552793-0675-29062010114350-MINSAT.
txt20100629'
SQL ordered by Reads for DB: GABON Instance: gabon Snaps: 51 -52
-> End Disk Reads Threshold:    1000
                                                     CPU      Elapsd
Physical Reads Executions Reads per Exec %Total Time (s) Time (s) Hash Value
         42,729            1       42,729.0    0.5     1.24      1.21 1402052156
Module: SQL*Plus
update infiles set records_loaded = 784 where filename = '091016
-0234-Ccn1CDRFile-100629-1140-552795-0670-29062010114304-MINSAT.
txt20100629'
         42,729            1       42,729.0    0.5     1.11      1.09 1617445411
Module: SQL*Plus
select distinct 'Exists' from infiles where filename = '091016-0
234-Ccn1CDRFile-100629-1138-552792-0668-29062010114246-MINSAT.tx
t20100629'
         42,729            1       42,729.0    0.5     1.11      1.08 1686434310
Module: SQL*Plus
select distinct 'Exists' from infiles where filename = '091016-0
234-Ccn1CDRFile-100629-1142-552798-0690-29062010114841-MINSAT.tx
t20100629'
         42,729            1       42,729.0    0.5     1.12      1.10 1778534429
Module: SQL*Plus
select distinct 'Exists' from infiles where filename = '091016-0
234-Ccn1CDRFile-100629-1140-552797-0677-29062010114405-MINSAT.tx
t20100629'
         42,729            1       42,729.0    0.5     1.11      1.08 1800594875
Module: SQL*Plus
select distinct 'Exists' from infiles where filename = '091016-0
234-Ccn1CDRFile-100629-1142-552800-0692-29062010114859-MINSAT.tx
t20100629'
         42,729            1       42,729.0    0.5     1.11      1.08 1952783295
Module: SQL*Plus
select distinct 'Exists' from infiles where filename = '091016-0
234-Ccn1CDRFile-100629-1139-552794-0671-29062010114326-MINSAT.tx
t20100629'
         42,729            1       42,729.0    0.5     1.12      1.10 1985306312
Module: SQL*Plus
select distinct 'Exists' from infiles where filename = '091016-0
234-Ccn1CDRFile-100629-1139-552793-0675-29062010114350-MINSAT.tx
t20100629'
         42,729            1       42,729.0    0.5     1.24      1.21 2073655895
Module: SQL*Plus
update infiles set records_loaded = 936 where filename = '091016
-0234-Ccn1CDRFile-100629-1138-552791-0673-29062010114335-MINSAT.
txt20100629'
         42,729            1       42,729.0    0.5     1.11      1.08 2132012199
Module: SQL*Plus
select distinct 'Exists' from infiles where filename = '091016-0
234-Ccn1CDRFile-100629-1140-552796-0672-29062010114329-MINSAT.tx
t20100629'
SQL ordered by Reads for DB: GABON Instance: gabon Snaps: 51 -52
-> End Disk Reads Threshold:    1000
                                                     CPU      Elapsd
Physical Reads Executions Reads per Exec %Total Time (s) Time (s) Hash Value
         42,729            1       42,729.0    0.5     1.24      1.21 2179069916
Module: SQL*Plus
update infiles set records_loaded = 936 where filename = '091016
-0234-Ccn1CDRFile-100629-1139-552794-0671-29062010114326-MINSAT.
txt20100629'
         42,729            1       42,729.0    0.5     1.24      1.21 3172937007
Module: SQL*Plus
update infiles set records_loaded = 909 where filename = '091016
-0234-Ccn1CDRFile-100629-1140-552796-0672-29062010114329-MINSAT.
txt20100629'
         42,729            1       42,729.0    0.5     1.22      1.21 3567256981
Module: SQL*Plus
select distinct 'Exists' from infiles where filename = '091016-0
234-Ccn1CDRFile-100629-1142-552801-0696-29062010114902-MINSAT.tx
t20100629'
SQL ordered by Executions for DB: GABON Instance: gabon Snaps: 51 -52
-> End Executions Threshold:     100
                                                CPU per    Elap per
Executions   Rows Processed   Rows per Exec    Exec (s)   Exec (s) Hash Value
      22,803          22,803              1.0       0.00        0.00 2453141568
Module: SQL*Plus
DELETE from AIR_CDR where ROWID = :b1
      21,452          21,374              1.0       0.00        0.01 1609964435
Module: SQL*Plus
INSERT INTO ADJUSTMENT_CDR        ( NOMINALAMOUNT,   MSISDN,   S
ERVICECLASSID,   ORIGINNODEID,   ORIGINOPERATORID,   DESCRIPTION
, DESCRIPTION2,   AMOUNTDA1,   AMOUNTDA2,   AMOUNTDA3,   AMOUNT
DA4,   AMOUNTDA5,   startdate,   sequencenumber,   FILEID )
   VALUES       ( :b15 , :b14 , :b13 , :b12 , :b11 , :b10 ,
       5,268          22,389              4.3       0.00        0.00 4143084494
select privilege#,level from sysauth$ connect by grantee#=prior
privilege# and privilege#>0 start with grantee#=:1 and privilege
#>0
       1,434           1,434              1.0       0.00        0.01 1782899448
Module: SQL*Plus
INSERT INTO VOUCHER_CDR        ( MSISDN,   STARTDATE,   SERIALNU
MBER,   COST,   RECHARGEAMOUNTMARKET,   VOUCHERGROUP,   sequence
number,   FILEID )        VALUES        ( :b8,   to_date(substr(
:b7,1,14),'YYYYMMDDHH24MISS'),   :b6,   :b5,   :b4,   :b3,   :b2
, :b1 )
       1,321               0              0.0       0.00        0.00 3611653548
Module: perl@kgateway (TNS V1-V3)
ALTER SESSION SET TIME_ZONE='+01:00'
       1,317           5,268              4.0       0.00        0.00 888033327
select role# from defrole$ d,user$ u where d.user#=:1 and u.user
#=d.user# and u.defrole=2 union select privilege# from sysauth$
s,user$ u where (grantee#=:1 or grantee#=1) and privilege#>0 and
not exists (select null from defrole$ where user#=:1 and role#=
s.privilege#) and u.user#=:1 and u.defrole=3
       1,020               0              0.0       0.00        0.00 2009857449
Module: sqlplus@cdranalysis (TNS V1-V3)
SELECT CHAR_VALUE FROM SYSTEM.PRODUCT_PRIVS WHERE   (UPPER('SQL*
Plus') LIKE UPPER(PRODUCT)) AND   ((UPPER(USER) LIKE USERID) OR
(USERID = 'PUBLIC')) AND   (UPPER(ATTRIBUTE) = 'ROLES')
       1,020               0              0.0       0.00        0.00 3096433403
Module: sqlplus@cdranalysis (TNS V1-V3)
SELECT ATTRIBUTE,SCOPE,NUMERIC_VALUE,CHAR_VALUE,DATE_VALUE FROM
SYSTEM.PRODUCT_PRIVS WHERE (UPPER('SQL*Plus') LIKE UPPER(PRODUCT
)) AND (UPPER(USER) LIKE USERID)
       1,020           1,020              1.0       0.00        0.00 4119976668
Module: sqlplus@cdranalysis (TNS V1-V3)
SELECT USER FROM DUAL
       1,020           1,020              1.0       0.00        0.00 4282642546
Module: SQL*Plusregards
Lucienot.

Resizing the redo_buffer

Hi all,
This post is with regard to the performance issue which I am facing rite now.
When applications are running there is 'Wait Events' are showing, application also running very slow,
I here by list the statistics of my redo_buffer,
Redo Buffers 7135232 bytes
Redo Buffer Waits
3131
Redo Buffer Waits
41
NAME VALUE
redo synch writes 148,331
redo synch time 6,401
redo blocks read for recovery 1,410
redo entries 503,067
redo size 168,676,236
redo buffer allocation retries 13
redo wastage 20,239,188
redo writer latching time 57
redo writes 79,839
redo blocks written 381,764
redo write time 10,986
NAME VALUE
redo log space requests 41
redo log space wait time 3,131
redo log switch interrupts 0
redo ordering marks 15,649
redo subscn max counts 0
16 rows selected.
If I want to increase the size of redo_buffer shall I do it dynamically?
Could you please recomend the estimated size based on the statstics above?
I am using Oracle 10g.
Thanks & Cheers
Antony

I apologise for the wrong info actually the parameter can be changable but you have to make the changes in the pfile.
Then you can have to bounce the database, but which alter system command it wont work.
If you want to resize the parameter then you should give all the other parameter like, buffer cache, large pool, shared pool and everything you have to maintain manually.
Instead of that if you are using 10g then give the parameter sga_target which will take care of everything.
SQL> show parameter spfile
NAME TYPE VALUE
spfile string /opt/app/oracle/app/oracle/pro
duct/10.1.0/db_1/dbs/spfiledba
1.ora
SQL> alter system set log_buffer = 1m scope=spfile;
alter system set log_buffer = 1m scope=spfile
ERROR at line 1:
ORA-02095: specified initialization parameter cannot be modified

Db_CACHE_SIZE

I have it set to 0 which just show that I use it.
This is the output I have now:
select id,name,block_size, current_size,buffers from v$buffer_pool;
3,DEFAULT,8192,4656,578508;
My SGA is 6G.
what will be the optimum size I could resize this parameter to?
Thanks,

Hi
USE v$db_cahce_advice for setting db_cache_size parameter
but this view is available on 9.2 onwards.
Thanks and Regards
Kuljeet Pal Singh

Set optimal db_cache_size param

I read this article http://articles.techrepublic.com.com/5100-10878_11-5031958.html because I want to set optimal db_cache_size parameter on my database. But I still don't know which oracle metric should check to draw such chart and choose best value for my database. Could anybody give me some advice?

The article you read is 8 years old, and doesn't apply to Oracle 10g and beyond, as Oracle 10g and beyond are self-tuning.
Setting db_cache_size in 10g and beyond will disable self-tuning.
So if you are running 10g and beyond (yet again you didn't include your version) the best thing you can do is
- not to read 8 year old articles
- not to set db_cache_size
and better still
be very cautious about anything Donald K Burleson writes, as his tuning approach often includes generic measures, and most other experts like Jonathan Lewis, Tom Kyte, Richard Foote, Cary Millsap and lot of others
fundamentally disagree with him.
Finally: how to determine db_cache_size is in the article, so I suggest you re-read it. Hint: especially read the bits on the cache advisor. Try to be not distracted by the impressive multi-color graphs.
Sybrand Bakker
Senior Oracle DBA

Pga_aggregate_target & db_cache_size for an Oracle 10g Datawarehouse env

We have an Oracle 10g Datawarehousing environment , with roughly 180 GB odd data 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 .Certain packages take 35 min . or so to get executed.
How much should we modify the value of pga_aggregate_target & db_cache_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.
Current PGA_AGGREGATE_TARGET is 8589934592, whereas db_cache_size is
1073741824
Please suggest ,
Thanks a lot in advance ,

It is not clear what is meant by term "packages" in this context - i.e. are these PL/SQL packages or some other bunch of pl/sql statements or whatever else, but simply blindly changing init parameters you won't get anything good in a predictable future.
You have to find WHAT is slow and tune that, it might very well be that it has nothing to do with pga_aggregate_target or another init parameters.
Optimizing Oracle Performance by Cary Millsap and Jeff Holt can be the gretest help in this case.
You can also look at his website www.hotsos.com, it has many whitepapers that can help you if you haven't the book.
I for example see " 3 - node RAC" in your post and that makes me suspicious because if you are running batch jobs reading/writing the same data on all 3 nodes simultaneously, then the problem might be data pinging among nodes. BUT I DON'T KNOW FOR SURE, as well as you don't know, so the only predictable scenario is to get to know what is the reason.
Gints Plivna
http://www.gplivna.eu

Error message while starting database

Hi all,
I am getting the following error message while starting the database . I just modified the DB_CACHE_SIZE parameter from 781MB to 781(+500MB) .We are using Oracle 9.2.0.1 in Windows server 2003 . The database starts fine with old parameter value.I searched in Metalink and in Google but no exact solution for this error . Can any body of you help me in this regard.. It is urgent....
C:\Documents and Settings\mishelpdesk.MISSERVER>d:
D:\>set oracle_sid=MISAPP1
D:\>sqlplus /nolog
SQL*Plus: Release 9.2.0.1.0 - Production on Thu Jun 15 06:32:31 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> connect sys as sysdba
Enter password:
Connected to an idle instance.
SQL> startup pfile='D:\oracle\admin\MISAPP1\pfile\init.ora';
ORA-27102: out of memory
OSD-00022: Message 22 not found; product=RDBMS; facility=SOSD
O/S-Error: (OS 8) Not enough storage is available to process this command.
Thanks in Advance...
Govind.

Your problem is an OS, not Oracle problem, so it wouldn't help to play around with different init.ora parameters, as long as the basic problem persists. The note addresses W2K, you are on W2003, that may the reason for the different OSD error numbers.
For more information about AWE see on metalink
Implementing Address Windowing Extensions (AWE) or VLM on Windows Platforms
Note:225349.1
Werner

SOA-- Invoking OSB Service Getting Error :ORA-00084: global area must be PGA, SGA, or UGA

Hello Friends,
Really appreciate your help/inputs on the below Error Message encountered while running a Concurrent Program--using SOA:Same encountered in recently refreshed DEV instance, Can it be related to some Developement Instance Configuration related to SOA, as same working as expected in PROD.PLEASE ASSIST
Need your inputs on the Error Message we are getting which Invoking OSB Service.
"Error inside invoke_osb_service -> Error Code : -84Error Message :ORA-00084: global area must be PGA, SGA, or UGA "
Can you please review and confirm if the same encountered before or assist on the same:
XXFIN_AP_INVOICES_INT_IB_PKG.invoke_osb_service
-- Define the SOAP request according the the definition of the web service being called
l_soap_request :=
            '<?xml version = "1.0" encoding = "UTF-8"?>'
        || '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:prox="http://OmnicareFinance/ProxyInput/">'
         ||   '<soapenv:Header/>'
         ||     '<soapenv:Body>'
         ||       '<prox:InboundProcess>'
         ||     '<Source_system>'||g_source_instance||'</Source_system>'
         ||     '<Run_mode>'||g_run_mode||'</Run_mode>'
         ||     '<Batch_key>'||g_batch_key||'</Batch_key>'
         ||     '<Request_id>'||g_request_id||'</Request_id>'
         ||     '<Invoice_Header_File_name>'||g_file_name||'</Invoice_Header_File_name>'
         ||     '<Invoice_Line_File_name>'||NULL||'</Invoice_Line_File_name>'
         ||     '<File_location>'||g_file_location||'</File_location>'
         ||       '</prox:InboundProcess>'
         ||     '</soapenv:Body>'
         ||   '</soapenv:Envelope>';
Oracle Apps Log File
-->Entering XXFIN_AP_INVOICES_INT_IB_PKG.invoke_osb_service
-->   = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
-->Response> status_code: "200"
-->Response> reason_phrase: "OK"
-->Response> http_version: "HTTP/1.1"
-->Response From OSB: <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:prox="http://OmnicareFinance/ProxyInput/"/><soapenv:Body xmlns:prox="http://OmnicareFinance/ProxyInput/"><prox:InboundProcessResponse><status>E</status></prox:InboundProcessResponse></soapenv:Body></soapenv:Envelope>
-->OSB Response: E
-->Error inside invoke_osb_service -> Error Code : -84Error Message :ORA-00084: global area must be PGA, SGA, or UGA
-->   = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
-->Entering XXFIN_AP_INVOICES_INT_IB_PKG.capture_error_info
THANKS
ANKUR

Hi..
>
# symptom: ORA-00381: cannot use both new and old parameters for buffer cache size specification
# cause: Both db_block_buffers and db_cache_size parameters are defined in the init.ora (instance parameter file). The db_block_buffers parameter has been deprecated and has been maintained only for backward compatibility. The db_cache_size parameter is one of the size parameters which defines the size of the cache for buffers. These parameters cannot be combined. Setting this along with the Dynamic SGA parameters errors out.
>
For sga_target refer to [http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams193.htm#REFRN10256]
which quotes
>
SGA_TARGET specifies the total size of all SGA components. If SGA_TARGET is specified, then the following memory pools are automatically sized:
*Buffer cache (DB_CACHE_SIZE)
* Shared pool (SHARED_POOL_SIZE)
* Large pool (LARGE_POOL_SIZE)
* Java pool (JAVA_POOL_SIZE)
* Streams pool (STREAMS_POOL_SIZE)
If these automatically tuned memory pools are set to non-zero values, then those values are used as minimum levels by Automatic Shared Memory Management. You would set minimum values if an application component needs a minimum amount of memory to function properly.
>
So, the what ever the value are set for the parameter will act as minimum value when sga_target is set.
HTH
Anand

Reduce buffer busy waits

Can you please provide me the suggestion on how to reduce the number of buffer busy waits for the below query?
Please find the query where the buffer busy waits is taking 11091 and 13160 seconds.
INSERT INTO RPM_CLEARANCE (CLEARANCE_ID, CLEARANCE_DISPLAY_ID, STATE,
REASON_CODE, CLEARANCE_RESET_ID, RESET_IND, ITEM, ZONE_ID, LOCATION,
ZONE_NODE_TYPE, EFFECTIVE_DATE, OUT_OF_STOCK_DATE, RESET_DATE, CHANGE_TYPE,
CHANGE_AMOUNT, CHANGE_PERCENT, CHANGE_CURRENCY, VENDOR_FUNDED_IND,
CREATE_DATE, CREATE_ID, APPROVAL_DATE, APPROVAL_ID, TSL_EVENT_REF,
TSL_MARKDOWN_REF, TSL_EVENT_PHASE, TSL_COVER_GROUP, TSL_END_DATE,
TSL_EVENT_POS_IND, TSL_EVENT_SEL_IND, TSL_HOPOS_TEMPLATE_ID )
VALUES
(:B23 , 'reset:'||:B22 , :B21 , :B20 , NULL, '1', :B19 , :B18 , :B17 , :B16 ,
:B15 , :B15 - 1, NULL, :B14 , :B13 , :B12 , :B11 , '0', :B10 , :B9 , :B10 ,
:B9 , :B8 , :B7 , :B6 , :B5 , :B4 , :B3 , :B2 , :B1 )
call count cpu elapsed disk query current rows
Parse 1849 0.06 0.05 0 0 0 0
Execute 1895091 2539.06 2606.23 32 119694 31084693 1895091
Fetch 0 0.00 0.00 0 0 0 0
total 1896940 2539.12 2606.28 32 119694 31084693 1895091
Misses in library cache during parse: 0
Optimizer mode: ALL_ROWS
Parsing user id: 202 (recursive depth: 1)
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
db file sequential read 32 0.01 0.22
buffer busy waits 11091 0.02 0.29
latch: cache buffers chains 30 0.00 0.00
enq: TX - index contention 563 0.01 0.11
log file switch completion 15 0.06 0.42
latch: In memory undo latch 7 0.00 0.00
buffer deadlock 88 0.00 0.00
cursor: pin S 59 0.00 0.00
cursor: pin S wait on X 1 0.00 0.00
INSERT INTO RPM_CLEARANCE (CLEARANCE_ID, CLEARANCE_DISPLAY_ID, STATE,
REASON_CODE, CLEARANCE_RESET_ID, RESET_IND, ITEM, ZONE_ID, LOCATION,
ZONE_NODE_TYPE, EFFECTIVE_DATE, OUT_OF_STOCK_DATE, RESET_DATE, CHANGE_TYPE,
CHANGE_AMOUNT, CHANGE_PERCENT, CHANGE_CURRENCY, VENDOR_FUNDED_IND,
CREATE_DATE, CREATE_ID, APPROVAL_DATE, APPROVAL_ID, TSL_EVENT_REF,
TSL_MARKDOWN_REF, TSL_EVENT_PHASE, TSL_COVER_GROUP, TSL_END_DATE,
TSL_EVENT_POS_IND, TSL_EVENT_SEL_IND, TSL_HOPOS_TEMPLATE_ID )
VALUES
(:B23 , 'reset:'||:B22 , :B21 , :B20 , NULL, '1', :B19 , :B18 , :B17 , :B16 ,
:B15 , :B15 - 1, NULL, :B14 , :B13 , :B12 , :B11 , '0', :B10 , :B9 , :B10 ,
:B9 , :B8 , :B7 , :B6 , :B5 , :B4 , :B3 , :B2 , :B1 )
call count cpu elapsed disk query current rows
Parse 575 0.02 0.01 0 0 0 0
Execute 1066687 1460.30 1478.77 0 121065 17556349 1066687
Fetch 0 0.00 0.00 0 0 0 0
total 1067262 1460.32 1478.79 0 121065 17556349 1066687
Misses in library cache during parse: 0
Optimizer mode: ALL_ROWS
Parsing user id: 202 (recursive depth: 1)
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
latch: cache buffers chains 28 0.01 0.01
buffer busy waits 13160 0.07 0.46
enq: TX - index contention 522 0.00 0.09
buffer deadlock 108 0.00 0.00
latch: In memory undo latch 17 0.00 0.00
cursor: pin S 8 0.00 0.00
log file switch completion 2 0.05 0.07
cursor: pin S wait on X 1 0.00 0.00
********************************************************************************

For reducing buffer busy waits you need to increase DB_CACHE_SIZE parameter value.
Try the query below
14:40:23 SQL> select name,size_for_estimate,size_factor,estd_physical_reads,buffers_for_estimate fro
m v$db_cache_advice order by 4;
NAME    SIZE_FOR_ESTIMATE SIZE_FACTOR ESTD_PHYSICAL_READS BUFFERS_FOR_ESTIMATE
DEFAULT               960       1.875              252983               119760
DEFAULT               912      1.7813              268597               113772
DEFAULT               864      1.6875              269415               107784
DEFAULT               816      1.5938              269673               101796
DEFAULT               768         1.5              270449                95808
DEFAULT               720      1.4063              270923                89820
DEFAULT               672      1.3125              272107                83832
DEFAULT               624      1.2188              276651                77844
DEFAULT               576       1.125              282272                71856
DEFAULT               528      1.0313              308869                65868
DEFAULT               512           1              334346                63872
DEFAULT               480       .9375              411617                59880
DEFAULT               432       .8438              467955                53892
DEFAULT               384         .75              520223                47904
DEFAULT               336       .6563              575829                41916
DEFAULT               288       .5625              628226                35928
DEFAULT               240       .4688              670286                29940
DEFAULT               192        .375              725289                23952
DEFAULT               144       .2813              784512                17964
DEFAULT                96       .1875              921481                11976
DEFAULT                48       .0938             1948144                 5988
21 rows selected.You will get a result like above. SIZE_FOR_ESTIMATE column shows values in MB.
Then from the result, choose a size for the buffer cache in which there is minimal physical reads but according to the avaliability of your physical memory and set it.

SAP BW with ORA-04031 Errors

Hello All,
Context:
We have a financial closing system working in the BW 3.5 and Oracle 9.2.0.7.0.
We are working with more than 100 millions records in 3 days.
In general, the system uses the standard data marts and BPS processes (copy, distribution, etc).
Error:
We had a lot of ORA-04031 errors for all execution (ABAP Programs, Data Loads, BPS Executions), it stopped the environment.
We did the "stop/start" the server to solved the problem.
The basis team increase the parameter "shared_pool_size" = 3000M - We saw the SAP Note (690241) and which is more than enough.
We have fear about it, we think it is posible to occurs again.
This is a big impact for the business.
Have you got this error in the past?
Could you please help us.
Thanks a lot.
Daniel Souza
SAP BW, SEM and Portal Consultant.
São Paulo - Brazil
+55 11 99092151

Hi Chandran,
We saw this note.
The basis team have been changed the KGHDSIDXCOUNT parameter ( 4 to 1).
I am not founding more causes for this problem in the note.
Is it posible to have problems if the DB_CACHE_SIZE parameter is very large? example 18000M?
The basis team reduces the value for 1700M, in the last shutdown.
How can I flush the memory automatically?
The basis team reported this error for us. "It is not posible to flush the memory, it is necessary to shutdown the server".
Is it posible for the oracle 9i manage the memory area (shared pool) automatically? Is it recommended? Have you got this experience?
We have seen two notes about it:
997889 --> "Increase the memory SGA the ocurrence of error ORA-04031 but it does not prevent it."
617416 --> "The following areas of the SGA can be changed dynamically with Oracle 9.2 if the SGA is configured dynamically: Buffer Cache, Shared Pool, Large Pool."
Thanks a lot.
Best regards,
Daniel Souza
São Paulo - Brazil

Write Performanc Issues.

Hi
Oracle : 11.2.0.2.0 EE.
Linux : Rhel 5.6.
Dell R720 :
EMC VNX SAN Storage :
Here is the scenario:
The dell server is connected to the SAN . We have 2 instances on this same server. When we create a tablespace on one instance it takes twice as long as creating the tablespace on the 2nd instance. The tablespaces are created on the san.
At this point we have eliminated any hardware/ SAN issues. Since both databases are on the same server and hardware, connecting to the same lun on the san.
Any help would be appreciated.
Below is the relative information of the creation scripts and init.ora parameters.
Tablesapace creation Script for ORCL1 (Notice the 8k block size corresponding to the db_block_size on the db ).
CREATE BIGFILE TABLESPACE TEST_IO BLOCKSIZE 8k LOGGING
DATAFILE '/uP01/oracle/oradata/orcl1/TEST_IO_01.dbf'
SIZE 256G AUTOEXTEND OFF
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 256K
SEGMENT SPACE MANAGEMENT AUTO
PERMANENT ONLINE;
14 minutes to create
Tablespace creation script for orcl 2 (Notice the 32k block size corresponding to the db_block_size on the db ).
CREATE BIGFILE TABLESPACE TEST_IO BLOCKSIZE 32k LOGGING
DATAFILE '/uP01/oracle/oradata/orcl2/TEST_IO_01.dbf'
SIZE 256G AUTOEXTEND OFF
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 256K
SEGMENT SPACE MANAGEMENT AUTO
PERMANENT ONLINE;
30minutes to create
Init.ora on orcl1 :
orcl1.__db_cache_size=494927872
orcl1.__java_pool_size=4194304
orcl1.__large_pool_size=4194304
orcl1.__oracle_base='/opt/app/oracle/ora11g'#ORACLE_BASE set from environment
orcl1.__pga_aggregate_target=536870912
orcl1.__sga_target=1073741824
orcl1.__shared_io_pool_size=0
orcl1.__shared_pool_size=515899392
orcl1.__streams_pool_size=25165824
*._optimizer_extend_jppd_view_types=FALSE
*._optimizer_group_by_placement=FALSE
*._replace_virtual_columns=FALSE
*.audit_file_dest='/opt/app/oracle/ora11g/admin/orcl1/adump'
*.audit_trail='none'
*.compatible='11.1.0.0.0'
*.db_block_size=8192
*.db_domain=''
*.db_name='orcl1'
*.diagnostic_dest='/opt/app/oracle/ora11g'
*.local_listener=''
*.open_cursors=1000
*.pga_aggregate_target=536870912
*.processes=500
*.recyclebin='OFF'
*.remote_login_passwordfile='EXCLUSIVE'
*.sec_case_sensitive_logon=FALSE
*.sessions=555
*.sga_target=1073741824
*.undo_tablespace='UNDOTBS1'
orcl2
*.db_block_size=32768
*.db_cache_size=23068672000
*.db_domain=''
*.db_file_multiblock_read_count=32
*.db_files=10000
*.db_flashback_retention_target=0
*.db_keep_cache_size=134217728
*.db_name='orcl2'
*.db_unique_name='ORCL2'
*.diagnostic_dest='/opt/app/oracle/ora11g'
*.fast_start_mttr_target=1200
*.filesystemio_options='SETALL'
*.java_pool_size=268435456
*.job_queue_processes=4
*.large_pool_size=134217728
*.log_buffer=134217728
*.log_checkpoint_timeout=0
*.log_checkpoints_to_alert=TRUE
*.open_cursors=1000
*.pga_aggregate_target=31457280000
*.processes=300
*.query_rewrite_integrity='STALE_TOLERATED'
*.recyclebin='OFF'
*.remote_login_passwordfile='EXCLUSIVE'
*.resource_limit=TRUE
*.resumable_timeout=7200
*.sessions=335
*.shared_pool_reserved_size=134217728
*.shared_pool_size=2147483648
*.star_transformation_enabled='TRUE'
*.trace_enabled=FALSE
*.undo_retention=36000
*.undo_tablespace='UNDOTBS1'

>
The dell server is connected to the SAN . We have 2 instances on this same server. When we create a tablespace on one instance it takes twice as long as creating the tablespace on the 2nd instance. The tablespaces are created on the san.
At this point we have eliminated any hardware/ SAN issues. Since both databases are on the same server and hardware, connecting to the same lun on the san.
>
If those are really the config paramters for your instances then you may have some serious configuration issues.
Instance 1
1. you have shown SGA_TARGET is set (implying Automatice Shared Memory Management) but then you show the individual components have also been set: SHARED_POOL_SIZE, LARGE_POOL_SIZE, etc.
Which are trying to use manual or automatic shared memory management?
2. SGA_TARGET is set to only 1 GB. Why so small?
Instance 2
1. You have NOT set DB_nK_CACHE_SIZE but say you want to use 32 KB block size. This parameter MUST BE SET.
2. You have set DB_CACHE_SIZE to 23 GB. Why? Your block size is 32 KB that you want to use. Only the SYSTEM tablespace will use the standard 8K blocks so why the enormous cache? You only used a cache of .5 GB and total memory target of 1 GB for instance 1.
3. SGA_TARGET is NOT set - why not? why are you not using the same memory management as what you tried to do in instance 1.
What is going on with these two instances that their config is so radically different?
Daniel suggested a possible issue with the 32 KB block size. My hypothesis is that your configuration for both instances is faulty and that for instance 2 in particular your failure to provide any setting for DB_nK_CACHE_SIZE is a likely suspect for causing the issue.
Review the DBA Guide for how to configure memory and the requirements for using non-standard block sizes.
I would expect that once you have your instances configured properly you won't have the problem you reported.
http://docs.oracle.com/cd/E11882_01/server.112/e25494/memory004.htm
About Automatic Shared Memory Management
>
Automatic Shared Memory Management simplifies SGA memory management. You specify the total amount of SGA memory available to an instance using the SGA_TARGET initialization parameter and Oracle Database automatically distributes this memory among the various SGA components to ensure the most effective memory utilization.
>
See the example for automatic management
>
You can take advantage of automatic shared memory management by setting Total SGA Size to 992M in Oracle Enterprise Manager, or by issuing the following statements:
ALTER SYSTEM SET SGA_TARGET = 992M;
ALTER SYSTEM SET SHARED_POOL_SIZE = 0;
ALTER SYSTEM SET LARGE_POOL_SIZE = 0;
ALTER SYSTEM SET JAVA_POOL_SIZE = 0;
ALTER SYSTEM SET DB_CACHE_SIZE = 0;
ALTER SYSTEM SET STREAMS_POOL_SIZE = 0;
where 992M = 1200M minus 208M.
>
For non-standard block sizes see the section 'Setting the Buffer Cache Initialization Parameters'
>
Oracle Database supports multiple block sizes in a database. If you create tablespaces with nonstandard block sizes, you must configure nonstandard block size buffers to accommodate these tablespaces. The standard block size is used for the SYSTEM tablespace. You specify the standard block size by setting the initialization parameter DB_BLOCK_SIZE. Legitimate values are from 2K to 32K.
If you intend to use multiple block sizes in your database, you must have the DB_CACHE_SIZE and at least one DB_nK_CACHE_SIZE parameter set. Oracle Database assigns an appropriate default value to the DB_CACHE_SIZE parameter, but the DB_nK_CACHE_SIZE parameters default to 0, and no additional block size caches are configured.
The sizes and numbers of nonstandard block size buffers are specified by the following parameters:
DB_2K_CACHE_SIZE
DB_4K_CACHE_SIZE
DB_8K_CACHE_SIZE
DB_16K_CACHE_SIZE
DB_32K_CACHE_SIZE
Each parameter specifies the size of the cache for the corresponding block size.
>
Don't forget - when using non-standard block sizes you MUST set both the standard cache parameter (8k) and the non-standard parameter (32k for your use case).

SGA_TARGET

Hi,
I have one quick question regarding the SGA_TARGET parameter.
This is my sga allocation so far:
Total System Global Area 2147483648 bytes
Fixed Size 2140320 bytes
Variable Size 2124240736 bytes
Database Buffers 16777216 bytes
Redo Buffers 4325376 bytes
My RAM size is 16GB and i would be creating many other applications as well. now i have the following sga parameters:
SQL> sho parameter sga;
NAME TYPE VALUE
lock_sga boolean FALSE
pre_page_sga boolean FALSE
sga_max_size big integer 2G
sga_target big integer 0
Now my worry is the sga_target i want to make use but i have given old parameters as well and i am getting the error
Error:     ORA-00381 (ORA-381)
Text:     cannot use both new and old parameters for buffer cache size
     specification
now my db* parameter settings are:
SQL> sho parameter db;
NAME TYPE VALUE
db_16k_cache_size big integer 0
db_2k_cache_size big integer 0
db_32k_cache_size big integer 0
db_4k_cache_size big integer 0
db_8k_cache_size big integer 0
db_block_buffers integer 2048
db_block_checking string FALSE
db_block_checksum string TRUE
db_block_size integer 8192
db_cache_advice string ON
db_cache_size big integer 0
NAME TYPE VALUE
db_create_file_dest string
db_create_online_log_dest_1 string
db_create_online_log_dest_2 string
db_create_online_log_dest_3 string
db_create_online_log_dest_4 string
db_create_online_log_dest_5 string
db_domain string PFIZER.COM
db_file_multiblock_read_count integer 16
db_file_name_convert string
db_files integer 1024
db_flashback_retention_target integer 1440
NAME TYPE VALUE
db_keep_cache_size big integer 0
db_name string EAMS01
db_recovery_file_dest string
db_recovery_file_dest_size big integer 0
db_recycle_cache_size big integer 0
db_unique_name string EAMS01
db_writer_processes integer 2
dbwr_io_slaves integer 0
rdbms_server_dn string
standby_archive_dest string ?/dbs/arch
standby_file_management string MANUAL
and my init parameters are:
EAMS01.__streams_pool_size=33554432
*._allow_level_without_connect_by=TRUE
*.aq_tm_processes=1
*.ARCHIVE_LAG_TARGET=900
*.audit_file_dest='/u03/oracle/admin/EAMS01/adump'
*.audit_trail='TRUE'
*.background_dump_dest='/u03/oracle/admin/EAMS01/bdump'
*.control_files='/u04/oradata/EAMS01/control01.ctl','/u04/oradata/EAMS01/control02.ctl','/u04/oradata/EAMS01/control03.ctl'
*.core_dump_dest='/u03/oracle/admin/EAMS01/cdump'
*.db_block_buffers=550# SMALL
*.db_domain='PFIZER.COM'
*.db_file_multiblock_read_count=16# SMALL
*.db_files=1024# SMALL
*.db_name='EAMS01'
*.global_names=TRUE
*.java_pool_size=96M
*.job_queue_processes=15
*.large_pool_size=32M
*.log_archive_dest='/u04/arch/EAMS01'
*.log_archive_format='EAMS01_%t_%s_%r.arc'
*.log_archive_max_processes=5
*.log_checkpoint_interval=10000
*.log_checkpoints_to_alert=TRUE
*.max_dump_file_size='10240'# limit trace file size to 5 Meg each
*.NLS_DATE_FORMAT='YYYY-MM-DD'
*.nls_length_semantics='CHAR'
*.NLS_TERRITORY='AMERICA'
*.open_cursors=768
*.open_links=128
*.open_links_per_instance=128
*.optimizer_features_enable='10.2.0.3'
*.parallel_max_servers=5# SMALL
*.pga_aggregate_target=500M
*.processes=512# SMALL
*.query_rewrite_enabled='TRUE'
*.query_rewrite_integrity='STALE_TOLERATED'
*.remote_login_passwordfile='EXCLUSIVE'
*.resource_limit=TRUE
*.service_names='EAMS01.pfizer.com'
*.sga_max_size=2G
*.shared_pool_size=500000000# SMALL
*.streams_pool_size=33554432
*.timed_statistics=TRUE
*.undo_management='AUTO'
*.user_dump_dest='/u03/oracle/admin/EAMS01/udump'
now what the parameters i am missing or need to edit sga_target so that oralce will use empirically over
time. Thank you.
-- Raman.

Hi..
>
# symptom: ORA-00381: cannot use both new and old parameters for buffer cache size specification
# cause: Both db_block_buffers and db_cache_size parameters are defined in the init.ora (instance parameter file). The db_block_buffers parameter has been deprecated and has been maintained only for backward compatibility. The db_cache_size parameter is one of the size parameters which defines the size of the cache for buffers. These parameters cannot be combined. Setting this along with the Dynamic SGA parameters errors out.
>
For sga_target refer to [http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams193.htm#REFRN10256]
which quotes
>
SGA_TARGET specifies the total size of all SGA components. If SGA_TARGET is specified, then the following memory pools are automatically sized:
*Buffer cache (DB_CACHE_SIZE)
* Shared pool (SHARED_POOL_SIZE)
* Large pool (LARGE_POOL_SIZE)
* Java pool (JAVA_POOL_SIZE)
* Streams pool (STREAMS_POOL_SIZE)
If these automatically tuned memory pools are set to non-zero values, then those values are used as minimum levels by Automatic Shared Memory Management. You would set minimum values if an application component needs a minimum amount of memory to function properly.
>
So, the what ever the value are set for the parameter will act as minimum value when sga_target is set.
HTH
Anand

Tracking objects in oracle data buffers

hi all,
i am trying to move data blocks from the cold region of "default pool" to the hot region of "keep pool" and would like to know if theres a sweet and simple way to find out and achieve this?
comments and inputs would be appreciated.
thanks.

User1082,
I'm not sure if I understand you correctly but would like you to note that the KEEP pool is separate RAM region +(db_keep_cache_size)+ in additon to the db_cache_size parameter, which creates the DEFAULT pool.
Determining the actual size for data buffers can be critical depending on the size of the database, and with the KEEP pool there to have a database buffer hit ratio of 100%, it becomes a bit difficult to moving small tables and indexes into the KEEP pool. Hence, to achieve this, you should (a) be aware of the most frequently accessed tables in your DB, and (b) know of tables with high buffer residency.
One recommended approach (by Donald Burleson) to assigning KEEP pool contents is to assign objects (with 80% or more data blocks in buffer) to the KEEP pool. This could either be executed manually or via dbms_job, on a rotationary basis. You can repeat the same for assigning other objects (with 80% or more data blocks in physical RAM) to the KEEP pool.
For further understanding, please refer to Oracle Performance Tuning Guide provided by Aman.
Hope this helps.
Regards,
Naveed.

ASM cache....

Hi,
I want to understand what does ASM cache contains and for what purpose its used in ASM instance?I tried finding in docs but some how couldnt find it?ASM has all the other memory parameters than what does ASM cache does and how(if we can) change or configure its size?
Thanks in advance and regards,
Aman....

db_cache_size parameter controls your ASM cache. ASM cache area is used to
cache metadata blocks. The default value will suit most all implementations.
I have worked on single ASM instance with 4 disk groups and 12 databases deployed on it. Best practices only talks about increasing processes parameter if your number of databases increases. Default value (10202) of ASM cache is 24mb and seems to be enough to handle most of the load. Even if you try increase SGA for ASM using SGA_MAX_SIZE it seems most of the memory goes to variable size and ASM cache continues to be 24MB. so I modified db_cache_size value to 64mb and got it increased as I theotically feel that it has to be relative with number of disk groups, database instances supported.
Oracle does say that ASM memeory needs are static and dont change much dynamically during its run.

Database Block Specs.

Hi All,
Can someone help me with the docs. on block specification in oracle 9i.
Thanks pals
regards
aneej

The size of the block is normally based on the type of the database you are working, DSS, OLTP. The standard that is proposed by Oracle is 8kb for it. Thsi size suits most of the applications and databases. The value of the parameter DB_BLOCK_SIZE can range from 2 to 32kb(look at the doc link posted by Hans). But choosing a big block size realy needs a thorough benchmarking. You may want to read this thread in your spare time for the same discussion,
http://forums.oracle.com/forums/thread.jspa?threadID=663687&tstart=0
The db_nk_caches are not required untill you are not willing to include non-default blocksizes in your db. Again the non-default block size support was included to complement Transsportable Tablespace feature not performance. So mostly you don't need to set it either. Just set db_cache_size parameter and Keep/Recycle also if you feel that they can serve you and you are set to go.
HTH
Aman....

Resizing resize db_cache_size parameter

Similar Messages

Maybe you are looking for