SGA Max Size limit?

Question

Hi,
I have Fujitsu mid range Server with 16gb RAM and 64 bit Windows Server 2003,10g R2 db installed, current i have SGA size 4gb..
What is SGA max size limit????
One of my report runs in 24 seconds...*will this issue b solved increasing the SGA size upto 10,12 gb?*

Answer 1

Yes,
You can also go for a 10046 event tracing...
ACCEPT sid PROMPT 'Enter SID: '
ACCEPT serial PROMPT 'Enter SERIAL#: '
ACCEPT action PROMPT 'Enter TRUE or FALSE: '
EXEC sys.DBMS_SYSTEM.SET_SQL_TRACE_IN_SESSION(&sid,&serial,&action);
prompt Trace &action for &sid,&serial
exec DBMS_SYSTEM.SET_EV(10,20,10046,12,”);
Then you can check your dump file and see whcih events are higher......
For Eg. content could be like:
=====================
PARSING IN CURSOR #6 len=107 dep=1 uid=44 oct=6 lid=44 tim=1621758552415 hv=3988607735 ad='902c07a8'
UPDATE rn_lu_lastname_loca set entr_loca_id_plz14 = translate(entr_loca_id_plz14,'_','-') where rowid = :b1
END OF STMT
PARSE #6:c=0,e=981,p=0,cr=0,cu=0,mis=1,r=0,dep=1,og=0,tim=1621758552403
BINDS #6:
bind 0: dty=1 mxl=32(18) mal=00 scl=00 pre=00 oacflg=13 oacfl2=1 size=32 offset=0
bfp=10331d748 bln=32 avl=18 flg=09
value="AAAHINAATAAAwTTABV"
WAIT #6: nam='db file sequential read' ela= 12170 p1=6 p2=197843 p3=1
WAIT #6: nam='db file sequential read' ela= 8051 p1=14 p2=261084 p3=1
WAIT #6: nam='db file sequential read' ela= 7165 p1=19 p2=147722 p3=1
WAIT #6: nam='db file sequential read' ela= 9604 p1=19 p2=133999 p3=1
WAIT #6: nam='db file sequential read' ela= 6381 p1=19 p2=133801 p3=1
EXEC #6:c=10000,e=45750,p=5,cr=1,cu=10,mis=0,r=1,dep=1,og=4,tim=1621758598343
FETCH #5:c=0,e=357,p=0,cr=5,cu=0,mis=0,r=0,dep=1,og=4,tim=1621758598896
EXEC #1:c=30000,e=116691,p=36,cr=35,cu=10,mis=0,r=1,dep=0,og=4,tim=1621758599043
WAIT #1: nam='SQL*Net message to client' ela= 5 p1=1413697536 p2=1 p3=0
WAIT #1: nam='SQL*Net message from client' ela= 2283 p1=1413697536 p2=1 p3=0
Lines that start with WAIT
len Length of SQL statement.
dep Recursive depth of the cursor.
uid Schema user id of parsing user.
oct Oracle command type.
lid Privilege user id.
ela Elapsed time. 8i: in 1/1000th of a second, 9i: 1/1'000'000th of a second 
tim Timestamp. Pre-Oracle9i, the times recorded by Oracle only have a resolution of 1/100th of a second (10mS). As of Oracle9i some times are available to microsecond accuracy (1/1,000,000th of a second). The timestamp can be used to determine times between points in the trace file. The value is the value in v$timer when the line was written. If there are TIMESTAMPS in the file you can use the difference between 'tim' values to determine an absolute time. 
hv Hash id.
ad SQLTEXT address (see v$sqlarea and v$sqltext).
Lines that start with PARSE, EXEC or FETCH
#n  n = number of cursor 
c  cpu time 
e  elapsed time 
p  physical reads 
cr  consistant reads 
cu  current mode reads 
mis miss in cache (?) 
r  rows processed 
dep recursive depth 
og  optimizer goal 
tim time  Content