CIM_ERR_FAILED: No such instance: SAP_XIAdapterFramework.CreationClassName=

Hi friends
I have read all the old postings about this problem on SDN with all the links
that the users have suggested. It hasn't helped and so I am putting this problem here.
Any feedback will be greatly appreciated.
When I ran sxi_cache I kept getting the following errors.
Unable to refresh cache contents: Error during last attempt to refresh cache
So as per the suggestion from one of the experts on this forum, I ran the steps in Note:764176, to make sure that there are no inconsistensies in SLD contents.
It hasn't helped.
However as per the second step in the Note:764176 , I selected all the domains and XI components for the host and deleted them by pressing REMOVE.
It removed the stuff but gave an error message as follows.
CIM_ERR_FAILED: No such instance: SAP_XIAdapterFramework.CreationClassName="SAP_XIAdapterFramework",Name="af.cpi.dm32583"
The reason for checking the cache was that I have created a simple
File to File and
File to RFC scenario.
These were working very well but now has stopped working for no apparent reasons.
The file gets picked up from the source but not reaching the destination.
I checked RWB and everything looks ok with GREEN buttons (including cc channel etc.,).
The only problem that I am seeing is this cache problem when i use 'sxi_cache'.
Refreshing this is not solving the problem
Hope to hear from XI gurus.
Thanks
Ram

Hello, I have the same problem with CIM_ERR_FAILED: No such instance. Can you please give more detail what is the cause of the error and how you fixed it? Thanks!

Similar Messages

WLC 5508 version 7.3.112.0 : SNMP No Such Instance

Dear all,
I've set SNMP community v2c read-only on the controller and then trying to parse a specific OID with a MIB Tool with that community
but the following OID always returns "No such instance".
Controller Model : 5508 version 7.3.112.0
Object
clsSysApConnectCount
OID
1.3.6.1.4.1.9.9.618.1.8.4
Type
Unsigned32
Permission
read-only
Status
current
MIB
CISCO-LWAPP-SYS-MIB ; - View Supporting Images
Description
"This object specifies the count of AP's that are
connected with WLC"
Any solutions ?
Thanks

Hi
Only Cisco TAC can analysis this & tells you exact reason of this reload. It looks like a software related crash..
I would suggest to move onto a later code (like 7.4.121.0) rather staying in 7.3 code when you get the new hardware.
HTH
Rasika
**** Pls rate all useful responses ****

Adapter Engine no register in SLD.

Hi,
The Adapter Engine not this registered in SLD-> Technical Systems -> Process Integration.
The version in that we are working is:
SAP_ABA 711 0004 SAPKA71104
SAP_BASIS 711 0004 SAPKB71104
PI_BASIS 711 0004 SAPK-71104INPIBASIS
ST-PI 2005_1_710 0003 SAPKITLQJ3
SAP_BW 711 0004 SAPKW71104
Also we have applied the following SAP notes:
1031321 u2013 Self-Registration of Adapter Engine and RWD fails
764176 u2013 Error in XI inconsistent SLD content
1278562 u2013 Specification of message server host in Exchange Profile
Log:
- defaultTrace
#2.0 #2010 03 10 13:17:37:097#+0100#Error#com.sap.nw.lm.aci.engine.base.sld.connection.AccSldConnector#
#BC-AC-7XX#sap.com/tclmacienginebaselib05#005056911C95111C0000000100001234#7161750000045479#sap.com/tclmacimonitor~app#com.sap.nw.lm.aci.engine.base.sld.connection.AccSldConnector.getSldComputerSystemsForMonitoring(String)#AGUZMAN#0#SAP J2EE Engine JTA Transaction : [06d47ffffff96006d43]#2218C4902C1811DFCB06005056911C95#2218c4902c1811dfcb06005056911c95#2218c4902c1811dfcb06005056911c95#0#Thread[Managed_Application_Thread_21,5,Managed_Application_Thread]#Java##
Unable to obtain Computer Systems, associated to NW Admin NWA_FOR_FirstLandScpSrvcName, from SLD. CIM_ERR_FAILED: No such instance: SAP_NWAdministrator.CreationClassName="SAP_NWAdministrator",Name="NWA_FOR_FirstLandScpSrvcName" [this message was repeated 60 times]
[EXCEPTION]
- applications_00.1.txt
#2.0 #2010 03 10 13:01:59:324#+0100#Error#/Applications/ExchangeInfrastructure#
#BC-XI#com.sap.xi.util.misc#005056911C9500260000000C00001234#7161750000000001##com.sap.aii.ibdir.server.cache.monitoring.CacheMonitor####221828512C1811DF8ADA005056911C95#221828512c1811df8ada005056911c95#221828512c1811df8ada005056911c95#0#Timeout Service Synchronous Queue Processor#Java##
No SLD elements of type SAP_XIAdapterFramework found
Thrown:
com.sap.aii.ib.bom.landscape.SLDElementNotFoundException: No SLD elements of type SAP_XIAdapterFramework found
Thacks

Hi,
It follows without working.
The connections with the SLD are correct
SLD Connection Test
Properties of RFC destination SAPSLDAPI
RFC host: %%RFCSERVER%%
Program ID: SAPSLDAPI_PID
Gateway host:
Gateway service:
Testing RFC connection to the SLD java client...
RFC ping was successful
SLD destination settings:
Alias: SAP_CONFIG
Host name: SvFig2056
Port number: 08100
User: SLD_CL_PID
Testing HTTP connection to the SLD server...
SLD ping was successful
Connection to SLD works correctly
http://svfig2056:8100/sap/xi/engine?type=entry
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header />
- <SOAP:Body>
- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Client</faultcode>
<faultstring>Empty HTTP request received</faultstring>
<faultactor>http://sap.com/xi/XI/Message/30</faultactor>
- <detail>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Empty HTTP query received; message processing not possible</SAP:Stack>
</SAP:Error>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>

Facing Problem in SLD(getting 500 INTERNAL SERVER ERROR IN PORTAL)

Dear All,
we had ESS application just few days back it went to Go live , very frequently we are facing the issue
Regards JCO 's , we are getting "500 Internal Server Error" in production Portal
After getting the error ,the " Maintained JCO's" and "Created JCO'S " are both are disabled
uder contenten administraton->webdynpro.
But the SDL is in active , we can able to open SLD url every thing is also fine
Technical system and every thing coming fine
we checked SLD User also in SLD User Administration , the SLD user is also there it is not unlocked
The problem is : if the problem is happend after restarting the server again it is coming properly
Again after some time it is getting same error ,whith out doing any thing also some times the problem is resolving automatically
we are not getting Root cause of this behaviour
In our client side SLD is centralized ,they are not maintain locally
If the SLD is Proble , the error has to come in Quality and Production also why bcz it is centralized
But Some times 500 ERROR IN Prodution and some times in Quality.
And some times the Portal is very slowly opening especially ESS application ,after restart happening it is some better
again it is getting down after some time
If it is NETWORK Iuuse or any firewall ect...in which way we can can with them and where
Guru's share your knowledge it's a very critical for me what are he possible ways...
Regards,
Giri

Here I am giving the LOG details which is available in SLD (J2EE) server
#2.0 #2012 03 03 14:24:57:513#+0530#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
#BC-XI-CON-AFW#com.sap.aii.af.lib#005056BB552201A70000000000000DF0#151402750000001894##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#Guest#0##1014F5C2650011E1B811005056BB5522#1014f5c2650011e1b811005056bb5522#1014f5c2650011e1b811005056bb5522#0#Application [17]#Plain##
SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
#2.0 #2012 03 03 14:26:06:739#+0530#Error#com.sap.nw.lm.aci.engine.base.sld.connection.AccSldConnector#
#BC-AC-7XX#sap.com/tc~lm~aci~engine~baselib~05#005056BB552201AB0000000100000DF0#151402750000008310#sap.com/tc~lm~aci~monitor~app#com.sap.nw.lm.aci.engine.base.sld.connection.AccSldConnector.getSldComputerSystemsForMonitoring(String)#Administrator#0#SAP J2EE Engine JTA Transaction : [9638fffffffe00fffffff85]#1014F5C2650011E1B811005056BB5522#1014f5c2650011e1b811005056bb5522#1014f5c2650011e1b811005056bb5522#0#Thread[Managed_Application_Thread_29,5,Managed_Application_Thread]#Java##
Unable to obtain Computer Systems, associated to NW Admin NWA_FOR_FirstLandScpSrvcName, from SLD. CIM_ERR_FAILED: No such instance: SAP_NWAdministrator.CreationClassName="SAP_NWAdministrator",Name="NWA_FOR_FirstLandScpSrvcName" [this message was repeated 9 times]
[EXCEPTION]
{0}#1#com.sap.sld.api.wbem.exception.CIMException: CIM_ERR_FAILED: No such instance: SAP_NWAdministrator.CreationClassName="SAP_NWAdministrator",Name="NWA_FOR_FirstLandScpSrvcName"
     at com.sap.sld.api.wbem.client.WBEMRequestSender.convertErrorResponse(WBEMRequestSender.java:127)
     at com.sap.sld.api.wbem.client.WBEMRequestSender.convertErrorResponse(WBEMRequestSender.java:48)
     at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:272)
     at com.sap.sld.api.wbem.client.WBEMRemoteClient.sendAndCast(WBEMRemoteClient.java:936)
     at com.sap.sld.api.wbem.client.WBEMRemoteClient.associatorNamesImpl(WBEMRemoteClient.java:507)
     at com.sap.sld.api.wbem.client.WBEMAbstractClient.associatorNames(WBEMAbstractClient.java:544)
     at com.sap.nw.lm.aci.engine.base.sld.connection.AccSldConnector.getSldComputerSystemsForMonitoring(AccSldConnector.java:3731)
     at com.sap.nw.lm.aci.monitor.fetch.util.MonitoringSldAdapter.getAllHostnames(MonitoringSldAdapter.java:277)
     at com.sap.nw.lm.aci.monitor.fetch.manager.PrefetchPackageUtil.repackageCs(PrefetchPackageUtil.java:71)
     at com.sap.nw.lm.aci.monitor.fetch.manager.PrefetchPackageUtil.repackageAll(PrefetchPackageUtil.java:58)
     at com.sap.nw.lm.aci.monitor.fetch.manager.FetchManager.repackageIfRequired(FetchManager.java:1046)
     at com.sap.nw.lm.aci.monitor.fetch.manager.FetchManager.run(FetchManager.java:435)
     at com.sap.nw.lm.aci.monitor.fetch.job.FetchJobBean.onJob(FetchJobBean.java:67)
     at com.sap.engine.services.scheduler.runtime.mdb.MDBJobDelegateImpl$2.run(MDBJobDelegateImpl.java:233)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAs(Subject.java:396)
     at com.sap.engine.services.scheduler.runtime.mdb.MDBJobDelegateImpl.onMessage(MDBJobDelegateImpl.java:267)
     at com.sap.scheduler.runtime.mdb.MDBJobImplementation.onMessage(MDBJobImplementation.java:60)
     at sun.reflect.GeneratedMethodAccessor284.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:110)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
     at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:77)
     at $Proxy1058.onMessage(Unknown Source)
     at com.sap.jms.resourceadapter.RaServerSession.internalOnMessage(RaServerSession.java:188)
     at com.sap.jms.resourceadapter.RaServerSession.onMessage(RaServerSession.java:330)
     at com.sap.jms.client.session.JMSSession.deliverMessage(JMSSession.java:805)
     at com.sap.jms.client.session.JMSSession.run(JMSSession.java:709)
     at com.sap.jms.resourceadapter.RaServerSession.run(RaServerSession.java:379)
     at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:420)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
#2.0 #2012 03 03 14:26:57:526#+0530#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
#BC-XI-CON-AFW#com.sap.aii.af.lib#005056BB552201B00000000000000DF0#151402750000001894##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#Guest#0##1014F5C2650011E1B811005056BB5522#1014f5c2650011e1b811005056bb5522#1014f5c2650011e1b811005056bb5522#0#Application [6]#Plain##
SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
#2.0 #2012 03 03 14:28:57:522#+0530#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
#BC-XI-CON-AFW#com.sap.aii.af.lib#005056BB552201B70000000000000DF0#151402750000001894##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#Guest#0##1014F5C2650011E1B811005056BB5522#1014f5c2650011e1b811005056bb5522#1014f5c2650011e1b811005056bb5522#0#Application [5]#Plain##
SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
#2.0 #2012 03 03 14:30:57:519#+0530#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
#BC-XI-CON-AFW#com.sap.aii.af.lib#005056BB552201BE0000000000000DF0#151402750000001894##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#Guest#0##1014F5C2650011E1B811005056BB5522#1014f5c2650011e1b811005056bb5522#1014f5c2650011e1b811005056bb5522#0#Application [20]#Plain##
SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
Edited by: giriep on Mar 3, 2012 11:38 AM

PI 7.11 sp6 system copy Exchange Profile error code: 399

Experts,
We have a PI 7.1 (EHP1, sp6) PI system based on AIX 6.1 OS and Oracle 11g.
I recently did the standard PI system copy from a prod source (PIP) to a training target (PIT).
I used the most recenty PI system copy guide that is specific for PI 7.1 EHP1
I did not run into any major problems doing the steps of the copy itself.
I did the usual "post" steps, documented in the guide that really are done on any NW system.
Then I got into the specific "PI" post steps and that's where I now have a problem.
I followed all the steps, fixing my RFCs, JCos, Destinations, cleaning up SLD, SLDAPICUST, creating new business systems...etc.
My big problem is with the exchange profile. Yes, it's easy to change all the SIDs and hostnames using the search tool for all the parameters in the exchange profile, but the one I COULD NOT CHANGE was the "ABAP Connection". In there right after the copy was the hostname of the prod system, the client, and the user PILDUSER. I attempted to put the hostname of my target (PIT) system, but I would get the error:
com.sap.rprof.dbprofiles.DBException: RFC call returned an error code: 399
I'm certain the user is NOT locked and the password is correct for PILDUSER. It'll give me a different error if I put the wrong password in, so I know it's hitting my system.
Worse yet, If I left the hostname in there that was set to "prod", then when I changed all the other values in the "parameters" section of the XI profile, then it actually changed my PROD system!!
If I keep the ABAP connection to PIT, then the entire exchange profile disappears for PIT.
I see these errors in the default trace and application log:
Caused by: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND:
No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",
Name="PIT.SystemHome.<traininghostname>"
Caused by: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND: No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="PIT.SystemHome.<traininghostname>"
at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120)
#2.#2011 11 03 13:49:47:008#0-500#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
#BC-XI-CON-AFW#com.sap.aii.af.lib#7E3832DEA80F002B00000000008700C6#4804850000001902##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#J2EE_GUEST#0##0AFD01D4064C11E1CB5E7E3832DEA80F#0afd01d4064c11e1cb5e7e3832dea80f#0afd01d4064c11e1cb5e7e3832dea80f#0#Application [24]#Plain##
SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
#2.#2011 11 03 14:51:18:096#0-500#Error#com.sap.esi.esp.service.server.ESPServiceInterfaceAbstract#
#BC-ESI-WS-JAV#tcesiespsrv#7E3832DEA80F001100000000009A004C#4804850000001385##com.sap.esi.esp.service.server.ESPServiceInterfaceAbstract####109F6812065511E1BF9C7E3832DEA80F#109f6812065511e1bf9c7e3832dea80f#109f6812065511e1bf9c7e3832dea80f#0#Service Runner [tcesiespsrv]#Plain##
+There is problem reading the hostname from the ClusterManager. This could lead to improper wsdl links.#
SLDCHECK shows this:
Function call returned exception code 3
Access to the XI Profile is currently disrupted.
I can't be the first person to run into this.
SO strange that I can actually plug in either my dev/QA or PROD hostname in the "ABAP connection" box and it WILL ACCEPT IT...but then, it registered my training system as a "non central adapter engine". I don't want that.
Any ideas?
Another issue is that the SLD PI information from the PIT system is missing the "Integration Directory". It has the other 5 entries...Adapter Engine, Domain, Integration Repository, Integration Server, RWB.
Thanks for reading this,
NICK

Here is the error I get when I try to change the "abap connection" to the correct hostname:
RFC call returned an error code: 399
Stack Trace class com.sap.rprof.dbprofiles.DBException: <pre>at com.sap.rprof.dbprofiles.DBProfiles.checkReturn(DBProfiles.java:184) at com.sap.rprof.dbprofiles.DBProfiles.getProfile(DBProfiles.java:105) at com.sap.rprof.dbprofiles.RemoteProfile.readRemoteProfileFromMedia(RemoteProfile.java:1378) at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactory(RemoteProfile.java:204) at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfile(RemoteProfile.java:154) at com.sap.rprof.dbprofiles.ExchangeProfile.getExchangeProfile(ExchangeProfile.java:46) at com.sap.rprof.remoteProfile.webui.ProfileWebTree.<init>(ProfileWebTree.java:24) at com.sap.rprof.remoteProfile.webui.Edit.getWebTree(Edit.java:322) at JEE_jsp_treeexprof_4804850_1319481176000_1319565151782._jspService(JEE_jsp_treeexprof_4804850_1319481176000_1319565151782.java:59) at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:436) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:493) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388) at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247) at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327) </pre>

JCO - Get meta data - Grey status in JCO connections tab

Hi all,
I read many post on this topics within this forum but I didn't succeed to get meta data required and to set correctly my connection.
Let's start quickly to give you my conf
In the j2ee admin
-> Services > SLD Data Supplier > CIM Client Generation Settings
I set fields with : SLD7000 / 50000 and my logon info
Save and test -> result is ok !
In my web dynpro application, I am able to get correct BAPI from BCE system using my logon info. And I map my view to display data from the corresponding BAPI called.
So at this time, in my IDE, the connection to the SAP Backend system SAP works because I can get the list of BAPIs from the BCE SAP Backend System as well.
Build and deploy my application.
Now, let's go to webdynpro welcome page on my j2ee server : http://<host>:<port>/webdynpro/welcome
-> content administration
-> I select from the left tree browser my application, and open the "JCO Connections" Tab. I can see my connections previously I set in my webdynpro application. But I CAN'T use the button "Create" to configure new JCO connection. ??
Last thing:
in the BCE backend system
transaction : RZ70
I have, host = sldmain and service = sapgw47
Also, in the list of data collection programs, everything is checked as active except the program "_SLD_RFC"
I don't know if it is important....?
Finally, I give you from the exception I got in my browser only lines "Caused by"....
Caused by: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create J2EE cluster node in SLD for 'J2E.SystemHome.localhost': com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND: No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="J2E.SystemHome.localhost"
Thanks a lot for your support and help,
Best regards,
Emmanuel.

Hi Emmanuel
You said
" I select from the left tree browser my application, and open the "JCO Connections" Tab. I can see my connections previously I set in my webdynpro application. But I CAN'T use the button "Create" to configure new JCO connection. ??"
What is their status ? Is it green on red? Usually create is greyed out if it is green. What about Edit?
Try creating a new Web Dynpro component with another destination name ,deploy and then check the Content administrator if these new destinations have Create enabled
After running RZ70 did you check the Technical System in SLD administration to see if the technical details have been propogated ?
Regards
Pran

WDRuntimeException: Failed to create J2EE cluster node in SLD

Hello,
I am getting the below error, but to my knowledge I have everything set up properly. Let me briefly outline the logistics (I am running everything LOCALLY (will move to remote later)):
WAS 6.4 SP12
Set up JCo and tests fine
Set up Visual Administrator / SLD Data Supplier / HTTP and CIM configured and seem to test fine
Created SLD and it tests OK
Created Technical Landscape
I have noticed that in SP12, in the SLD config I actually have a NEW category called "System Landscape" above my "Technical Landscape" link. I have not seen this option in previous versions SP9 or SP11. Is it mandatory to configure this?
Also, I created a model for Adaptive RFC and found the function I needed successfully.
Anyway, here is the error when trying to deploy...
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error while obtaining JCO connection.
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create J2EE cluster node in SLD for 'J2E.SystemHome.bc347792': com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND: No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="J2E.SystemHome.bc347792"
Any help will be appreciated!

I figured it out for those that may have a similar problem.
Although I had created and tested my JCo's properly and they were working fine, somehow, and I still don't know why, they went RED in the JCo Maintainence screen.
I had to "create" again and it works fine now.

NWDI/DI configuration

Hi!
Can anybody here say, where is full step by step configuration guide for NWDI or CBS/DTR/CMS/...?
We have DTR/CBS etc. on DEV server. But some configuration issues were missed:
1. CMS Landscape configurator -> Domain Data -> Update CMS:
SLD (URL http://serverxxx:50000) server exception: CIM_ERR_FAILED: No such instance: sld/active:SAP_DependencyContext.Name="BuildTime",Type="Development"
2. http://serverxxx:50000/dtr
<DAV:error>
<DAV:access-denied/>
</DAV:error>
Any answer will be appreciate.
Regards,
Maxim

Hi Sandeep!
Thanks for the manual! I re-configured SLD in accordance with it. And problem with access to DTR solved, but after server was re-started, I get this message when try to get "Administration" link in SLD:
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
at com.sap.sld.wd.main.wdp.InternalMainInterfaceView.wdFirePlugToOldUI(InternalMainInterfaceView.java:154)
at com.sap.sld.wd.main.Head.onActionAdministration(Head.java:277)
at com.sap.sld.wd.main.wdp.InternalHead.wdInvokeEventHandler(InternalHead.java:227)
Do you have any idea?
P.S. In Visual Admin "Send Result - Success" and "CIM Client Test - Passed"
Thanks in advance!
Edited by: Maxim Pak on Oct 17, 2008 1:29 PM
Edited by: Maxim Pak on Oct 17, 2008 1:31 PM

Netweaver Rapid Installer

Hi all,
i have installed the Portal using the netweaver rapid installer and everything went fine, after that i launched the sapinst one more time and this time chose the configuration part the Self Service packages without PSS
however the installation is stops while it is still taking the parameters with the following error
Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath C:/usr/sap/XSS/JC01/j2ee/cluster/server0/apps/sap.com/tclmctcutilbasic_ear/servlet_jsp/ctc/root/WEB-INF/classes com.sap.ctc.util.ConfigMainExt com.sap.ctc.util.Verifying;MAINTAIN_JCO_DESTINATION;NAME=SAP_R3_Financials,CLIENT=,MSGSERVERNAME=,SYSTEMNAME=,USER=,PASSWORD=,LOGONGROUP=PUBLIC,USERTYPE=SSO,SLDHOST=netweaver,SLDPORT=50100,SLDUSER=SLDDSUSER,SLDPASSWORD=des19(80|24|150|247|101|200|181|119|);CHECK netweaver:50100 Administrator XXXXXX" finished with return code 0. Output:
TYPE=A STATE= INFO_SHORT=com.sap.lcr.api.cimclient.LcrException: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND: No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="XSS.SystemHome.netweaver"
 at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120)
 at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.getIResult(SimpleResponseAnalyser.java:53)
 at com.sap.lcr.api.cimclient.CIMOMClient.sendImpl(CIMOMClient.java:218)
 at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:146)
 at com.sap.lcr.api.cimclient.CIMOMClient.getInstance(CIMOMClient.java:572)
 at com.sap.lcr.api.cimclient.CIMClient.getInstance(CIMClient.java:1250)
 at com.sap.lcr.api.sapmodel.SAP_J2EEEngineClusterAccessor.getInstance(SAP_J2EEEngineClusterAccessor.java:92)
 at com.sap.lcr.api.sapmodel.SAP_J2EEEngineClusterAccessor.getInstance(SAP_J2EEEngineClusterAccessor.java:78)
 at com.sap.ctc.util.Verifying.maintainJcoDestinationCheck(Verifying.java:1271)
 at com.sap.ctc.util.Verifying.performCheck(Verifying.java:275)
 at com.sap.ctc.util.ConfigServlet.doGet(ConfigServlet.java:70)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 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)
// => Error while obtaining JCO connection.
 + com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:149)
 + com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:157)
 + com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.getJCOClientConnection(WDSystemLandscape.java:41)
 + com.sap.ctc.util.Verifying.maintainJcoDestinationCheck(Verifying.java:1233)
 + com.sap.ctc.util.Verifying.performCheck(Verifying.java:275)
 + com.sap.ctc.util.ConfigServlet.doGet(ConfigServlet.java:70)
 + javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 + javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 + com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 + com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 + com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 + com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 + com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 + com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 + com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 + com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 + com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 + com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 + com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 + java.security.AccessController.doPrivileged(Native Method)
 + com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 + com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
 + Checking SLD content ...
 + SLD ping to http://netweaver:50100 OK.
 + Cluster Name:XSS.SystemHome.netweaver
is there something that should be configured before running the configuration ?
I also couldnt find any installation guides so could some please share his knowledge.

Hi,
You should contact SAP to get the software. Netweaver Rapid Installer is optimized to run on 2 Hardware configurations (SUN for Unix and HP for Win-based).
(for Sun have a look at http://www.sun.com/third-party/global/sap/solutions/rapidinstaller.html )
Regards,
Igor.

SLD Configuration Error

Dear All,
I have configured SLD and the SLD Server's SID is KSL and the SLD Client SID is KDS. when the client passes the data to SLD Server the following error occurs.
What could be the reason
Log Record Details
#1121 04/05/2007 19:09:31.781 [Thread-43] ERROR com.sap.lcr.sagent.specificbuilder.AbstractBuilder: Unexpected error processing supplied data.
Thrown:
com.sap.sld.api.wbem.exception.CIMException: CIM_ERR_NOT_FOUND: No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="KDS.SystemHome.kaar-server3"
at com.sap.lcr.objmgr.requests.WBEMGetInstance.execute(WBEMGetInstance.java:79)
at com.sap.lcr.objmgr.requests.WBEM_ReadRequest.execute(WBEM_ReadRequest.java:50)
at com.sap.lcr.objmgr.core.ObjectManager.executeImpl(ObjectManager.java:1294)
at com.sap.lcr.objmgr.core.ObjectManager.execute(ObjectManager.java:1191)
at com.sap.lcr.objmgr.core.ObjectManager.getInstance(ObjectManager.java:838)
at com.sap.lcr.cimsrv.WBEMLocalClient.getInstanceImpl(WBEMLocalClient.java:122)
at com.sap.sld.api.wbem.client.WBEMClient.getInstance(WBEMClient.java:385)
at com.sap.sld.api.wbem.client.WBEMClientUtil.getInstanceComplete(WBEMClientUtil.java:476)
at com.sap.lcr.sagent.specificbuilder.SupplierUtil.createCollection(SupplierUtil.java:528)
at com.sap.lcr.sagent.specificbuilder.AbstractBuilder.sync(AbstractBuilder.java:510)
at com.sap.lcr.sagent.specificbuilder.AbstractBuilder.work(AbstractBuilder.java:166)
at com.sap.lcr.sagent.BuilderDirector.performWork(BuilderDirector.java:885)
at com.sap.lcr.sagent.BuilderDirector.performWork(BuilderDirector.java:586)
at com.sap.lcr.sagent.BuilderDirector.run(BuilderDirector.java:441)
regards,
Anand

Hi,
Check all these in VA.
Go to Visual Composer
1)Make new Connecion
a)User name->
b)Host ->
c)Port->50004
Goto cluster ->got to server->services->sld Data supplier.
Set RFC Settings
a)Gateway Host ->ip of ep
b)GateWay service/port->sapgw00/3300
CIM client generation settings
Host->ip address of ep
Port ->50000
user->
Set Http Settings
Host->ip of ep
port->50000
user->j2ee_admin
Do these steps
It might helps you.
Thanks,
Lohi.

Need to send object instances over the network

I found no other way to implement a switch case to cast objects on both sides to solve my problem.
Basically I need to send objects over a network protocol based on XML, the object is sent inside XML
converted in base64, overall encoding of XML is utf-8.
Let's suppose in my network there are 2 peers connected via socket.
I have multiple instances of different types on both peers but I want to keep these instances
synchronized. If something changes on side A, side B must receive that instance and replace
it in the correct place (just one way, from A to B).
When I receive such instance on B I want to cast it to it's proper instance
of it's proper type and I am scratching my head on how could I implement this without some
sort of unique ID table and switch case.
If I had 1 instance per type could it be done easily?
But I need to keep in synch many instances per type.
Is there any dynamic casting that I can trigger based on some type/instanceID information
I could send along the object?

I found no other way to implement a switch case to cast objects on both sides to solve my problem.
Basically I need to send objects over a network protocol based on XML, the object is sent inside XML
converted in base64, overall encoding of XML is utf-8.
Let's suppose in my network there are 2 peers connected via socket.
I have multiple instances of different types on both peers but I want to keep these instances
synchronized. If something changes on side A, side B must receive that instance and replace
it in the correct place (just one way, from A to B).
When I receive such instance on B I want to cast it to it's proper instance
of it's proper type and I am scratching my head on how could I implement this without some
sort of unique ID table and switch case.
If I had 1 instance per type could it be done easily?
But I need to keep in synch many instances per type.
Is there any dynamic casting that I can trigger based on some type/instanceID information
I could send along the object?

Fresh install of 11.1 and "sqlplus user@instance/password" does not work

new server, windows server 2008, fresh install of 11.1.0.7 with local instance.
can connect to the instance using "sqlplus user/password" since ORACLE_SID is set,
can connect to a 9.2 remote instance using "sqlplus user@remoteinstance/password".
can't connect using "sqlplus user@localinstance/password".
<command>
l:path>set oracle_sid=localinstance
l:path>sqlplus username/password
SQL*Plus: Release 11.1.0.7.0 - Production on Mon Nov 8 13:11:02 2010
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Release 11.1.0.7.0 - Production
SQL> exit
Disconnected from Oracle Database 11g Release 11.1.0.7.0 - Production
l:\path>sqlplus username@localinstance/password
SQL*Plus: Release 11.1.0.7.0 - Production on Mon Nov 8 13:11:21 2010
Copyright (c) 1982, 2008, Oracle. All rights reserved.
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
l:\path>
l:\path>sqlplus username@remoteinstance/password
SQL*Plus: Release 11.1.0.7.0 - Production on Mon Nov 8 13:11:45 2010
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
SQL> exit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
l:\path>
</command>
what am i doing wrong?
many thanks in advance,
stephen.

=================================
A couple of important points.
First, the listener is a server side only process. It's entire purpose in life is to receive requests for connections to databases and set up those connections. Once the connection is established, the listener is out of the picture. It creates the connection. It doesn't sustain the connection. One listener, with the default name of LISTENER, running from one oracle home, listening on a single port, will serve multiple database instances of multiple versions running from multiple homes. It is an unnecessary complexity to try to have multiple listeners or to name the listener as if it belongs to a particular database. That would be like the telephone company building a separate switchboard for each customer.
Additional notes on the listener: One listener is capable of listening on multiple ports. But please notice that it is the listener using these ports, not the database instance. You can't bind a specific listener port to a specific db instance. Similarly, one listener is capable of listnening on multiple IP addresses (in the case of a server with multiple NICs) But just like the port, you can't bind a specific ip address to a specific db instance.
Second, the tnsnames.ora file is a client side issue. It's purpose is for address resolution - the tns equivalent of the 'hosts' file further down the network stack. The only reason it exists on a host machine is because that machine can also run client processes.
Assume you have the following in your tnsnames.ora:
larry =
(DESCRIPTION =
 (ADDRESS_LIST =
 (ADDRESS = (PROTOCOL = TCP)(HOST = myhost)(PORT = 1521))
 (CONNECT_DATA =
 (SERVICE_NAME = curley)
)Now, when you issue a connect, say like this:
$> sqlplus scott/tiger@larrytns will look in your tnsnames.ora for an entry called 'larry'. Next, tns sends a request to (PORT = 1521) on (HOST = myhost) using (PROTOCOL = TCP), asking for a connection to (SERVICE_NAME = curley).
Where is (HOST = myhost) on the network? When the request gets passed from tns to the next layer in the network stack, the name 'myhost' will get resolved to an IP address, either via a local 'hosts' file, via DNS, or possibly other less used mechanisms. You can also hard-code the ip address (HOST = 123.456.789.101) in the tnsnames.ora.
Next, the request arrives at port 1521 on myhost. Hopefully, there is a listener on myhost configured to listen on port 1521, and that listener knows about SERVICE_NAME = curley. If so, you'll be connected.
What can go wrong?
First, there may not be an entry for 'larry' in your tnsnames. In that case you get "ORA-12154: TNS:could not resolve the connect identifier specified" No need to go looking for a problem on the host, with the listener, etc. If you can't place a telephone call because you don't know the number (can't find your telephone directory (tnsnames.ora) or can't find the party you are looking for listed in it (no entry for larry)) you don't look for problems at the telephone switchboard.
Maybe the entry for larry was found, but myhost couldn't be resolved to an IP address (say there was no entry for myhost in the local hosts file). This will result in "ORA-12545: Connect failed because target host or object does not exist"
Maybe there was an entry for myserver in the local hosts file, but it specified a bad IP address. This will result in "ORA-12545: Connect failed because target host or object does not exist"
Maybe the IP was good, but there is no listener running: "ORA-12541: TNS:no listener"
Maybe the IP was good, there is a listener at myhost, but it is listening on a different port. "ORA-12560: TNS:protocol adapter error"
Maybe the IP was good, there is a listener at myhost, it is listening on the specified port, but doesn't know about SERVICE_NAME = curley. "ORA-12514: TNS:listener does not currently know of service requested in connect descriptor"
Third: If the client is on the same machine as the db instance, it is possible to connect without referencing tnsnames and without going through the listener.
Now, when you issue a connect, say like this:
$> sqlplus scott/tigertns will attempt to establish an IPC connection to the db instance. How does it know the name of the instance? It uses the current value of the enviornment variable ORACLE_SID. So...
$> export ORACLE_SID=fred
$> sqlplus scott/tigerIt will attempt to connect to the instance known as "fred". If there is no such instance, it will, of course, fail. Also, if there is no value set for ORACLE_SID, the connect will fail.
check executing instances to get the SID
[oracle@vmlnx01 ~]$ ps -ef|grep pmon|grep -v grep
oracle 4236 1 0 10:30 ? 00:00:00 ora_pmon_vlnxora1set ORACLE_SID appropriately, and connect
[oracle@vmlnx01 ~]$ export ORACLE_SID='vlnxora1
[oracle@vmlnx01 ~]$ sqlplus scott/tiger
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 22 10:42:37 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing optionsNow set ORACLE_SID to a bogus value, and try to connect
SQL> exit
[oracle@vmlnx01 ~]$ export ORACLE_SID=FUBAR
[oracle@vmlnx01 ~]$ sqlplus scott/tiger
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 22 10:42:57 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
Enter user-name: Now set ORACLE_SID to null, and try to connect
[oracle@vmlnx01 ~]$ export ORACLE_SID=
[oracle@vmlnx01 ~]$ sqlplus /scott/tiger
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 22 10:43:24 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
ERROR:
ORA-12162: TNS:net service name is incorrectly specifiedOk, that is how we get from the client connection request to the listener. What about the listener's part of all this?
The listener is very simple. It's job is to listen for connection requests and make the connection (server process) between the client and the database instance. Once that connection is made, the listener is out of the picture. If you were to kill the listener, all existing connections would continue. The listener is configured with the listener.ora file, but if that file doesn't exist, the listener is quite capable of starting up with all default values. One common mistake with the listner configuration is to specify "HOST=localhost" or "HOST=127.0.01". This is a NONROUTABLE ip address. LOCALHOST and ip address 127.0.0.1 always mean "this machine on which I am sitting". So, all computers are known as "localhost" or "127.0.0.1". If you specify this address, the listener will only be capable of receiving requests from the machine on which it is running. If you specified that address in your tnsnames file - on a remote client machine - the request would be routed to the machine on which the requesting client resides. Probably not what you want.
=====================================

Create a test instance

I installed the new oracle 10g home, before upgrade the main database from 9i to 10g, i want to create a testing instance just to test if i can start sqlplus from 10g home. What's the procedure to create such instance?
Thanks!

If you want to create a regular instance go ahead and run dbca or run your scripts.
Regards

Scalability of a single instance of Sun One 7

Upto how many concurrent users can a single instance of Sun One 7 scale (let's say on E10K with six CPUs & 6-8 gig memory), considering that a single JVM runs everything (http server, web & ejb containers, messaging server etc) ? Are there any numbers available ? Is there an option to have multiple JVMs within a single app server instance (like multiple KJS in iPlanet for scalability) ? If not, is clustering(in enterprise edition) the only option to achieve the equivalent of multiple KJS ?

Our performance engineers can comment on the core of your question, but here are some answers to other aspects of your post:
- The Message Broker always runs out of process. By default, each app server instance starts/stops its own broker process. After creating an app server instance, you can disable the auto start/stop of the broker and map your JMS resources to a broker that could be shared by multiple app server instances.
- In AS 7.0 Platform Edition and Standard Edition, there is one JVM process per app server instance. You can configure multiple app server instances to house the same apps and resources, but you will have to keep these configs in sync on your own and you will need to provide your own front end load balancer that routes traffic across these instances.
In the Enterprise Edition, configuration of cloned instances and built in load balancing across such instances will be available in the product.
- Keep in mind that the built-in HTTP server is a highly refined and efficient subsystem. You might be thinking that its presence incurs a lot of overheard when in fact it is very lean.
We'll have our perf engineers comment on the scalability characteristics of app server 7.
Thanks,
Chris

Terminate CAL instance error - AWS credentials

Hi there,
I'm on a slightly misleading 'free' Fiori course via openSAP.
Once I realised 'free' meant that I may be charged hundreds of dollars by AWS I canceled/closed my AWS account.
Unfortunately I can't seem to now delete my CAL instance because it's trying to verify my credentials with my non-existent AWS account
Not quite sure how to get me out of this? Is there anyone that can help?
Thanks in advance,
Rob

Hi Rob,
The “undefined” instance stayed in SAP CAL although no VMs left in AWS after the terminate operation. The SAP CAL Team is working on a solution to clean-up such instances.
Apologies for the inconvenience,
Stanimir

CIM_ERR_FAILED: No such instance: SAP_XIAdapterFramework.CreationClassName=

Similar Messages

Maybe you are looking for