SMD E2E Trace Anaysis Fails

Hi
On Clicking on SMD E2E Trace Analysis the following message is shown on the UI
"type com.sap.sup.admin.e2e.trace.wd.model.types.Syuzeit could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection"
SMD SP 12
LMSERVICE SP 12
Any Ideas?
-Log file--
#1#com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.sap.sup.admin.e2e.trace.wd.model.types.Syuzeit could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
     at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
     at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
     at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:448)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:386)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:415)
     at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:79)
     at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:121)
     at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:117)
     at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:212)
Caused by: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
     at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:377)
     at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:322)
     at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:181)
     at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
     at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
     at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
     at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
     at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
     at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
     ... 61 more
Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:152)
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:178)
     at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:62)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
     ... 71 more
Caused by: java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4AppServerJCODestination(JCOClientConnection.java:704)
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:478)
     at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:233)
     at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:218)
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:129)
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150)
Regards,
Vikram

Hi Paula,
Thanks for the speedy response.
No I don't think I have performed any step to create JCO connections on SLD. Do you have any details on the steps?
Do you think it would be wise to wait for SP13? Wonder why have SAP is forcing customers to buy the SMD Starter Pack.
Regards,
Vikram

Similar Messages

SMD E2E Trace analysis - Urgent!!

Hi,
I have configured Root cause analysis for r/3 system. Everything is working but unable to enable the system in Trace analysis. Its says, Trace status could not be evalutated.
The system meets all the prerequisites in note 1061383 and Exeption,Configuration analysis are working fine for it.
Please help
Ajay Kande

Make sure your RFC destinations in java in monitored system to the SLD are working correctly, ie VA > Server > Services > SLD Data Supplier.
Do a "trigger" to make sure you can pass info to the SLD.

(DB) ERROR: db_connect rc = 256 DbSl Trace: CONNECT failed with sql error '-2'

Hi Experts,
I have an error when I copy Homogeneous in SOLMAN, I do the import of the database and this error occurs:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
/usr/sap/SOP/SYS/exe/uc/linuxx86_64/R3load: START OF LOG: 20140407112019
/usr/sap/SOP/SYS/exe/uc/linuxx86_64/R3load: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#21 $ SAP
/usr/sap/SOP/SYS/exe/uc/linuxx86_64/R3load: version R7.20/V1.4 [UNICODE]
Compiled Mar 18 2014 22:40:46
/usr/sap/SOP/SYS/exe/uc/linuxx86_64/R3load -testconnect
(DB) ERROR: db_connect rc = 256
DbSl Trace: CONNECT failed with sql error '-2'
(DB) ERROR: DbSlErrorMsg rc = 99
/usr/sap/SOP/SYS/exe/uc/linuxx86_64/R3load: job finished with 1 error(s)
/usr/sap/SOP/SYS/exe/uc/linuxx86_64/R3load: END OF LOG: 20140407112019
I need help to correct this error.

Hi Michal,
Login with ora<SID> and check whether you are able to connect to sqlplus ( do steps as below )
1. sqlplus "/as sysdba"
2. select status from v$instance.
Let us know the ouput of both the command
Thanks
Anil

DbSl Trace: CONNECT failed with sql error '12518' at IMPORT ABAP

Hi
We are trying to install ECC 6.0 on windows 2008 SP2 and oracle 10.2.0.4. We get an error at IMPORT ABAP phase.
content of import_monitor.java :
java version "1.4.2_26"
Java(TM) Platform, Standard Edition for Business (build 1.4.2_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_26-b03, mixed mode)
Import Monitor jobs: running 1, waiting 1, completed 26, failed 0, total 28.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.
content of SAPSLOAD.log:
E:\usr\sap\UED\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100705173108
E:\usr\sap\UED\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP
E:\usr\sap\UED\SYS\exe\uc\NTAMD64\R3load.exe: version R7.01/V1.4 [UNICODE]
Compiled Feb 24 2009 23:41:07
E:\usr\sap\UED\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -stop_on_error
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12518
DbSl Trace: CONNECT failed with sql error '12518'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12518
DbSl Trace: CONNECT failed with sql error '12518'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12518
DbSl Trace: CONNECT failed with sql error '12518'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12518
DbSl Trace: CONNECT failed with sql error '12518'
(DB) ERROR: DbSlErrorMsg rc = 99
E:\usr\sap\UED\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
E:\usr\sap\UED\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100705173108
content of sqlnet.log file:
Fatal NI connect error 12560, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleUED)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(SID=UED)(CID=(PROGRAM=E:\oracle\UED\102\bin\sqlplus.exe)(HOST=U34SSAPUED)(USER=uedadm))))
VERSION INFORMATION:
     TNS for 64-bit Windows: Version 10.2.0.4.0 - Production
     Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 10.2.0.4.0 - Production
Time: 05-JUL-2010 16:19:39
Tracing not turned on.
Tns error struct:
    ns main err code: 12560
    TNS-12560: TNS:protocol adapter error
    ns secondary err code: 0
    nt main err code: 530
    TNS-00530: Protocol adapter error
    nt secondary err code: 2
    nt OS err code: 0
Fatal NI connect error 12518, connecting to:
(DESCRIPTION=(ADDRESS=(COMMUNITY=SAP.WORLD)(PROTOCOL=TCP)(HOST=u34ssapued)(PORT=1527))(CONNECT_DATA=(SID=UED)(GLOBAL_NAME=UED.WORLD)(CID=(PROGRAM=E:\usr\sap\UED\SYS\exe\uc\NTAMD64\R3load.exe)(HOST=U34SSAPUED)(USER=uedadm))))
VERSION INFORMATION:
     TNS for 64-bit Windows: Version 10.2.0.2.0 - Production
     Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 10.2.0.2.0 - Production
Time: 05-JUL-2010 17:28:38
Tracing not turned on.
Tns error struct:
    ns main err code: 12564
    TNS-12564: TNS:connection refused
    ns secondary err code: 0
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0
Best Regards...,

Hi,
TNS-12560: TNS:protocol adapter error
Probably your listener or database is down...
If both are running, just stop the installation and reboot the server.
Then again start listener and database and continue SAP installation with "Continue old installation" option..
Also make sure that below environment variables are set properly...
ORACLE_HOME
ORACLE_SID
DBSID
Regards.
Rajesh Narkhede

E2E trace analysis in Solman

Dear all,
I have some question about the E2E trace analysis on solman. Hope you can help me!~
1. We are using Solman 7.1 SP6 and we will upgrade to SP10 or SP11 in recent months. We want to use solman RCA trace analysis to trace ERP ABAP program. Could anyone can told me how to do this? I can do the HTTP trace in solman with RCA trace analysis but I don't know whether we can also nalysis the ABAP trace in solman.
2. We have many printers in our PRD systems and all printers connected to a SPRINTER server. Now we need some suggestion on how we can monitoring these printers with solman. Also we hope to use the RCA tools to nalaysis the problem on printer such as the printer are offline/dead halt/printing very slowly and so on.
Is this possible?

Hi Yushuai,
1. Using E2E in SolMan you can capture the movement of request and response to any JAVA and ABAP system. It will show you that what ABAP program has been called but It will not tell you what happening inside ABAP program.
Regards,
Ravi Maheshwari

ORA-48913: Writing into trace file failed

Hi
my OS: OUL5x64
DB: 11.1.0.7
receive this error in alert.log but could not figure out which parameter to increase.
Can someone please help.
Non critical error ORA-48913 caught while writing to trace file
Error message: ORA-48913: Writing into trace file failed, file size limit [10485760] reached
the suggestion:
ORA-48913: Writing into trace file failed
*Cause:An attempt was made to write into a trace file that exceeds the trace's file size limit
*Action:increase the trace's file size limit.
Thanks in advance.

Hi ,
I have one more doubt :
ORACLE_SID=XXXX
/XXXX/XX/ofaroot/XXXX/diag/rdbms/xxxx/XXXXX/trace
Non critical error ORA-48913 caught while writing to file "trace /XXXX/XX/ofaroot/XXXX/diag/rdbms/xxxx/XXXXX/trace/XXXX_ora_8218.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [10485760]everywhere its written to increase the parameter max_dump_file_size or to relocate the alert log, but as far as i understand ,
is this because a trace file with the name XXXX_ora_8218.trc was getting generated with a greater size than the one defined in max_dump_file_size. Is this what happened ?
Also , I am not able to find what directory does this parameter points to ? is it the trace directory or diag directory ?
i checked select * from v$diag_info ,but i could not find any conclusion.
Probably , on getting the above info , i will be able to decide where to move the alert.log to create space.

DbSl Trace: CONNECT failed with sql error '12154'

Hi
I am trying to install DB instance , platform -> IBM AIX 5.3 , Database - Oracle 9i, sap version -> 4.7. I am getting error at Database load phase. The listener is started successfully, TNS ping is ok. Host file edited with proper ip address and the hostname, Still the error is same.
DbSl Trace: CONNECT failed with sql error '12154'
I am able to connect to oracle idle instance .
Please help me in solving this issue
Regards
Prasanna.B.S

Hi,
Good evening and greetings,
Please go through the following OSS Note
Note 324714 - DB connect error in TMS after Oracle upgrade/change
Please reward points if found useful
Thanking you
With kindest regards
Ramesh Padmanabhan

DbSl Trace: CONNECT failed with sql error '12170'

Hi,
I'm having this problem during installation of DB instance. I already installed Oracle patchSet. Could you some tell me what could be the issue.
SAP Release: NW 2004s SR1
SAP Variant: ABAP
OS: Solaris 10 64 Bit
Oracle: 102_64
INFO       2006-11-16 11:32:19
           CJSlibModule::writeInfo_impl()
Output of /usr/sap/RED/SYS/exe/run/R3load -testconnect is written to the logfile R3load.exe.log.
WARNING    2006-11-16 11:47:19
           CJSlibModule::writeWarning_impl()
Execution of the command "/usr/sap/RED/SYS/exe/run/R3load -testconnect" finished with return code 2. Output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
/usr/sap/RED/SYS/exe/run/R3load: START OF LOG: 20061116113220
/usr/sap/RED/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
/usr/sap/RED/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
Compiled Apr 1 2006 03:18:31
/usr/sap/RED/SYS/exe/run/R3load -testconnect
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12170
DbSl Trace: CONNECT failed with sql error '12170'
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12170
DbSl Trace: CONNECT failed with sql error '12170'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12170
DbSl Trace: CONNECT failed with sql error '12170'
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12170
DbSl Trace: CONNECT failed with sql error '12170'
(DB) ERROR: DbSlErrorMsg rc = 99
/usr/sap/RED/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/RED/SYS/exe/run/R3load: END OF LOG: 20061116114718
ERROR      2006-11-16 11:47:19
           CJSlibModule::writeError_impl()
CJS-30023 Process call '/usr/sap/RED/SYS/exe/run/R3load -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.
ERROR      2006-11-16 11:47:19 [iaxxgenimp.cpp:736]
           showDialog()
FCO-00011 The step testDatabaseConnection with step key |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|8|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|testDatabaseConnection was executed with status ERROR .
Thanks
Torpedo

Hi ram
Just brief ur Env please ..
If you are receiving the ora-12535 error from tnsping as well as sqlplus, the client box is probably unable to find the listener for whatever reason. If the listener is definitely running and you are able to ping the listener's address from the client box but still can't tnsping it, you are probably running into a firewall issue.
The reason for this is that with tnsping failing you are probably timing out before the connection gets to the listener. You can verify that the listener is running by checking the status in lsnrctl or doing a loopback connection through it. You can verify that the listener's address is visible to the remote box by pinging it from the remote box. Firewalls generally filter by port number so this is the next logical thing to check. If the remote connection passes through a firewall and the listener's port has not been opened up you will see this error.
regards
Vinod

SMD Post installation activities failed.

Hi Gurus
I have installed Solution Manager 4.0 with SLD SP09 now i want to setup SMD on same server. I have successfuly deployed LMSERVICE*.sca file and trying to du SMD upgrader step in one of the step "scheduler upgrade" i am getting following error.
Any body can help on this.
Thanks in advance.
Shriraj
Report Upgrade for Scheduler Upgrade
Status: Fail in 283ms.
Upgrade Result:
Data Collector integration: Error during Scheduler tasks upgrade: Task's class not found while trying to instanciate it!
Exception Cause:
com.sap.sup.admin.scheduler.exception.TaskBrowseException: Task's class not found while trying to instanciate it!
     at com.sap.sup.admin.scheduler.JmsScheduler.getTaskList(JmsScheduler.java:861)
     at com.sap.sup.admin.scheduler.JmsScheduler.getTaskList(JmsScheduler.java:777)
     at com.sap.sup.admin.scheduler.JmsScheduler.getTasks(JmsScheduler.java:614)
     at com.sap.sup.admin.scheduler.upgrade.sp15.DataCollectorIntegration.execute(DataCollectorIntegration.java:37)
     at com.sap.sup.admin.scheduler.upgrade.SchedulerUpgrade.execute(SchedulerUpgrade.java:56)
     at com.sap.smd.SMDUpgradeManager.executeUpgrade(SMDUpgradeManager.java:155)
     at com.sap.sup.admin.smd.upgrader.SMDUpgraderComponentView.onActionUpgrade(SMDUpgraderComponentView.java:394)
     at com.sap.sup.admin.smd.upgrader.wdp.InternalSMDUpgraderComponentView.wdInvokeEventHandler(InternalSMDUpgraderComponentView.java:229)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.ClassNotFoundException: com.sap.sup.admin.scheduler.task.e2e.loganalysis.LogAnalysisTask
Loader Info -
ClassLoader name: [sap.com/tcwebadministratorsolmandiag]
Parent loader name: [Frame ClassLoader]
References:
   common:service:http;service:servlet_jsp
   service:ejb
   common:service:iiop;service:naming;service:p4;service:ts
   service:jmsconnector
   library:jsse
   library:servlet
   common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
   library:ejb20
   library:j2eeca
   library:jms
   library:opensql
   common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
   interface:resourcecontext_api
   interface:webservices
   interface:cross
   interface:ejbserialization
   interface:tcsecdestinations~interface
   interface:keystore_api
   interface:security
   library:com.sap.mw.jco
   library:com.sap.util.monitor.jarm
   library:com.sap.exception
   library:sapxmltoolkit
   library:tcSLUTIL
   library:jnet
   library:core_lib
   service:webdynpro
   service:webservices
   service:rfcengine
   service:timeout
   library:com.sap.aii.proxy.framework
   service:tcsecdestinations~service
   service:tcsmdserver~service
   sap.com/tcsmdagentapplicationfilesystem
   sap.com/tcsmdagentapplicationpar
   sap.com/tcsmdagentapplicationdatacollector
   sap.com/tcsmdagentapplicationremoteos
   sap.com/tcsmdagentapplicationremotesetup
   sap.com/tcsmdagentapplicationglobal~conf
Resources:
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/AbapConnectorLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/ThreadDumpScanLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/LandscapeLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/ComponentInfoLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/confchangereportlib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/EwaIsData.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/LoggingLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/NwawrapperLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/ConfigTaskLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/classes
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/LandscapeAgentLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/systemlandscapeupload_task.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/work
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/WSCheckAuthLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/HttpAnalysisLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/RemoteLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/EwaPar.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/SecurityLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/UpgradeLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/InterAppLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/schedulertasks.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/MemSnapshotLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/IntroscopeJDBC.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/DatabaseLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/SelfCheckLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/EwaGca.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/schedulerlib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/NavigationLib.jar
   /usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/OsCommandLib.jar
Loading model: {parent,references,local}
     at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:382)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:141)
     at com.sap.sup.admin.scheduler.JmsScheduler.getTaskList(JmsScheduler.java:803)
     ... 36 more

Hi Shriraj,
For configuring solution manager diagnostics in my landscape i used the following document available in service market place,
"SAP Solution Manager 4.0 (SP10)
End to End Diagnostic
Powered by SAP NetWeaver 04s SPS 11"
This document was very helpful and i successfully configured SMD.
Moreover you will have to download Willy Interoscope also.
Hope this will help you out.
Thanks and Regards
Manas

Install SMD agent on EP6 fails

Hi,
I get an error when installing SDM agent on EP6 (HP-UX):
STEP 7: checking P4 Connection and SMD Agent Registration
External Command Executed:
/opt/java1.4/bin/java -DP4ClassLoad=P4Connection -Dsap.p4.remote_classloading=false -cp ":/usr/sap/SMD/J97/SMDAgent/lib/sapxmltoolkit.jar:/usr/sap/SMD/J97/SMDAgent/lib/smdagent.jar:/usr/sap/SMD/J97/SMDAgent/lib/tc_sec_secstorefs.jar:/usr/sap/SMD/J97/SMDAgent/lib/iaik_jce_export.jar:/usr/sap/SMD/J97/SMDAgent/lib/launcher/logging.jar:/usr/sap/SMD/J97/SMDAgent/lib/smdserver.jar:/usr/sap/SMD/J97/SMDAgent/lib/exception.jar:/usr/sap/SMD/J97/SMDAgent/lib/sapj2eeclient.jar:/usr/sap/SMD/J97/SMDAgent/lib/launcher/smdagentlauncher.jar:" com.sap.smd.setup.Setup /p4connection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
P4 Connection succeeded but SMD Agent Registration failed
Root exception is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of smdserver.
I couldn't find anything on SAP Market Place but a similar thread here advised to check if SDM servers is not in maintenance mode.
Well, it's not.
Can someone please help?
Thx
Bert

Hi,
Did you connect to smd server http://host:port/smd and desactivate maintenance mode in Agent Administration page?
This should solve your issue.
Regards,
Frederic

Trac upgrade failed on console.py

I just upgrade trac from 0.12.3-1 -> 1.0-1
It ask me to do 'trac-admin <repo_path> upgrade.
When I done, it shows
The upgrade failed. Please fix the issue and try again.
AttributeError:
I checked the trac.log:
2012-09-21 13:03:57,574 Trac[console] ERROR: Exception in trac-admin command:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/trac/admin/console.py", line 108, in onecmd
rv = cmd.Cmd.onecmd(self, line) or 0
File "/usr/lib/python2.7/cmd.py", line 220, in onecmd
return self.default(line)
File "/usr/lib/python2.7/site-packages/trac/admin/console.py", line 284, in default
return cmd_mgr.execute_command(*args)
File "/usr/lib/python2.7/site-packages/trac/admin/api.py", line 124, in execute_command
return f(*fargs)
File "/usr/lib/python2.7/site-packages/trac/env.py", line 970, in _do_upgrade
self.env.upgrade(backup=no_backup is None)
File "/usr/lib/python2.7/site-packages/trac/env.py", line 686, in upgrade
if participant.environment_needs_upgrade(db):
File "/home/python/mytrac/tagsplugin/tractags/model.py", line 23, in environment_needs_upgrade
if self._need_migration(db):
File "/home/python/mytrac/tagsplugin/tractags/model.py", line 45, in _need_migration
db.rollback()
File "/usr/lib/python2.7/site-packages/trac/db/util.py", line 107, in __getattr__
raise AttributeError
AttributeError:

I just upgrade trac from 0.12.3-1 -> 1.0-1
It ask me to do 'trac-admin <repo_path> upgrade.
When I done, it shows
The upgrade failed. Please fix the issue and try again.
AttributeError:
I checked the trac.log:
2012-09-21 13:03:57,574 Trac[console] ERROR: Exception in trac-admin command:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/trac/admin/console.py", line 108, in onecmd
rv = cmd.Cmd.onecmd(self, line) or 0
File "/usr/lib/python2.7/cmd.py", line 220, in onecmd
return self.default(line)
File "/usr/lib/python2.7/site-packages/trac/admin/console.py", line 284, in default
return cmd_mgr.execute_command(*args)
File "/usr/lib/python2.7/site-packages/trac/admin/api.py", line 124, in execute_command
return f(*fargs)
File "/usr/lib/python2.7/site-packages/trac/env.py", line 970, in _do_upgrade
self.env.upgrade(backup=no_backup is None)
File "/usr/lib/python2.7/site-packages/trac/env.py", line 686, in upgrade
if participant.environment_needs_upgrade(db):
File "/home/python/mytrac/tagsplugin/tractags/model.py", line 23, in environment_needs_upgrade
if self._need_migration(db):
File "/home/python/mytrac/tagsplugin/tractags/model.py", line 45, in _need_migration
db.rollback()
File "/usr/lib/python2.7/site-packages/trac/db/util.py", line 107, in __getattr__
raise AttributeError
AttributeError:

SMD E2E: Configuration Analysis

Hi!
I can already see the data for E2E Workload Analysis.
Unfortunately I cannot see the data under the tab "E2E Configuration".
Can some one tel me how to proceed with with errors/warnings?
No SID found for value 'E11 0020198811012003146909000001927' of characteristic 0SMD_FSRC
Invalid filter on 0SMD_FSRC: Filter changed
Characteristic 0SMD_CSAL was changed in InfoCube 0SMD_CA01. Adjust the query
What I have already done
tcode RSRT --> Gen. query directly --> "0SMD*"
tcode CCMSBISETUP --> Sceanrio "E2E"
Any helpful information will be appreciated
regards
Thom

Hi,
I'm trying to setup E2E. Diagnostics server (BI client in solman) & Managed system setup was done.
I don't see any graphs(at least plain) in solman. I observed that extractor jobs are failing, also i dont see any info objects under solman diagnostics in TC - RSA1.
Please guide.
Thanks in advance.

SMD, E2E, Ehp1 ???

I have a Solman 7.0 SPS 16 that was upgraded from a 3.2 system. I have also added a Java Add-In to this system. My original goal was to install SMD. But when you go to \service.sap.com\diagnostics, it points you to End to End diagnostics. So I figured SAP just renamed the function but when installing Wiley it wants you to use SMD. They only install guide I can find for SMD is for a 4.0 system. Is there a 7.0 install guide for SMD? Is SMD the same as E2E and what is Ehp1? Thank you in advance for the enlightenment.

Renamed version of Solman 4.0 is the Solman 7.0
So, Installation guide for SMD on solman4.0 is same as on 7.0
You will get those guides as per you NW version and SP stack level.
SMD is just one component of E2E. To configure E2E between the satellite systems and the Solman system, SMD is one of the components among SMD agent, willy Introscope agent etc...
EhP1 is the enhancement pack 1 stack for SAP systems. Solman EhP1 is the SP stack 18. Means, to upgrade the solman system more than the SP 17, you need to apply EhP1.
You have to read a lot...continue with that diagnostic link and service.sap.com/solutionmanager and the SAP Notes

Workload Datacollection for BI in SolMan system(SMD/E2E)

I am unable to collect workload data in solman from BI system and every task under specific BI system tab and Overview tab is saying that that "no applicable data found".Tried with all time periods.
If I see extractor jobs (E2E_EXTRACTOR_COLLECTOR) job for BI ,the result log is saying that
all sub-extractors under EC: Main Extractor      E2E_ME_RFC are working fine and writing data to persistance.
But the sub-extractors under Main Extractor      E2E_ME_ST_API are unable to execute because of below error
EC: Extractor           F90_CA_NOTES
ME: 06:33:45 UTC Calling Extractor F90_CA_NOTES
ME: 06:33:45 Receiving return code     8   from F90_CA_NOTES
ME: 06:33:45 Extractor Error: E Subroutine CE2_EXECUTE_ACTION not found/not executable.
EC: 06:33:45 UTC Main Extractor raises exception. No Data returned by extractor.
If any one is having any ideas then please let me know.
I hope above info is enough to give some inputs!.
Thank you.
Srikanth.M

Hi,
Please activate we templates in BI system in T-code RSA1-> BI content->Web Template (Format SAP BW 3.x) --->Select Objects
double click and select your required template and activate.
Regards,
Teja.

EU_IMPORT5: DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1017

Hi,
The upgrade is on phase EU_IMPORT5 and it seems to run for a long time. But am afraid it this is really true. When I look in the file: E000006.DPR I find the following:
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1017
DbSl Trace: CONNECT failed with sql error '1017'
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(SQL) INFO: SSEXC.SQL not found
(DB) INFO: DOKHL~ created #20081003122232
(IMP) INFO: import of DOKHL~ completed (2185665 rows) #20081003125935
(DB) INFO: DOKHL^0 created #20081003125948
(DB) INFO: DOKIL~ created #20081003125949
Is this means that it stoped?
Thanks in advance
HanseAtik

Hi,
Check in SAPup.log if you're not requested to do an action .
You'll probably see
>Continue ?
>Exit ?
If yes, just stop SAPup and restart, you'll be asked again.
Hope that was helpfull.

SMD E2E Trace Anaysis Fails

Similar Messages

Maybe you are looking for