OSW

部署OSW：

[oracle@lmrac1 liming]$ tar -xvf oswbb733.tar 
oswbb/
tar: oswbb: Cannot mkdir: Permission denied
oswbb/docs/

报错了，是因为解压OSW包的时候，会自动新建一个文件夹，而当前用户在当前目录下没有权限。改了权限之后就成功了。

[oracle@lmrac1 ~]$ cd oswbb
[oracle@lmrac1 oswbb]$ ls
call_du.sh      Example_extras.txt  ltop.sh         OSWatcher.sh  oswrds.sh    startOSWbb.sh              vmsub.sh
call_sar.sh     Exampleprivate.net  mpsub.sh        oswbba.jar    oswsub.sh    stopOSWbb.sh               xtop.sh
call_uptime.sh  ifconfigsub.sh      nfssub.sh       oswib.sh      psmemsub.sh  tarupfiles.sh
docs            iosub.sh            OSWatcherFM.sh  oswnet.sh     src          tar_up_partial_archive.sh
[oracle@lmrac1 oswbb]$ ./startOSWbb.sh 
[oracle@lmrac1 oswbb]$ 
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/home/oracle/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 = 1

Discovery completed.

Starting OSWatcher v7.3.3  on Thu Oct 15 05:20:36 CST 2015
With SnapshotInterval = 30
With ArchiveInterval = 48

OSWatcher - 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 [email protected]

Data is stored in directory: /home/oracle/oswbb/archive

Starting Data Collection...

oswbb heartbeat:Thu Oct 15 05:20:41 CST 2015
oswbb heartbeat:Thu Oct 15 05:21:11 CST 2015
oswbb heartbeat:Thu Oct 15 05:21:41 CST 2015
oswbb heartbeat:Thu Oct 15 05:22:11 CST 2015

现在也就能部署上，具体的分析后续使用之后继续更新，且听下回分解。