This action might not be possible to undo. Are you sure you want to continue?
In this section we will outline the new and improved features regarding database and instance tuning. Oracle has introduced some good features that enhance self-tuning and automated tuning. They are summarized as follows: User initiated Buffer "utomated $U osting ache !lushing hec#point Tuning
%ynamic &ling Tuning Transaction 'ecovery and (asy )onitoring
User initiated Buffer Cache Flushing
In the past* we had a facility to flush the shared pool. The !+U&, &,"'(%$OO+ clause of "+T(' &-&T() lets you clear all data from the shared pool in the &." /system global area0. This is a useful feature to clear e1isting data and re-load fresh data. 2ow* with 34 g* it becomes possible for users to flush the cache buffers also. Before 34g* Oracle used to internally flush the buffer cache bloc#s as needed. The !+U&, &,"'(%$OO+ clause is useful if you need to measure the performance of rewritten 5ueries or a suite of 5ueries from identical starting points. Use the following statement to flush the buffer cache.
SQL> ALTER SYSTEM FLUSH BUFFER_CACHE; System altered.
,owever* note that this clause is intended for use only on a test database. It is not advisable to use this clause on a production database* because subse5uent 5ueries will have no hits* only misses. The following e1ample shows the effect of flush buffer_cache. There are 64*444 rows in the table 7$O+I -'( 8.
SQL> update P L!CYREC set sum_assured " sum_assured # $%; %&&&& r'(s updated. SQL> )'mm*t; C'mm*t )'mplete. SQL> sele)t '. B+ECT_TYPE, su-str.'. B+ECT_/AME,$,$&0 '-12ame , -.'-1d , -.status, )'u2t.-.'-1d0 3r'm 45-6 -, d-a_'-1e)ts ' (6ere -.'-1d " '.data_'-1e)t_*d a2d '.'(2er " 7/YUSER7 8r'up -y '.'-1e)t_type, '.'-1e)t_2ame,-.'-1d, -.status ; B+ECT_TYPE B+/AME B+9 STATUS C U/T.B. B+90
? @<= <?> SQL> alter system 3lus6 -u33er_)a)6e. If there is a failure and then subse5uent cache recovery* only the redo records containing changes at & 2/s0 higher than the chec#point need to be applied during recovery.'-1d " '. d-a_'-1e)ts ' (6ere -. -.-. SQL> sele)t '.'-1e)t_type. B+90 :::::::::: :::::::::::::: ::::: ::::: ::::::::::::: TABLE TEST$ .<&%= 3ree > TABLE P L!CYREC . Oracle recommends using the fast_start_mttr_target initialization parameter to control the duration of startup after instance failure.'-1d . B+ECT_/AME.'-1d. B+ECT_TYPE B+/AME B+9 STATUS C U/T. "dministrators specify a target /bounded0 time to complete the cache recovery phase of recovery with the .$.data_'-1e)t_*d a2d '.cache recovery followed by transaction recovery.<&%= 3ree . System altered. '.-. Oracle continuously estimates the recovery time and automatically ad9usts the chec#-pointing rate to meet the target recovery time. -.status .status.<&>$ 3ree >>& Automated Checkpoint Tuning hec#-pointing is an important Oracle activity which records the highest system change number /& 2*0 so that all data bloc#s less than or e5ual to the & 2 are #nown to be written out to the data files.'(2er " 7/YUSER7 8r'up -y '.'-1e)t_2ame. %uring the cache recovery phase* also #nown as the rolling forward stage* Oracle applies all committed and uncommitted changes in the redo log files to the affected data bloc#s. !ast-start recovery can greatly reduce the mean time to recover / )TT'0* with minimal effects on online application performance. This method reduces the time re5uired for cache recovery and ma#es the recovery bounded and predictable by limiting the number of dirty buffers and the number of redo records generated between the most recent redo record and the last chec#point. The wor# re5uired for cache recovery processing is proportional to the rate of change to the database and the time between chec#points.<&>$ A)ur ::::::: > .$&0 '-12ame . -ou no longer have to set any chec#point-related parameters.'. -. su-str. B+ECT_TYPE.B.::::::::::: TABLE TABLE TABLE TABLE ::::::::::::: TEST$ P L!CYREC P L!CYREC P L!CYREC :::::: :::::: .'-1d0 3r'm 45-6 -.<&>$ 3ree . :ith 34g* the Oracle database can now self-tune chec#-pointing to achieve good recovery times with low impact on normal throughput. )'u2t. "s we are aware* instance and crash recovery occur in two steps .<&>$ )r .
.fast_start_mttr_target initialization parameter* and Oracle automatically varies the incremental chec#point writes to meet that target. CCPT_BL CC_DR!TES FR M E5!/STA/CE_REC EERY. v$fast_start_servers provides information about all recovery processes . The target_mttr field of v$instance_recovery contains the )TT' target in effect. Together* these two features help to increase the efficiency of the recovery phase. TARBET_MTTR EST!MATE9_MTTR CCPT_BL CC_DR!TES ::::::::::: :::::::::::::: ::::::::::::::::: <? @@ @&F$=? :henever you set fast_start_mttr_target to a nonzero value* and while )TT' advisory is O2* Oracle orporation recommends that you disable /set to 40 the following parameters: L B_CHECCP !/T_T!ME UT L B_CHECCP !/T_!/TEREAL FAST_START_! _TARBET Because these initialization parameters either override fast_start_mttr_target or potentially drive chec#points more aggressively than fast_start_mttr_target does* they can interfere with the simulation.s recovery is handled first. The estimated_mttr field of v$instance_recovery contains the estimated )TT' should a crash happen right away.fast-start parallel rollbac#. and . onse5uently* new transactions do not have to wait until all parts of a long transaction are rolled bac#.!ast-start ondemand rollbac#. !or e1ample* SQL> SELECT TARBET_MTTR. Easier Transaction Recover !onitoring %uring the second phase of instance recovery* Oracle rolls bac# uncommitted transactions. EST!MATE9_MTTR. Using the fast-start on-demand rollbac# feature* the re5uired transaction. This feature is particularly useful when a system has transactions that run a long time before committing* especially parallel I2&('T* U$%"T(* and %(+(T( operations. If a user attempts to access a row that is loc#ed by a terminated transaction* Oracle rolls bac# only those changes necessary to complete the transaction< in other words* it rolls them bac# on demand. In the fast-start parallel rollbac# method* the bac#ground process &)O2 acts as a coordinator and rolls bac# a set of transactions in parallel using multiple server processes. -ou can monitor the progress of fast-start parallel rollbac# by e1amining the v$fast_start_servers and v$fast_start_transactions views. Oracle uses two methods: . &)O2 automatically decides when to begin parallel rollbac# and disperses the wor# among several parallel processes.
)i#e "ult* one of the world.=0 /UMBER The above is an e1cerpt from the bestselling Oracle34g boo# Oracle %atabase 34g 2ew !eatures by )i#e "ult* )adhu Tumma and %aniel +iu* published by 'ampant Tech$ress. v$fast_start_transactions contains data about the progress of the transactions. They are =I%* $=I%* and ' >&('>('&* as shown in the description below.s top Oracle e1perts* has finally consented to release his complete collection of more than ?64 Oracle scripts* covering every possible area of Oracle administration and management.=0 RAD. There are three new columns in the 34 g release that assist monitoring.C6* less than a dime per script.performing fast-start parallel rollbac# .$>0 /UMBER /UMBER /UMBER /UMBER /UMBER /UMBER /UMBER RAD. -ou can download them immediately at this lin#: http:DDwww. )i#e has priced his collection of ?@6 scripts at ABC. SQL> des) E5FAST_START_TRA/SACT! /S /ame /ullG :::::::::::::::::::::::::::: :::::::: US/ SLT SEQ STATE U/9 BL CCS9 /E U/9 BL CCST TAL P!9 CPUT!ME PARE/TUS/ PARE/TSLT PARE/TSEQ H!9 PH!9 RCESEREERS Type :::::::::::: /UMBER /UMBER /UMBER EARCHAR@.comDdownloadEadvEmonEtuning. This is the definitive collection of Oracle monitoring and tuning scripts* and it would ta#e thousands of hours to re-create this vast arsenal of scripts from scratch.htm .rampant-boo#s.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.