I was recently playing around with the Log Analysis tool on 11.1.2.2.
John Goodwin has a good write up of the basic operation of the log analysis utility here:
http://john-goodwin.blogspot.com/2013/09/epm-standalone-log-analysis-utility.html
After reviewing the tool, I was curious how to make it a bit more useful.
First, John seems to be pinpointing specific product log directories with the "-d" option. I am curious if it is possible to get more generic and just have the utility tell us what is wrong without specifying the product. This would be beneficial if an error is occurring in the system and you just want a quick report of what error messages might be coming out to help troubleshoot.
I tried very generically:
loganalysis.bat -system -tmin 60 -d d:\Oracle\
However, this seemed to only get the logs in user_projects\epmsystem1\diagnostics. It was missing the Weblogic logs under user_projects\domains. These logs are important because they provide insight into what is happening at the web application server layer. To get more of a complete picture of the system, it is possible to generate a report for both the domains folder and the diagnostics folder.
loganalysis.bat -system -tmin 60 -d d:\Oracle\
loganalysis.bat -system -tmin 60 -d d:\Oracle\
Now this is on the right track. The next issue is that the utility is only scanning a single node. In a distributed environment, this doesn't help the problem of having to log into multiple nodes to gather the logs. Digging a little deeper, it looks like UNC paths work well in the Log Analysis utility.
For instance,
loganalysis.bat -system -tmin 60 -d \\node1\d$\Oracle\ Middleware\user_projects\ epmsystem1\diagnostics -o node1_diagnostics
The final script to run reports for all nodes at once might look something like this:
set SEARCH_IN_MINS=60
start cmd /C "loganalysis.bat -system -tmin %SEARCH_IN_MINS% -d \\node1\d$\Oracle\ Middleware\user_projects\ domains -o web1_domains"
start cmd /C "loganalysis.bat -system -tmin %SEARCH_IN_MINS% -d \\node1\d$\Oracle\ Middleware\user_projects\ epmsystem1\diagnostics -o web1_diagnostics"
start cmd /C "loganalysis.bat -system -tmin %SEARCH_IN_MINS% -d \\node2\d$\Oracle\ Middleware\user_projects\ domains -o web2_domains"
start cmd /C "loganalysis.bat -system -tmin %SEARCH_IN_MINS% -d \\node2\d$\Oracle\ Middleware\user_projects\ epmsystem1\diagnostics -o web2_diagnostics"
start cmd /C "loganalysis.bat -system -tmin %SEARCH_IN_MINS% -d \\node3\d$\Oracle\ Middleware\user_projects\ epmsystem1\diagnostics -o planning1_diagnostics"
start cmd /C "loganalysis.bat -system -tmin %SEARCH_IN_MINS% -d \\node3\d$\Oracle\ Middleware\user_projects\ domains -o planning1_domains"
start cmd /C "loganalysis.bat -system -tmin %SEARCH_IN_MINS% -d \\node4\d$\Oracle\ Middleware\user_projects\ epmsystem1\diagnostics -o planning2_diagnostics"
start cmd /C "loganalysis.bat -system -tmin %SEARCH_IN_MINS% -d \\node4\d$\Oracle\ Middleware\user_projects\ domains -o planning2_domains"
....
I think this is infinity more useful. Much more useful than the single node, single product example. Next time Hyperion is down and everyone is scrambling looking for answers, this script might just be a quick way to discover the issue.
No comments:
Post a Comment