Pular para o conteúdo principal

Calcular optimizer_index_cost_adj

O parâmetro optimizer_index_cost_adj foi criado para permitir alterar os custos relativos entre full-scan e operações índexadas.

Abaixo uma consulta para cacular o valor ideal para instance.

col c1 heading 'Media Waits para|Full Scan Read I/O' format 9999.999
col c2 heading 'Media Waits para|Index Read I/O' format 9999.999
col c3 heading 'Porcentagem de| I/O Waits|para Full Scans' format 9.99
col c4 heading 'Porcentagem de| I/O Waits|para Index Scans' format 9.99
col c5 heading 'Valor|inicial|para|optimizer|index|cost|adj' format 999

select
a.average_wait c1,
b.average_wait c2,
a.total_waits /(a.total_waits + b.total_waits) c3,
b.total_waits /(a.total_waits + b.total_waits) c4,
(b.average_wait / a.average_wait)*100 c5
from
v$system_event a,
v$system_event b
where
a.event = 'db file scattered read'
and
b.event = 'db file sequential read'
;
Por tratar-se de um ajuste mais fino da sua instance, deve verificar também os parametrôs optimizer_index_caching e db_file_multiblock_read_count, um tutorial mais detalhado você pode consultar http://www.dba-oracle.com/oracle_tips_cost_adj.htm

Comentários

Postar um comentário

Postagens mais visitadas deste blog

Webcenter Content - Cache Configuration for JdbcFileStore configuration

The configuration values below, control the temporarily cached files keep in FileCache table. FsCacheThreshold Specifies the maximum cache size, in megabytes (default=100) Once the threshold is met, Content Server starts deleting files that are older than the minimum age, as specified by the FsMinimumFileCacheAge parameter FsMaximumFileCacheAge The age at which files are deleted, expressed in days. The default is 365 days FsMinimumFileCacheAge The minimum age at which cached files can be deleted This parameter is used in conjunction with the FsCacheThreshold parameter to determine when to delete cached files FsCleanUpCacheDuringIndexing This parameter activates vault cache cleaning, while FsCacheThreshold, FsMaximumFileCacheAge and FsMinimumFileCacheAge are controling its behaviour.  Expect, when this is enabled on a system that currently has a large number of files in the FileCache table, the first cycle will take a long time to complete. How to Confi...

Oracle Data Modeler and SQL Developer: change user interface (GUI) language

Oracle Data Modeler and Oracle SQL Developer does not allow to change the user interface language in “Options” or somewhere else in the GUI. This applies to the versions: Oracle SQL Developer Data Modeler - Version All and later (18.2.0 in my case) Oracle SQL Developer - Version 3.2 and later However, it’s possible switch to other language, changing datamodeler\ide\bin\ide.conf configuration file. The following lines should be added to the file for support English: AddVMOption -Duser.language=en AddVMOption -Duser.country=US Restart application! SQL Developer and Data Modeler supports the following languages: French(fr), German(de), Italian(it), Spanish(es), Brazilian Portuguese(pt BR), Japanese(ja), Korean(ko), Simplified Chinese(zh CN), Traditional Chinese(zh TW).

Recompile JSP EBS - R12.2

1. Backup $ cd $EBS_APPS_DEPLOYMENT_DIR/oacore/html/WEB-INF/classes/ $ mv _pages _pages_old 2. Stop services cd $ADMIN_SCCRIPTS_HOME ./adapcctl.sh stop ./admanagedsrvctl.sh stop oafm_server1 ./admanagedsrvctl.sh stop oacore_server1 3. Compile the jsps manually  cd $FND_TOP/patch/115/bin/ perl $FND_TOP/patch/115/bin/ojspCompile.pl --compile --flush -p             4. Checking $ cd $EBS_APPS_DEPLOYMENT_DIR/oacore/html/WEB-INF/classes/_pages $ ls -ltr  5. Start services cd $ADMIN_SCCRIPTS_HOME ./admanagedsrvctl.sh start oacore_server1 ./admanagedsrvctl.sh start oafm_server1 ./adapcctl.sh start 6. Clear your web browser cache