OSWatcher solves small and medium problems

OSWatcher solves small and medium problems

This article describes how to solve the two problems encountered during the use of OSWatcher. If you have a better method, please leave a message.

1: After OSWatcher sets the parameter OSW_COMPRESSION to gzip in the configuration file, all data files collected by OSWatcher will be compressed. When using OSWatcher bba to generate analysis reports, you may encounter problems. oswbba. jar cannot analyze these compressed files. How can this problem be solved?

1.1: data collected by default is stored in the archive directory. If it is not in this directory, check the OSW_ARCHIVE parameter in the configuration file/etc/oswbb. conf. Package the directory first

[root@DB-Server oswbb]# tar -cvf archive.tar ./archive/

 

1.2: Create the directory archive_unzip, decompress the package directory to this directory, and decompress all the gz files.

[root@DB-Server oswbb]# mkdir   archive_unzip

[root@DB-Server oswbb]# tar -xvf archive.tar  -C /home/oracle/monitoring/oswbb/archive_unzip/

[root@DB-Server oswbb]# cd archive_unzip

[root@DB-Server archive_unzip]# cd archive

[root@DB-Server archive]#  find . -name "*.gz" -exec gunzip  {} \;

[root@DB-Server archive]# ls

 

1.3: Use OSWatcher bba to analyze data and generate relevant files.

java -jar Xmx512M oswbba.jar -i /home/oracle/monitoring/oswbb/archive_unzip/archive/

2: When the Linux server does not have the desktop components installed, or the runlevel is 3, or you cannot log on using VNC, how can you use OSWatcher bba to analyze archive data and generate images or report files?

 

The answer is also very simple. You can package and download the collected data files, put them in your own virtual machine or test server, and then use OSWatcher bba for analysis. The steps are similar to the above and will not be described too much here.

 

Address: http://www.cnblogs.com/kerrycode/p/6605694.html