E2E Root cause analysis in solution manager

Hi
How to add the E2E root cause analysis, the new functionality in solution manager 4.0 with the E2E root cause analysis functionality does it require support pack which level of SP required to use the new functionaltiy
Regards
Dinaker vikas

Hi,
If you have PI system in your landscape, I would strongly recommend to upgrade to SP15.
Trace monitoring for PI is to be available from SP17 (Not yet released)
Check [this Link.|http://service.sap.com/e2e].
Hope this solves your problem.
Feel free to revert back.
--Ragu

Similar Messages

How to do E2E root cause analysis?

Gurus:
Could you provide some "how-to" guides here about how to do E2E root cause analysis?
I have NO problem with E2E set up. My problem is after setting up, how to use it to do E2E root cause analysis?
Thanks!

>
Ashley Ho wrote:
> Could you provide some "how-to" guides here about how to do E2E root cause analysis?
Have you already visitited the Diagnostics Page and SolMan Ramp-Up Knowledge Transfer in SAP Support Portal?
[www.service.sap.com/diagnostics]
[www.service.sap.com/rkt-solman]
There is also a very interesting training available:
E2E100 Root Cause Analysis (I don't know the exact name)
Best regards,
Ruediger

What is the diff of Solution monitoring and E2E Root cause analysis

Hi,
I want to know what is the different for Solution Manager Solution Monitoring and End to End root cause analysis. Currently we have implemented change management and Implementing and Upgrading SAP Solutions, if i would like to explore the solution monitoring, and end to end root cause analysis, what is the steps of configuration i need?
if i would like to have a check on the system whether is performing well, or setup the functionality of sending alert when system is having problem, which feature would be better? end of end functionality or Solution Monitoring?
Please advice..
thanks
-Fung

Hi,
If you have PI system in your landscape, I would strongly recommend to upgrade to SP15.
Trace monitoring for PI is to be available from SP17 (Not yet released)
Check [this Link.|http://service.sap.com/e2e].
Hope this solves your problem.
Feel free to revert back.
--Ragu

Problem with E2E Root Cause analysis in EHP1

Hi All,
I'm facing a very strange problem with using the E2E RCA functionality in EHP1. The problem is when I select the systems that I want to analyse and click on a functionality such as change analysis, I get the following error message in SAP GUI:
Action canceled
Internet Explorer was unable to link to the Web page you requested. The page might be temporarily unavailable.
I'm fairly sure that this is a connectivity problem because it only happens on my client machines which are behind the firewall. If I connect to solution manager without going trough the firewall I can access the application. I have checked all firewall logs and it is not blocking anything. I also did a trace using wireshark but could not find anything suspicious.
Has anybody faced this problem? Any suggestions to resolve the problem?
Cheers,
Masoud

Hi,
If you have PI system in your landscape, I would strongly recommend to upgrade to SP15.
Trace monitoring for PI is to be available from SP17 (Not yet released)
Check [this Link.|http://service.sap.com/e2e].
Hope this solves your problem.
Feel free to revert back.
--Ragu

E2e Root Cause Analysis Checklist

Hello everyone,
I know I am close to getting some systems setup for RCA, but nothing is showing up in EWAs or within the RCA workcenter.
My system is currently at 7.01 SP05.
Since I've gone through the solman_setup and received all green lights through setting up my diagnostics system and a couple managed I don't know what else to get done. I know the managed system wizard is a step-through but I am asking for help setting up a checklist to make sure I've got everything installed and checked.
Configuration:
   Initial - complete
   Basic - complete
Diagnostics System
   setup wizard - green light
   advanced setup - green light
   upgrader - green light
Managed Systems
   I have a bunch of different systems with green lights under setup results; ABAP, JAVA, and Dual Stack
ISAGENT
   I've got updated isagents installed on each system
Wily
   Currently at the latest release and our Solution Manager system is connected
SMD Agents
   each server/LPAR has an agent installed and is attached
I'd like to finish this up but again I am missing something?!?
Thanks for any help on this one.
Ryan

Hello Ryan,
I would suggest you visit these two links:
> http://service.sap.com/diagnotics - media library - here you can get installation and troubleshooting guides
and
> http://service.sap.com/EWA
This way you have all the steps documented, and you can check what you have done so far against what is required, and identify the gaps.
Hopefully this information has been helpful.
Regards,
Paul

Root Cause Analysis (OS and DB - OS Command Console) Connection problem!

Dear Community,
i've got a problem with the Root Cause Analysis OS Command console!
Currently I try to read the System MemStat info from the console, without success!
I've got the following errors:
Error1:
Error to parse the data returns by 'SAPOSCol', cause :com.sap.smd.plugin.remoteos.exception.SAPOSColDataParserException: Unknown Error during the parsing of saposcol output; nested exception is:
java.lang.NullPointerException
Error2:
'SAPOSCol' Service not availbale, detail :com.sap.smd.plugin.remoteos.exception.SAPOScolNotAvailable: SAPOSCol not available (detail output: )
The saposcol service is running, when I look on the server, I've got the correct status:
server:<sid>adm> saposcol -s
Collector Versions :
running : COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux
dialog : COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux, 2007/02/16
Shared Memory       : attached
Number of records   : 5758
Active Flag         : active (01)
Operating System    : Linux server 2.6.5-7.283-smp #1 SMP Wed Nov 29
Collector PID       : 9536 (00002540)
Collector           : running
Start time coll.    : Wed Apr 23 15:00:58 2008
Current Time        : Wed Apr 23 15:12:08 2008
Last write access   : Wed Apr 23 15:12:04 2008
Last Read Access   : Wed Apr 23 15:12:03 2008
Collection Interval : 10 sec (next delay).
Collection Interval : 10 sec (last ).
Status              : free
Collect Details     : required
Refresh             : required
Header Extention Structure
Number of x-header      Records : 1
Number of Communication Records : 60
Number of free Com.     Records : 60
Resulting offset to 1.data rec. : 61
Trace level             : 2
Collector in IDLE - mode ? : NO
become idle after 300 sec without read access.
Length of Idle Interval : 60 sec
Length of norm.Interval : 10 sec
The strange thing is, sometimes it works, sometimes not!
Any Ideas?
System: Solution Manager 4.0 SP Stack 13
Thanks and regards
Sascha

>   running : COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux
>   dialog : COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux, 2007/02/16
I suggest you upgrade your saposcol on the Linux box, it's more than a year old and it's possible, that the SMD client needs a newer version that provides the data you're requesting.
Markus

Root Cause Analysis - Breakpoints in ABAP

Gurus ,
We had this breakpoints in the ECC - datasource extractors which got transported in the production and I have been given the task to identify the root cause analysis as to why was it not caught in dev,qa and testing.
can any one share their experience as to how to avoid this negligence and the additional steps required to ensure this does not happen again ?
Thanks in advance

Hi,
To identify the break points and avoid the transport of breakpoints. U can run the extended program check and there you can find in EPC error in superfluous statements the break points present in ur report.
Regards,
Vasanth

Building and deploying J2EE apps ? Now there is a solution for production root cause analysis.

Is your organization building and deploying J2EE apps? If so, Halo
can help solve one of the toughest issues facing enterprises today:
Finding the root cause of software faults.
"Halo monitors, pinpoints, reports on and provides a source-code level
root cause of software faults in deployed J2EE apps. Halo is unique
because it's the only technology that can give you a root cause
diagnosis in a fully deployed, live production application. Halo has
such low performance overhead that customers deploy their final,
production versions of their applications with Halo enabled.
Used with Web Application Servers like WebLogic, Halo helps ensure
that deployed code is reliable and able to be quickly fixed if
problems turn up. Most important, because Halo is an "always on"
technology, you get all the information you need to rapidly solve a
problem on the first fault. Problem replication and bug reports are
obsolete with Halo
"Halo has a unique ability to provide a root cause diagonosis and
understanding
of software problems in production systems, without needing to
replicate the
issue.
Test on WebLogic proved that Halo runs with extremely low overhead and
is suitable for use in deployed production systems"
Andrew Sliwkowski, Software Engineer
BEA Systems, Inc.
The key is Halo's high performance, low overhead TraceBack
instrumentation technology. Based on technology out of MIT and proven
in the field, TraceBack enables you to instrument JARs, EARs and WARs
within minutes, without touching source code.
Halo is useful throughout the entire application life cycle, from
development through test, beta and deployment.
If you have interest in learning more visit our website at
www.incer.com or email me directly at [email protected] (Rick Martin)

I have two questions. We have just started developing apps using jdev9i, 9iAS v2 and are new to the j2ee environment so my questions may be very easy ones.
Question 1: We have set up Oracle pooling connection to our databases. We have a development, test and production database. When I deploy my application, it includes the connections. This is preventing me from moving the EAR files from dev to test to prod without modification and re deploying to my EAR file. Is there a way or a place that I can put my database connections that will not be included in my EAR files and the application still find them?datasources.xml is where the info regradings connection to databases is licated. If you're using 9iAS
you can use EM to create datasource entry at the global level. In OC4J standalone you could use admin.jar
or edit the file. Check out the standalone user's guide at http://otn.oracle.com/tech/java/oc4j/pdf/oc4j_so_usersguide_r2.pdf.
Also, you will othe OC4J docs on OTN.
Question 2: I have a stand alone oc4j set up for our developers to use while testing their applications. The applications include libraries supplied in jdev such as xml parser v2. I do not want to deploy those lib files with the app because I will have to redeploy all my apps if I upgrade jdev. I just want to be able to upgrade the libraries, test the apps and not have to redeploy everything. I can do this by coping the jdev lib to 9iAS but I can't seem to find the right place to put the lib for the stand alone oc4j instance. You can use the library tag within application.xml for server wide availability. Check out the article
http://otn.oracle.com/oramag/oracle/02-sep/o52oc4j_2.html specifically class loading in OC4J section
Any help would be greatly appreciated. Thanks in advance.

Tools for root cause analysis of stack corruption?

I'm experiencing extremely rare stack corruption that results in SEGV core dumps for a large and complex C++ program. Having run all the standard tools such as IBM Rational Purify, Sun mdb/libumem and dbx/rtc (although unfortunately using dbx check -access takes inordinately long and eventually crashes before the main() function is executed), I am no closer to discovering the root cause of the stack corruption. I'm confident based on the tools run and on the stack trace from the core dump that the problem is not heap corruption, but stack corruption.
The environment is Sun Studio 12 (but not update 1) on Solaris 10 on SPARC. The program is compiled with minor optimisation (-xO2 -xbuiltin=%all).
Is anyone aware of other tools or approaches that could help pinpoint the problem? Your help would be much appreciated!
Thanks in advance,
Simon

If you are in fact having stack corruption issues, I don't think any of the tools you mentioned other than Purify would help you identify it.
You may also be simply running out of stack space, and not having corruption issues. Is your app multi-threaded? If so, you could increase the stack size your threads use to something larger than the default.
Another thing you can look for are syslog entries stating "no swap space to grow stack" for your process, you've run out of virtual memory. To avoid this, you can "pre-allocate" your stack memory with code similar to this:
void growStack( size_t bytes )
    char *mem = ( char * ) alloca( bytes );
    memset( mem, 0, bytes );
    return;
}That code, when called, will force the creation of stack memory virtual pages backed by swap, before your server gets into a situation where free memory might be in short supply.
I also seem to recall that Solaris under certain circumstances will allocate stack memory with the MAP_NORESERVE option, which means swap space won't be reserved for your stack. If your process gets swapped out, its stack(s) will be lost and you'll probably get a SIGSEGV or SIGBUS. See this bug:
[http://bugs.opensolaris.org/view_bug.do?bug_id=1221729|http://bugs.opensolaris.org/view_bug.do?bug_id=1221729]
I remember working a similar issue for a customer running large apps on Sun E15Ks, maybe about 5 years ago. To work around this behavoir, I think you'll need to explicitly allocate stack memory for any threads you may be creating. I think that's what we had to do.

Functional and Technical Administration Roles in Solution Manager

Hello
A big company has been implementing new functionality in Solution Manager during the last couple of years, they started with System Monitoring and EWA, Maintenance Optimizar, then Project Implementation, now Service Desk and ChaRM. This is company has a wide open structure in IT and a discussion has been raised about who is the owner of soluton manager in IT.
In my experience I always propose two main roles one is Technical Administrator Role and the other is Functional Administrator role. The former is more basis oriented, in charge of the installation and update of stacks in Solman, basic-initial configuration and then working mainly in setting Solutions, RFCs, System Monitoring, EWA, SAP services, OSS connections, Diagnostic, E2E Root Cause Analysis and also support in ChaRM (in setting up the transport routes, security)
On the other hand, I support a role of SolMan Functional Administrator which deals with Implemenation side, ASAP methodologies, business process definition, integration with ARIS, setting up project standards, coaching Project Managers, ensuring good application information. Also in Service Desk and ChaRM, setting the process, customizing, implementing and controlling that things are running smooth in SolMan productive.
I would like to get from you your inputs and experiences regarding how to set-up those roles, whether there are clear lines to divide responsiblities or what kind of definitions should be made.
Many thanks
Esteban Hartzstein
Director
Tebyon Consulting

As recommended by some colleagues I am also investigating Customer Center of Excelence as a reference to define roles and responsibilities, particularly in the concept of Application Lifecycle Management.
Any other input is welcome.
Regards
Esteban

Solution manager 7.1 SP04 dump

Dear Experts,
I am getting follwing abap dump after configuring managed system in Solution manager.
I have already implemented SAP central note for Solman 7.1 SPS 04. Please suggest me how to resolve this issue as i am getting morethan 5000 dumps a day.
Regards,
Cinu

Hi Sinu,
Refer below note also,
1680556 - E2E Root Cause Analysis causes "CREATE_DATA_UNKNOWN_TYPE
Regards
K.N

Connect two Solution Manager systems.

Hello,
We are planning to couple two Solution Manager systems.
We want to get all the alerts ABAP+JAVA(Root Cause) from one Solution Manager to the other.
What are te steps to take?
Connect the SLD's?
Connect the systems thru RFC?
Point all the agents to the 2 Solution Manager systems?
Regards,
Mike Geluk

Hello,
It is possible.
For SLD, two options:
- Each Solution Manager can use its own SLD. Then you must define the other server in the SLD, and vice-versa.
- Each Solution manager can connect to a central SLD where the two are defined.
The rest is just like any other managed system configuration: follow the steps in solman_setup.
Best regards,
Guiilherme

Configuration Solution Manager - Travel Management for Route Cause Analisys

Hi,
Can you describe how to configure Solution Manager to monitor (RCA-E2E) our Travel System (SAP Enterprise Portal + SAP HR)?
Best regards,
Diego.

Hi,
RCA configuration remain same for all the module/component
All the steps are there in RCA Configuration thread
SPRO>SAP SOlutionManager Implementation Guide> SAP Solution Manager>Basic settings> Root Cause analysis
here you can find all the information regarding setup, please follow one after the other.
Regards,
Shyam.

E2E Solution manager Diagnostic

Hi,
I want the model question for the E2E 100(End to End Solution Manager Diagnostic). I need to apper in the certification. Can anybody provide me the model question for this certification or need a guidence for the preparation.............
very thankful to you.
regards,
shanti

Hello,
Are you using versin 8.0? If not use version 8.0.
Regards,
Paul

EWA for Business Objects (XI 3.1) within SAP Solution Manager

Hello!
We use Business Objects (XI 3.1) and would like to get weekly a EWA report within our SAP Solution Manager.
Our SAP Solution Manger has only ABAP stack and it has the SPS version 25.
We also do not use Wily Introscope/Diagnostics and E2E tools within SAP Solution Manager.
Question
Is it possible to set up EWA for Business Objects with our requirements (SOLMAN with ABAP stack and without E2E/Diagnostics tools)?

Hello,
The short answer is no. You can verify this in SAP Note 1507629 - Preparing a BOE system for Service Sessions in Sol. Manager.
"...1.) Managed System Setup
Perform the Managed System Setup for SAP BusinessObjects Enterprise as
described in the "End-to-End Root Cause Analysis System Landscape Setup
Guide". This guide can be found in the SAP Service Market Place:
-> http://service.sap.com/diagnostics
-> Navigate to the "Media Library"
-> Open the document "SAP Solution Manager Landscape Setup Guide"
Please ensure that you perform all steps mentioned in the guide which
are relevant for your product and version. Please read also SAP note
1357901, which is also referred to in the above mentioned setup guide."
So this is a requirement. There are also pdf documetns attached to this note that describe how to setup the EWA in Solution Manager. EGI_SBOP_EWA_part1.pdf and EGI_SBOP_EWA_part2.pdf.
The fact you have no Java stack and have not installed Diagnostics, just means it has not been done. It can be done and then you can do a managed system setup, and the balance of tasks required to prepare the system and Solution manager to generate EWA reports for the BOE system. Its just more work, not a show stopper.
Regards,
Paul

E2E Root cause analysis in solution manager

Similar Messages

Maybe you are looking for