Database Reference
In-Depth Information
WHERE F.TS#=T.TS#
AND (F.FILE#=??
OR F.FILE#=??)
AND T.NAME = TABLESPACE_NAME
FILE# FNAME TNAME TABLE_NAME
----- ------------------------------------------------------ ---------- -----------
11 +EGCDEV_DATA/egcdev/datafile/raptest.275.745061089 RAPTEST CUSTOMER
11 +EGCDEV_DATA/egcdev/datafile/raptest.275.745061089 RAPTEST CUSTOMER
13 +EGCDEV_DATA/egcdev/datafile/raptest.277.747755595 RAPTEST CUSTOMER
13 +EGCDEV_DATA/egcdev/datafile/raptest.277.747755595 RAPTEST CUSTOMER
14 +EGCDEV_DATA/egcdev/datafile/raptest.279.748210755 RAPTEST CUSTOMER
14 +EGCDEV_DATA/egcdev/datafile/raptest.279.748210755 RAPTEST CUSTOMER
13 +EGCDEV_DATA/egcdev/datafile/raptest.277.747755595 RAPTEST CUSTOMERS
11 +EGCDEV_DATA/egcdev/datafile/raptest.275.745061089 RAPTEST CUSTOMERS
14 +EGCDEV_DATA/egcdev/datafile/raptest.279.748210755 RAPTEST CUSTOMERS
11 +EGCDEV_DATA/egcdev/datafile/raptest.275.745061089 RAPTEST DISTRICT
Occasional contentions need not be of concern. However, if this contention is repeatable, the reasons need to
be identified. From the above analysis there are two potential areas where the problem could be mapped. Either the
contention is because the raw device partition is mapped to the same set of disks or it is because the tables are hot
tables and need to be moved into their respective tablespaces to use different files to store the data.
So far we have discussed the OWI with respect to the database, in the sense that it concerns the information
reported by
GV$SESSION_EVENT
,
GV$SYSTEM_EVENT
, and
GV$SESSION_WAIT
. These wait activities more or less relate to
the database configuration or the behavior of SQL queries or the distribution of data in the database.
It is not just the database and the data that can report issues concerning bad performance; performance data
from the operating system can also help in troubleshooting and problem solving. The OWI reports on system-level
activities or waits at the system level such as CPU, memory, etc. Similar to the database statistics reported by the other
three views, the wait activities for the CPU and memory can be obtained by querying the
GV$SYSSTAT
and
GV$SESSTAT
.
Similar to the
GV$SYSTEM_EVENT
that reports on the wait events at the instance level,
GV$SYSSTAT
also reports
operating system statistics at the system level. This means that the statistics generated from this view only provide an
overall health indication for the database in the cluster. Also, the data provided by this view covers the time since the
instance was last bounced as indicated by the
GV$INSTANCE
view.
COL NAME FORMAT A40
SELECT
INST_ID,
NAME,
VALUE
FROM GV$SYSSTAT
WHERE (NAME LIKE 'db%'
OR NAME LIKE '%prase%'
OR NAME LIKE '%cpu%'
OR NAME LIKE '%global%'
OR NAME LIKE '%gc%')
The above output indicates the session statistics of the system. It indicates the amount of memory and CPU
(not shown in the output) consumed by the session. Data from this output can be utilized for sizing the Oracle
memory; if there is high CPU usage, you should consider tuning the query.
Search WWH ::
Custom Search