MDM 7.1 CLIX error
Hi all,
I am using a batch file with CLIX to automate repository unload/archive and to stop an MDM 7.1 server.
Here is an excerpt of the batch code:
Echo.Stopping MDM Server...
Echo ********Stop MDM Server ********
CLIX mdsStop %MDMSERVER% %DBLOGIN%:%DBPASS%
where %MDMSERVER% is the server address; %DBLOGIN% is the Administrator User Name of the MDM server, and %DBPASS% is the password for the Administrator account.
However, when I execute this batch, it gives this error:
Error: 0xffab4010, The command issued is no longer supported
when it comes to the CLIX mdsStop line.
I have already looked in the MDM 7.1 Console Reference Guide, which explicitly shows that the statement IS CLIX mdsStop.
I have used this CLIX command in the past when I created a batch for an MDM 5.5 server, and it worked just fine there.
Now I am lost as to why this same command is not working in 7.1
All help is greatly appreciated.
Thanks,
Bryce
The unsupported command problem has been solved, thank you Simon. However, now when I try to use the command icHalt, I get another error.
Stop of MDD Failed with error: 2147549185
Stop of -N Failed with error: 2147549185
Error: 0x80010001, Not found
According to the CLIX 7.1 command help, the command should be :
CLIX icHalt MdsHost UserId Password instance1 [-T] [-N]
The error is saying that stopping the specified instance (MDD) failed. However, to be sure that the DBMS instance is MDD, I used the mdsStatus command, and this is what it returned:
RepositName DBMSInstance DBT Port# RepType Status
GDS MDD O Unknown Needs Login
So I am sure that the instance is correct. I've been searching SDN and google for possible causes for both error: 2147549185 AND Error: 0x80010001, Not found but haven't found anything. If anyone is familiar with either of these two errors, or could help solve my problem with DBMS instance, I would be very grateful.
Thanks again,
Bryce
Edited by: bryceflorek on Aug 27, 2009 6:13 PM
Similar Messages
-
Hi All,
I am trying to make MDM CLIX command works but I still have the same error : Error: 0x8002000e, File failed a crc check
And I am not completely sure if my syntax is correct or not
NMHi,
"I am trying to make MDM CLIX command works but I still have the same error : Error: 0x8002000e, File failed a crc check
And I am not completely sure if my syntax is correct or not"
I am not having that much idea but generally "File failed a CRC check" error comes when the versions are not matching.
Like your MDM Server and MDM Clix are of the same Version like MDMCLIXInstall_Ver5.5.61.48.exe and MDMInstall_ver5.5.61.48.exe
I think the versions of MDM CLIX and MDM guis are not same.Kindly check.If problem persists there may be syntax error
Rgds
Ankit -
MDM 71 - mdm console and clix - unable to connect to database server
Hi,
environment, MDM 7.1, AIX 6, Oracle 10.2.0.4 (installed as part of a standalone java AS)
i've an issue. I have installed MDM 71 via sapinst, before that I installed a standalone java application server. During the installation, i gave the 'oracle client', 'oracle home' and 'oracle sqlplus utility' to be those of the oracle database installed for the java AS.
After sapinst completed I tested my connection to the database via
tnsping <SID> = OK
sqlplus system/passwd@<SID> = OK
When i start up the mdm console (7.1.02.90) i can mount the MDM server, BUT when I try to configure the database settings i get
error 'unable to connect to database server'
I get the same error when i use clix dblist
Error: 0x84020004, Unable to connect with Database Server
Has anybody got any ideas.To see why the MDM is not able to connect to database, do the following:
% cd /usr/sap/<SID>/MDSxx/log
% ls -ltr
You will find last updated log file with name like MDS_LogXXUX101224X164953.csv
% tail -100 MDS_LogXXUX101224X164953.csv
You will see the reason for not being able to connect. If the reason is:
",MDSAdminServerXGetAvailableReps,Oracle_DBConnection.cpp,205,,,,server_user,server_global,,,
2011-09-23T06:10:48.933,6 ,24,"Service 'SID', Schema 'system', ERROR CODE=12154 ||| ORA-12154: TNS:could not resolve the connect identifier specified
OCI Attach, try again ...
Then edit the /oracle/SID/112_64/network/admin/tnsnames.ora with entry like following:
SID.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = SAP.WORLD)
(PROTOCOL = TCP)
(HOST = hostname)
(PORT = PORT_NO)
(CONNECT_DATA =
(SID = SID)
(GLOBAL_NAME = SID.WORLD)
then issue:
tnsping SID
If result is like
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP.WORLD) (PROTOCOL = TCP) (HOST = hostname) (PORT = PORT_NO))) (CONNECT_DATA = (SID = SID) (GLOBAL_NAME = SID.WORLD)))
OK (0 msec) -
Unable to start MDM Server using CLIX
I am able to Stop the MDM Server by issuing 'mdsStop' command from command line. But I'm unable to re-start the MDM Server by issuing the 'mdsStart' command from command line. Is anyone else using CLIX? If so, are you successful in starting the server from CLIX?
My command:
CLIX mdsStart SERVERNAME
I get no error messages and the command line prompt comes back like normal but the MDM Server is still not running.Klaus, the point is that the MDSSTOP command will work and the result of this command is that the MDM Server service on the hostmachine gets killed. I would assume that the MDSSTART command is supposed to startup the MDM Server service on the host machine, but it does not.
The MDMSTATUS command will work if the MDM server service is running. -
MDM 5.5 SP03 - Error while connecting EP to MDM server
Hello colleagues,
I've deployed the following content of MDM 55 SP03 delivery to portal:
a. com.sap.mdm.tech.mdm4j.sda
b. com.sap.mdm.tech.connector.sda
c. BPMDMTECHN00_0.sca
d. BPMDMAPPLI00_0.sca
Then I created MDM system in Portal, arranged mapping but I couldn't
connect to MDM server using Connection test.
The MDM server is ip and running, port number in Portal is correct,
versions of deployed JAVA API and MDM connector fit to MDM server, user
mapping is correct too.
I actually have no idea what is the problem.
Are there any authorization requirements while connecting from EP to MDM Server?
Thanks and regards,
Konstantin.Hi Nir,
Sorry for replying so late. I am following the steps given in the Business Package document.
1.I have created a system with system alias SAP_MDM_Repository_Customer(I want to connect to only customer repository) in a folder "Customer Repository".
2. I have created three groups MDM 5.5 SP3 Business Expert, MDM 5.5 SP3 MDM Admin, MDM 5.5 SP3 MD Expert
3. Then from the "Content provided by SAP" -> Specialist i am copying all the roles viz. Business Expert, Master Data Administrator, Master Data Expert. And then in the folder "Customer Repository" paste them as delta links.
4. Then in the user administration tab in the roles tab I am searching by group and adding the roles to these groups as below:
Group Role
MDM 5.5 SP3 Business Expert Business Expert
MDM 5.5 SP3 MDM Admin Master Data Administrator
MDM 5.5 SP3 MD Expert Master Data Expert
(Initially i have not adde eu_role but later i have added that also)
5. Then in the user mapping tab. I do the user mapping for the groups with the mdm repository users as below:
PortalUser Group Repository
user
mdmuser MDM 5.5 SP3 Business Expert User/pwd
mdmadmin MDM 5.5 SP3 MDM Admin Admin/pwd
mdmexpert MDM 5.5 SP3 MD Expert Expert/pwd
6. Then when i test the connection i get connection failed error.
7. When i add each roles in the "Everyone" group the connection test is successful but no data is displayed when i login with the portal user mdmuser no data is displayed.
Thats all. AFAIK i have covered every detail. Waiting for your reply.
Regards,
Jaydeep
Message was edited by: Jaydeep Kalmankar -
MDM Java Connector Config Error.
We deployed "com.sap.mdm.tech.connector.sda", "com.sap.mdm.tech.mdm4j.sda" using SDM. The deployment was successful. We wanted to set all the parameters like
UserName, Password,Server, Port, RepositoryLanguage as Key-Value pair in MDM Connector properties in Visual Admin from Server->Connection Container->Connectors -> MDM Factory -> Managed Connection Factory -> Poperties.
The intention was to use "spec.getAllConnectionProperties()" code to get the properties at runtime using following code given below.
Context ctx = new InitialContext();
IConnectionFactory conFactory = (IConnectionFactory)
ctx.lookup("deployedAdapters/MDM Factory/shareable/MDM Factory");
IConnectionSpec spec = conFactory.getConnectionSpec();
While setting these properties in Visual Admin, it threw an error.
java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 19149650:com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.mdm.connector.connection.MdmManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1210)
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.registerConnector(DeployAdmin.java:2015)
at com.sap.engine.services.connector.jca.deploy.ContainerImpl.prepareStart(ContainerImpl.java:1144)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.connector.jca.deploy.ContainerImpl.startApplication(ContainerImpl.java:1745)
at com.sap.engine.services.connector.jca15.gui.RuntimeControlsImpl.startApplication(RuntimeControlsImpl.java:169)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
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.NoSuchMethodException: com.sap.mdm.connector.connection.MdmManagedConnectionFactory.setUserName(java.lang.String)
at java.lang.Class.getMethod(Class.java:986)
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1190)
... 42 more
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:663)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.connector.jca.deploy.ContainerImpl.startApplication(ContainerImpl.java:1745)
at com.sap.engine.services.connector.jca15.gui.RuntimeControlsImpl.startApplication(RuntimeControlsImpl.java:169)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
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: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 19149650:com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.mdm.connector.connection.MdmManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1210)
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.registerConnector(DeployAdmin.java:2015)
at com.sap.engine.services.connector.jca.deploy.ContainerImpl.prepareStart(ContainerImpl.java:1144)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.connector.jca.deploy.ContainerImpl.startApplication(ContainerImpl.java:1745)
at com.sap.engine.services.connector.jca15.gui.RuntimeControlsImpl.startApplication(RuntimeControlsImpl.java:169)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
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.NoSuchMethodException: com.sap.mdm.connector.connection.MdmManagedConnectionFactory.setUserName(java.lang.String)
at java.lang.Class.getMethod(Class.java:986)
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1190)
... 42 more
at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:270)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:127)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
... 32 more
How do I solve this bug? We tried both in NW04 SP17 J2EE engine and NW04s SPS9 J2EE engine. It is throwing error in both. Any immediate help will highly be recognise.
Best Regards
KalyanHi Kalyan,
setting the properties in visual admin is not supported for the MDM connector. You always need to set the properties in your code:
spec.setPropertyValue("UserName", user);
spec.setPropertyValue("Password", password);
spec.setPropertyValue("Server", server);
spec.setPropertyValue("Port", String.valueOf(port));
spec.setPropertyValue("RepositoryLanguage", lang);
spec.setPropertyValue("CodeRegion", "English [US]");
// Get the Connection
connection = connectionFactory.getConnectionEx(spec);
// Retrieve Native inteface
INative nativeInterface = connection.retrieveNative();
// Get the CatalogData the physical connection
catalog = (CatalogData)
nativeInterface.getNative(CatalogData.class.getName());
Kind regards,
Andreas -
MDM managed system configuaration error
Hi,
While doing managed system configuration getting the error, below versions are using.
MDM 7.1 SP10 Import server and Solution manager 7.1 SP10.
Can anyone help me?.
Regards
ChandraDear ,
Haseeb,
I had the exact same problem with MDM managed system setup . I was on MDM 7.1 SP10.
1940337 - RCA template for Solution Manager 7.10 SP10
This note should resolve your problem. This note has the updated template for MDM.
It did for mine
Thanks
Amit -
MDM 5.5 SP02 Error during import of Customer Data
Hello,
I am a beginner in MDM 5.5.
I tried to import the customer data via the import manager. I got the error message:
<b>" E1KNA1M wasn't found in the source "</b>
What's wrong with this repository ? I used the DEBMDM06 for extraction out of an R/3 4.7. The XML-file includes this segment !
Can someone help me ?
Thanks in advance.
MichaelRonen,
Thanks for quick response.
Let me fill you in with the my environment info. I am using MDM SP 02 with SQL Server on Windows XP.
I am following the SAP NetWeaver MDM 5.5 SP02
Scenario Configuration Guide to import customer Data from R/3 to MDM repository via XI, idoc.
According to guide I was able to extract the Customer data from R/3, and using XI (and FTP) I was able to get the data file customer.dat (which is in XML format).
In console I tried to setup the client system as a you specified, but here is what I see in my MDM console
Name: MDC (R/3 4.6 DEBMDM05)
Code: MDC (R/3 4.6 DEBMDM05)
Client System: Import [ for this field it shows me Import, Export, Import/Export options only and not the inbound/outbound as you specified]. If I select option Import then only it will show this Client System while defining the Port.
For port definition it shows following fields
[Port]
Name : R3Import
Code : R3Import
Type : Inbound
Data Definition: [ dropdown options are Access, Excel, XML, Flat Text, XML Schema. Were you referring this field as the 'Format' field.]
XML Schema: I selected DEBMDM05 from dropdown.
Client System : MDC (R/3 4.6 DEBMDM05)
Map: [ dropdown does not have any values to select and I can not type in that field]
If you are still with me, what are the correct settings for Client system and port?
How those settings are being used in Import Manager?
On Connect to Source dialogue screen what should I select/enter for following fields?
Type : [options are Access, Excel, ODBC, Oracle, Port, SQL Server, XML, XML Schema]
Should I be using Client System and Port or XML/XML Schema????
Client System: MDC (R/3 4.6 DEBMDM05)
Port : [ Why this value 'R3Import' is grayed out??? ]
Please help.
Abhay -
MDM Database command execution error. A SQL statement failed to execute
Hi,
When we tried to execute an MDM Java query modify/create, we get the following dump.
Is this anything to do with the parameters that we pass or is it something to do with the database ?
We have checked the code and we do not find anything wrong with the code at all.
We are using Java API 5.5.63.73 and calling MDM API's using WebDynpro for Java.
I have noticed this issue has been raised here as well :
Database command execution error. (While mounting a repository)
com.sap.mdm.commands.CommandException:
com.sap.mdm.internal.protocol.manual.ServerException: Database command execution error. A SQL
statement failed to execute. The actual error may have been written to a log file. at
com.sap.mdm.data.commands.ModifyRecordCommand.execute(ModifyRecordCommand.java:163) at
Regards,
Subramanian V.
Edited by: Subramanian Venkateswaran on Dec 10, 2008 8:11 PMHi Subramanian ,
The error looks more like a problem with the data base or MDM system rather than the java code.
Which is the underlying database you are using with MDM? As some users have faced some difficulties when working with the DB2 Data base,If this is the data base you too are working upon then may be the issue could be similar,if possible try using the Oracle or SQL data base as these databse show more compatibility than a DB2 when working with MDM .
Also check the MDM users autorization and authentication to modifyor create recordrs in MDM.try given the user the ADMIN rights,and tehn try and see if teh user is able to modify/Create the mdm records.
Lastly you can check the database instance and listener configuration correctly.try restarting the Database service form the system if possible.
Hope It Helped
Thanks & Regards
Simona Pinto -
MDM Business Package Deployment error
Hi,
I am getting the following error while deploying the MDM Business package through JSPM at the check stage.
com.sap.sdt.jspm.phases.PhaseTypeJSPM
com.sap.sdt.util.diag.JavaException
java.lang.NullPointerException: null
JSPM_MAIN,JSPMPhases,NetWeaver Upgrade,
SAPJup
Java Upgrade
Can anyone let me know what can be the reason .
Best Regards
SidHi,
Try to add more memory to your database server in start up parameter. Like 512 or 1G. Bacause there me be insufficient memory. After this restart your db server.
or
It may be problem with downloaded business package. Try to check the size and compare.
Also try to check this note # 891983
Regards,
Padman -
MDM Lock command giving error MDMClientError:71 on Mavericks
I registred OSx 10.9 to my MDM server and installed MDM profiles successfully and when i send a lock command to the device it is not locking the device and i could see the below error in system.log file:
*** ERROR *** [Agent:501] ### Errors while processing: DeviceLock ###
*** ERROR *** [Agent:501] <MDMClientError:71> Command received for: <User: 503> but restricted to: <Device> <MDMClientError:71>
The same command is working fine in OSx 10.7/10.8 and iOS devices. I tried on different 10.9 systems but failing on all the devices with same error.
Not sure what went wrong, does mavericks need any configurations/settings tobe changed? Anyone faced this issue any time??
Any suggestions will be highly appreciated.below is the correct error log :
*** ERROR *** [Agent:501] ### Errors while processing: DeviceLock ###
*** ERROR *** [Agent:501] <MDMClientError:71> Command received for: <User: 501> but restricted to: <Device> <MDMClientError:71> -
MDM Import Server after error in import file
We setup Import Server and it processed a few files. then we tested what happens when there is an error. it logged a file to LOG folder. but would not start picking up new files we dropped in the READY folder. We removed the file with an error but still nothing; we fixed the error and put the file back and still nothing; we stopped and restarted the server, reposititory and import server but still nothing. Any ideas how we "reset" import server so it will start to process files again ? thanks
Hi Jay
I have faced the similar problem; have done some turn around to make things work, it may not be permanent solution. I have cleared the folders LOG,EXCEPTION(StructuralX), STATUS by copying the files to someother location for future reference and it worked.
Please feel free to revert to me for further clarifications.
thanks
Alexander
Note:Please mark the helpful answers. -
PI MDM Adapter Error - MDM port not found
We are working on an R/3 - PI - MDM scenario using the PI MDM Adapter. We are currently encountering the following errors.
In RWB - Communication Channel Monitoring
MDM Adapter listener could not start due to: Can not create repository session '<server=XXXXXXXX serverUser=Admin repository=Product user=Admin>' caused by: Connection Failed: Cannot create connection to MDM Server 'XXXXXXXX' for one of the following reasons: (1) server does not exist, (2) server is not started, or (3) input/output problem while creating connection, error code: UnknownServer
In RWB - Message Monitoring
2009-09-08 15:31:22 Error Message could not be forwarded permantely to the JCA adapter. Reason: System error: MDM port not found
2009-09-08 15:31:22 Error Message could not be forwarded to the JCA adapter. Reason: Permanent error: Adapter call failed. Reason: com.sap.aii.af.lib.ra.cci.XIAdapterException: System error: MDM port not found
2009-09-08 15:31:22 Error Adapter Framework caught exception: System error: MDM port not found
2009-09-08 15:31:22 Error Delivering the message to the application using connection MDM_http://sap.com/xi/MDMAdapter failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.lib.ra.cci.XIAdapterException: System error: MDM port not found.
Is there an issue with our receiver communication channel and the MDM Access Parameters? We are using the Port code and Remote System code provided by the MDM team.
Anyone experience this same issue?We are no longer seeing the MDM Port Not found error, but we are still seeing the UnknownServer error. Looking at RWB Message Monitoring it appears that the message is successfully sent to the MDM server, but nothing is coming into the Ready folder. Any ideas on where the message is going, and why it is not showing up in the Ready folder?
In RWB - Communication Channel Monitoring
MDM Adapter listener could not start due to: Can not create repository session '<server=XXXXXXXX serverUser=Admin repository=Product user=Admin>' caused by: Connection Failed: Cannot create connection to MDM Server 'XXXXXXXX' for one of the following reasons: (1) server does not exist, (2) server is not started, or (3) input/output problem while creating connection, error code: UnknownServer
In RWB - Message Monitoring
2009-09-11 14:04:15 Information The message was successfully received by the messaging system. Protocol: XI URL: http: //XXXXXXXX/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2009-09-11 14:04:15 Information Using connection MDM_http ://sap.com/xi/MDMAdapter. Trying to put the message into the receive queue.
2009-09-11 14:04:15 Information Message successfully put into the queue.
2009-09-11 14:04:15 Information The message was successfully retrieved from the receive queue.
2009-09-11 14:04:15 Information The message status was set to DLNG.
2009-09-11 14:04:15 Information Delivering to channel: MDS_TEST_CC
2009-09-11 14:04:15 Information The message was successfully delivered to the application using connection MDM_http ://sap.com/xi/MDMAdapter.
2009-09-11 14:04:15 Information The message status was set to DLVD.
I thought the implementation of the MDM Adapter was suppose to be straightforward and simple
Edited by: Chris Williar on Sep 11, 2009 9:56 PM -
We are trying to archive a repository on our MDM instance and we receive the following error:
$$$ Operation ended in ERROR : 84020008H : Database binary object error.
I then went on to check the repository and got this 1 warning:
$$$ Warning(1329): Table A2i_1 needs compacting(IdMax=171, IdCount=137).
I did some searching and found a way to compact the table with this command in sqlplus:
alter table A2i_1 shrink space compact;
But it has not have resolved the issue. We are running MDM on a Windows machine with an Oracle database. Has anyone seen this message before? Any help would be greatly appreciated.
Edited by: Nicole on Apr 8, 2008 11:29 PMHi Nicole,
I have not faced this problem before, but since the error tells you that the repository needs to be compacted.
I hope you have tried compacting the repository from Console.
RIght click on the rep-> Compact Repository.
Also if you have mentioned the error, you can also find out Which table and which line in MDM is causing the error.
Table A2i_1 needs compacting(IdMax=171, IdCount=137).
May be you must have created something before, that you have deleted later on. But the memory might have remained.
Also it sometimes might happens because of the Field Length. It should be kept to a minimum. Check your repository manually also.
Then kindly check and Verify your repository for errors.
Hope it helps.
Thanks and Regards
Nitin jain -
Log File Error when open MDS_Log from MDM Console
Hi Experts,
I am facing a problem when I tried to open MDS_Log file from MDM Console. The error message was showing as below:
Log File Error
Problems in the log file prevent Console from displaying its contents. To view log contents, open the log file in a seperate text editor.
Could any of you advise me how to open the log in a seperate text editor from MDM console ?
Thanks very much in advance
Regards,
Wei DonaHi ,
Just right click on record pane of log node and select save .it will sav to user defined location in .csv format.
Please try at yr end.
Thanks,
Sudhanshu
Maybe you are looking for
-
Iphone isn't being recognised by in Itunes on Windows 7
Hi Im using a Toshiba L500 laptop with windows 7 that was preinstalled. I transfered all my Itunes files and other files over from old Toshiba Laptop to this one and found that when I plug in my Iphone into Itunes after re-installing everything Itune
-
PROBLEM in all CS3 ARABIC TEXT Adobe Please Solve this
Dear Adobe We are all very happy when you introduce CS3 application. But know too much problem with these applications. First of all one big mistake you don't put contact E-mail address on your web site. For new user have a big problem to tell you ab
-
How to run a batch file from within an Oracle 9i Form?
Hi, I would like to execute a batch file from within an oracle form - I'm assuming there's some PLSQL command I can use? I am not allowed to use any third party libraries, and I'm hoping I can get away without having to progam any C or Java to do it.
-
SQL Developer 2.1.1 Editor question
Finally the problem posted here Re: SQL Developer 2.1 no longer allows to edit another granted schemas resolved. Now we can edit all granted schemas. I think, this is the most important improvement in this version! Thank you! But now, IMHO, we have t
-
Tax Accounts - Is it necessary to have separate tax acct. for each state
I am new at this: Is it necessary to have separate AR/AP/ account for each tax jurisdiction like state county etc?\ Or do the sales tax reports for payments in SAP produce outstanding taxes per jurisdiction. I would prefer only one Sales Tax account