Axis RightFax 8.5 Guía de instalación Pagina 83

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 106
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 82
Copyright © 2001, 2015, Oracle and/or its affiliates. All rights reserved.
13-7
Oracle Database also has automatic statistics gathering job GATHER_STATS_JOB, which is enabled by
default when a database is created, or when a database is upgraded from an earlier database release.
This job gathers statistics on all objects in the database that have missing statistics or stale statistics
(stale - the underlying object has been modified significantly, i.e. more than 10% of the rows). The
Scheduler runs this job during a maintenance window (by default, 10pm to 6am). This automatic job
gathers statistics by estimate and not in as much detail as the Oracle Transportation Management job.
Over time, it tends to override detailed statistics gathered by the Oracle Transportation Management
job for fast growing tables, hence automatic job should be replaced by Oracle Transportation
Management statistics job.
Below are the steps to verify that statistics are gathered by the Oracle Transportation Management
statistics job.
1. In SQL*Plus, as user GLOGOWNER, run:
select min(last_analyzed) from user_tables;
If it returns a date older than two weeks then Oracle Transportation Management statistics job is not
running since that day or it is not scheduled. In that case, schedule a weekly job using any job
scheduler, and have it run <otm_install_dir>/oracle/script8/gather_table_stats.sql during a low-
activity period or off-peak hours.
Note: gather_table_stats.sql also runs gather_column_histograms.sql, so both
should be in same directory.
2. Disable Oracle's automatic job. In SQL*Plus, as user SYS (or any DBA account), run:
BEGIN
DBMS_AUTO_TASK_ADMIN.DISABLE(
client_name => 'auto optimizer stats collection',
operation => NULL,
window_name => NULL);
END;
/
commit;
This will ensure Oracle Transportation Management database has up to date statistics with full
compute on all objects.
Database File Storage Performance
The two most commonly used forms of database file storage are: Storage Area Network (SAN) and
Network-Attached Storage (NAS). NAS provides both storage and filesystem access whereas SAN
provides only block-based storage and leaves file system concerns on the client side. Typical SAN
protocols are SCSI, Fibre Channel, iSCSI, ATA over Ethernet, or HyperSCSI. A NAS on the other hand
communicates over Ethernet and TCP/IP. Because NAS communicates over standard network
protocols there is a stronger possibility of a poorly performing network affecting the data access rate.
The latency from a database server to the NAS device should be less than 150 microseconds (0.15
ms) and preferably less than 100 microseconds (0.10 ms).
Full Export and Re-import
As data is added to tables the database may need to add additional database extents to store the data
and indexes. The general consensus among database administrators is that an increasing number of
extents does not affect performance of the database. However, in practice performance gains have
been seen by completing a Full export and import.
Vista de pagina 82
1 2 ... 78 79 80 81 82 83 84 85 86 87 88 ... 105 106

Comentarios a estos manuales

Sin comentarios