MDM Database command execution error. A SQL statement failed to execute

[Former Member]

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 :

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 PM

[Former Member · Accepted solution]

Hi 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

[Former Member · Accepted solution]

Hi Simona,

Thank you for your response.

I have also noticed that there is only one custom MDM application which has this issue. Other custom MDM applications developed in WebDynpro for Java use the same username/password and do not get this error.

Nevertheless, we are checking with username/password and will update.

Regards,

Subramanian V.

[Former Member]

This was a Java code issue. Thanks for all the help.

Regards,

Subramanian V.