Database Reference
In-Depth Information
Checking available disk space
Lack of available disk space is known to have an adverse effect on instance ex-
ecution. Sometimes this is due to excessive logging filling up the disk or logs not
being rotated periodically.
Following is an example of how to view the available disk space. Here, the
/u01
mount point on which Oracle SOA Suite 11g is installed has 74.5 GB available,
so space is not an issue:
root@soahost1:/root> df -m
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/sda8 996 451 494 48% /
/dev/sda9 815881 697454 76314 91% /u01
/dev/sda7 996 36 909 4% /home
/dev/sda5 1984 138 1744 8% /tmp
/dev/sda3 1984 283 1598 16% /var
/dev/sda2 5950 3842 1802 69% /usr
/dev/sda1 99 12 83 13% /boot
tmpfs 8023 0 8023 0% /dev/shm
Checking CPU, memory, and I/O utilization
Some processes can hog the CPU, be it a backup job, a bug in
AdminServer
,
unauthorized code deployments, or your monitoring tool agent. For example,
some intelligent monitoring agents, such as the Oracle Enterprise Manager Grid
Control Agent, perform constant queries against the database to retrieve met-
rics and statistics that may result in undue burden on your environment. Ensure
that there is sufficient memory available and that SWAP space (Unix) or virtual
memory (Windows) is not actively being used.
By reviewing the output of the Linux command
vmstat
as shown in the follow-
ing snippet, we see that SWAP utilization is 0 MB (good!), the amount of free
memory is 59 MB (keep an eye on it!), the numbers of bytes in and bytes out at
