Sunday Feb 15, 2015

OBIEE 11g: Troubleshooting Crash Issues

(In via Debbie)

We are pleased to advise the following NEW Knowledge Document for Oracle Business Intelligence Enterprise Edition (OBIEE)  which is now available in My Oracle Support:


OBIEE 11g: Troubleshooting Crash Issues
Doc ID 1964727.2


This Knowledge Document guides you through a series of steps to assist in investigating a crash in an OBIEE 11g environment.

Along with the Overview and Getting Started sections, details are provided for Investigating a Crash and Common Crash Symptoms. If an issue is not resolved, the important information to provide within a Service Request are also outlined.

Where more information is required, the References section provides links to related documents, and a useful list of the Log & Configuration File Locations.

Additional Information:

If encountering Stuck Threads or Hang Issues, refer to our previous Blog post:

OBIEE 11g: Troubleshooting Stuck Threads or Hangs

Before proceeding to troubleshoot any issues Oracle highly recommends the latest Bundle Patch Set available be installed. For more information on the latest releases please refer to the following Knowledge Document:

OBIEE 11g: Required and Recommended Bundle Patches and Patch Sets
Doc ID 1488475.1

Questions specific to OBIEE ...

For questions or an issue that you can not identify - visit the OBIEE Community as a first step on your way to a solution: :

My Oracle Support Community
OBIEE

Monday Oct 21, 2013

EPM troubleshooting Utilities

(in via Maurice)

"
Are you keeping up-to-date with the latest troubleshooting utilities introduced from EPM 11.1.2.2? These are typically not described in product documentation, so you might miss references to them. The following five utilities may be run from the command line.

(1) Deployment Report was introduced with EPM 11.1.2.2 (11 April 2012).
It details logical web addresses, web servers, application ports, database connections, user directories, database repositories configured for the EPM system, data directories used by EPM system products, instance directories, FMW homes, deployment distory, et cetera.
It also helps to keep you honest about whether you made changes to the system and at what times! Download Shared Services patch 13530721 to get the backported functionality in EPM 11.1.2.1.

Run it from
/Oracle/Middleware/user_projects/epmsystem1/bin/epmsys_registry.sh report deployment
(on Unix/Linux)
\Oracle\Middleware\user_projects\epmsystem1\bin\epmsys_registry.bat report deployment (on Microsoft Windows).
The output is saved under
\Oracle\Middleware\user_projects\epmsystem1\diagnostics\reports\deployment_report.html


(2) Log Analysis has received more "press".
It was released with EPM 11.1.2.3 and helps the user to slice and dice EPM logs. It has many parameters which are documented when run without parameters, when run with the -h parameter, or in the 'Readme' file. It has also been released as a standalone utility for EPM 11.1.2.3 and earlier versions. (Sign in to  My Oracle Support, click the 'Patches & Updates' tab, enter the patch number 17425397, and click the Search button.
Download the appropriate platform-specific zip file, unzip, and read the 'Readme' file.
Note that you must provide a proper value to a JAVA_HOME environment variable [pointer to the mother directory of the Java /bin subdirectory] in the loganalysis.bat | .sh file and use the -d parameter when running standalone.)

Run it from
/Oracle/Middleware/user_projects/epmsystem1/bin/loganalysis.sh -h (on Unix/Linux)
\Oracle\Middleware\user_projects\epmsystem1\bin\loganalysis.bat -h (on Microsoft Windows).
The output is saved under the
\Oracle\Middleware\user_projects\epmsystem1\diagnostics\reports\
subdirectory.


(3) The Registry Cleanup command may be used (without fear!) to clean up various corruptions which can  affect the Hyperion (database-based) Repository.

Run it from
/Oracle/Middleware/user_projects/epmsystem1/bin/registry-cleanup.sh (on Unix/Linux)
\Oracle\Middleware\user_projects\epmsystem1\bin\registry-cleanup.bat (on Microsoft Windows).
The actions are described on the command line.


(4) The Remove Instance Command is only used if there are two or more instances configured on one computer and one of those should be deleted.

Run it from
/Oracle/Middleware/user_projects/epmsystem1/bin/remove-instance.sh (on Unix/Linux)
\Oracle\Middleware\user_projects\epmsystem1\bin\remove-instance.bat (on Microsoft Windows).


(5) The Reset Configuration Tool was introduced with EPM 11.1.2.2.
It nullifies Shared Services Hyperion Registry settings so that a service may be reconfigured. You may locate the values to substitute for <product> or <task> by scanning registry.html (generated by running epmsys_registry.bat | .sh).
Find productNAME in INSTANCE_TASKS_CONFIGURATION and SYSTEM_TASKS_CONFIGURATION nodes and identify tasks by property pairs that have values of 'Configurated' or 'Pending'.

Run it from
/Oracle/Middleware/user_projects/epmsystem1/bin/resetConfigTask.sh -product <product> -task <task> (on Unix/Linux)
\Oracle\Middleware\user_projects\epmsystem1\bin\resetConfigTask.bat -product <product> -task <task> (on Microsoft Windows).

"
Thanks to Maurice for this collection of utilities.


About


This blog talks about the latest news and upcoming events initiated by the EPM/BI Proactive Support Team.

Authors:

italia.nowodworska@oracle.com
torben.hein@oracle.com
paul.anderson@oracle.com
julie.foster@oracle.com





Search

Archives
« April 2015
SunMonTueWedThuFriSat
   
3
4
5
6
7
9
10
11
12
13
15
16
17
18
19
23
25
26
27
28
29
30
  
       
Today