Monday Sep 30, 2013

Standalone Log Analysis Utility

I just had a comment from Development on one of our older posts.

Good news:

The Log file Analysis Tool that was introduced in EPM 11.1.2.3.000 ( read post here ) has now been made stand-alone.

Why would that be important?
Because:  "You can use this standalone log analysis utility to analyze logs from any 11.1.1.x or 11.1.2.x deployments.  It will run on EPM servers or non-EPM servers."
That's why!

It is available as a patch via MOS under the number  17425397

As of the readme, the prerequisites are fairly lightweight and not surprising:

Prerequisites
Any user can run this utility from any machine on which log files are stored.
- Users running the Log Analysis Utility must have execute privileges on the following files:
Windows: EPM_ORACLE_INSTANCE/bin/loganalysis.bat
LINUX/UNIX: EPM_ORACLE_INSTANCE/bin/loganalysis.sh

- The user who runs this utility must have read permissions on the directory where the log files are located.

The download is just over 2 MB and it includes the readme file. This will not only tells you how to install and use the utility, it also contains the list of available commands.

Sidenote:
The comment on the blog requesting a backport was posted early in September 2013 (our first mention in May).
The answer from Development came in on September 25th 2013. Less than a month to get this done!

Thanks to Fuad and Maurice for making this happen so quickly.


Thursday May 02, 2013

EPM 11.1.2.3 - new Log Analysis tool

(in via Maurice)

Log Analysis is a new and versatile troubleshooting tool which has been bundled with Enterprise Performance Management 11.1.2.3.
Documentation for the tool is available on the command line when running the batch without parameters.

To kick it off, simply run:

/Oracle/Middleware/user_projects/epmsystem1/bin/loganalysis.sh or
/Oracle/Middleware/user_projects/epmsystem1/bin/loganalysis.bat

Log Analysis can scan all the EPM logs in-situ or in an offline hierarchy of log directories pointed to by a path

  • (-d <Offline log files directory> )

Restrictions may include:

  • message type (-m INCIDENT_ERROR, ERROR, WARNING, NOTIFICATION, TRACE )
  • time range (-t YYYY-MM-DDTHOUR:MIN:SEC YYYY-MM-DDTHOUR:MIN:SEC )
  • time in minutes (-tmin 45 )
  • a string (-s "  " )
  • a message series across servers (-ecid "0000JpPDIjn9h^FpN0S4ye1HFRt100000J" )
  • output limited to size in megabytes (-maxsize 5 )
  • optional HTML output name (-o "    " )

You can selectively limit the output to return only those messages with an identifier in a Message_ID filter file.

Output is placed in

/Oracle/Middleware/user_projects/epmsystem1/diagnostics/reports/LogAnalysis_Report_YYYY_MM_DD_HH_MM_SS.html

and may be reviewed in a browser.

This will then look similar to:


(click to view full size)

About


This blog talks about the latest news and upcoming events initiated by the EPM/BI Proactive Support Team.
Authors:
Lia, Torben, Paul, Julie





Search

Archives
« September 2015
SunMonTueWedThuFriSat
  
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today