Database Reference
In-Depth Information
As part of the startup process, the following lines are displayed on the default terminal output:
Info...You did not enter a value for snapshotInterval.
Info...Using default value = 30
Info...You did not enter a value for archiveInterval.
Info...Using default value = 48
Setting the archive log directory to /u01/app/oracle/product /oswbb/archive
Testing for discovery of OS Utilities...
VMSTAT found on your system.
IOSTAT found on your system.
MPSTAT found on your system.
IFCONFIG found on your system.
NETSTAT found on your system.
TOP found on your system.
Testing for discovery of OS CPU COUNT
oswbb is looking for the CPU COUNT on your system
CPU COUNT will be used by oswbba to automatically look for cpu problems
CPU COUNT found on your system.
CPU COUNT = 16
Discovery completed.
Starting OSWatcher Black Box v7.2 on Mon May 26 12:53:55 EDT 2014
With SnapshotInterval = 30
With ArchiveInterval = 48
OSWatcher Black Box - Written by Carl Davis, Center of Expertise,
Oracle Corporation
For questions on install/usage please go to MOS (Note:301137.1)
If you need further assistance or have comments or enhancement
requests you can email me Carl.Davis@Oracle.com
Data is stored in directory: /u01/app/oracle/product/oswbb/archive
Starting Data Collection...
oswbb heartbeat:Mon May 26 12:54:00 EDT 2014
Using the Collected Data
Data collected can be used as-is (raw) by transferring it to some external program/analyzer or it can be converted into
graphs using the OSWg utility also provided by Oracle on Metalink. This uses the data collected by the OSW collector
and generates graphs for the various snapshots and types of data collected.
Generally O/S level metrics are not sufficient to determine the root cause of a problem. However, they assist
in determining why a certain situation occurred in the overall performance of the server. For example, why did
something run very slow during a specific time of the day? The reason for this could be that the process or session in
question consumed high CPU or the system was doing a huge amount of context switches (Figure 6-16 ).
 
Search WWH ::




Custom Search