Data Dictionary
>
FPSINPUT Views
> FPSINPUT.WIP_WAFER_HIST_LOOP
View FPSADMIN.ADM_SQL_HIST
The view DBA_HIST_SQLTEXT is a powerful diagnostic tool for investigating top queries if we have access. This is a basic query of how to use it which should be used with a filter on begin_interval_time. BEGIN_INTERVAL_TIME: The start time of the snapshot. BUFFER_GETS_PER_EXEC: The number of buffer gets per execution during the snapshot. A buffer get is a block read, either from memory or from disk, which obviously requires physical I/O. CPU_TIME_SEC_PER_EXEC: The CPU time (in seconds) per execution during the snapshot. DATABASE_NAME: The database instance name. DBID: The database instance identifier. DISK_READS_PER_BUFFER_GET: The number of disk reads for each buffer get during the snapshot. A high number indicates that a buffer get often goes to the disk and thus causes a lot of physical I/O. DISK_READS_PER_EXEC: The number of disk reads per execution during the snapshot. ELAPSED_TIME_SEC_PER_EXEC: The elapsed time (in seconds) per execution during the snapshot. END_INTERVAL_TIME: The end time of the snapshot. EXECUTIONS: The number of executions during the snapshot. IO_WAIT_SEC_PER_EXEC: The I/O wait time (in seconds) per execution during the snapshot. A high number may indicate a large number of disk reads, for instance because of cursor sharing of statements without bind variables. MODULE: The module through which the code is executed. PARSE_CALLS_PER_EXEC: The number of parse calls per execution during the snapshot. A high number (i.e. around 1) indicates that a SQL statement or PL/SQL module has been flushed from the cache and thus requires parsing, which adds a few milliseconds. Code that is executed frequently that also requires parsing can be a bottleneck. PARSING_SCHEMA_NAME: The parsing schema name, i.e. the schema from which the code is executed. PHYS_READ_REQS_PER_EXEC: The number of physical read requests per execution during the snapshot. PHYS_WRITE_REQS_PER_EXEC: The number of physical write requests per execution during the snapshot. PLSQL_EXEC_TIME_SEC_PER_EXEC: The PL/SQL execution time (in seconds) per execution during the snapshot. PLSQL_SQL_TIME_RATIO: The ratio of PL/SQL execution to CPU time, which is more or less the fraction of the time Oracle spends inside the PL/SQL engine instead of the SQL engine. A high ratio may indicate that there may be many context switches affecting the performance. ROWS_PROCESSED_PER_EXEC: The number of rows processed per execution during the snapshot. SQL_ID: The SQL identifier of the parent cursor. SQL_TEXT: The full statement for which the metrics are shown.