Com.sap.sql.DuplicateKeyException in file receiver channel

Hi experts,
I am currently testing the following scenario:
xml file -> file sender ->file receiver -> csv file
No mapping is used. Both channels are on the same PI 7.1 system.
The transformation seems to work so far. The only problem I have is that my receiver channel does not post the message to the directory because of this error:
Delivering the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id f167e134-145e-4b2c-2d47-e431b8b34fd8(INBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: [200]: Duplicate key.
Is it not possible to use file sender and file receiver in the same scenario? Thanks for any help.
Best regards.
Oliver.

Hi André,
I am using the test option so the message can be processed multiple times. Anyway, I also tried using deletion but I still get the same error. I also tried a completely new file but still no change. When I check the comm channel I see that there is always created a new message id and when I search the rwb it posts two entries. One from the sender step and one from the receiver step. Seems to be alright to me.
Regards.
Oliver.

Similar Messages

Com.sap.sql.DuplicateKeyException in file sender adapter

Putting message into send queue failed, due to: com.sap.aii.af.ra.ms.api.DuplicateMessageException: Message ID 01e6c3b0-0db0-11df-8e63-005056c00001(OUTBOUND)
already exists in database: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00140762) violated.
Returning to application. Exception: com.sap.aii.af.ra.ms.api.DuplicateMessageException: Message ID 01e6c3b0-0db0-11df-8e63-005056c00001(OUTBOUND)
already exists in database: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00140762) violated
plzzz help me i have tried all the forums threads...but didnt gt any usefull answer....!!!!

Hi Kiran,
>>no messages r there in sxmb_moni.....this trx code is not updating this particular channels files
So you are saying that all other messages are visible in transaction SXMB_MONI? If yes then do these:
1. try to do a dummy change in the channel and then activate it.
2. see whether there are any red entries in Integration Directory cache, if yes then take the corrective measures for making it green
3. Stop and start the channel using communication channel monitoring
4. Remove the already placed file and try placing some another file there and see whether that reaches SXMB_MONI
>>trnx prblm etc
Please avoid short forms when you ask or reply a thread. Since this is a community forum, these short form may not be understood by everyone reading these replies. Hope you will keep this when you post future threads/replies.
Regards
Suraj

Com.sap.sql.DuplicateKeyException in File Adapter

Hi,
In my Sender File Adapter, Randomly i'm getting the following error :
Putting message into send queue failed, due to: Message ID 710eaff0-91f3-11db-c706-001125a68f32(OUTBOUND) already exists in database: com.sap.sql.DuplicateKeyException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 1;SAPP08DB.XI_AF_MSG.
My poll interval is 10 sec. the funny part here is if a message takes 30 mins to get processed, and mean while next file is placed on the same location, the second one gets overwritten by the first one. as a result, i'm loosing few files. Can any one please help me out in this regard.
Need solution for both the points above.
Any help wud b appreciated.
Regards
Nilesh.

Hi Sandro,
The Scenario is simple. File to File.
Source Dir : Test\Source.
File Size : 1 KB.
Usage of Module processor : yes.
Content Conversion : No
Processing mode: Delete.
File Name : orders.txt (always the same file name).
Target Dir : Test\Target.
The problem is that our XI server is facing some memory problems and sometimes it will be slowed down. if orders.txt takes 30 mins (12:00 to 12:30 ) and then second orders (after the deletion of the first orders.txt) starts processing at 12:30, the second message gets overwritten by the first one. as a result same orders.txt message is sent in both the cases there by loosing the second orders.txt file.
The quality of service is EO.
Any update on this y it is behaving in this way.
Regards
Nilesh

GPEngineException Caused by a com.sap.sql.DuplicateKeyException

Often, we are getting the following error when we do an instance of GP Process from WebDynpro code, however in a second attempt with the same data the GP Process is created successfully: 
 
//----- CODE -
// 
IGPUserContext userContext = null; 
IWDClientUser wdUser = null; 
IUser user = null; 
IGPProcess process = null; 
IGPRuntimeManager rtm = null; 
IGPProcessRoleInstanceList roles = null; 
IGPStructure params = null; 
 
try { 
 wdUser = WDClientUser.getCurrentUser(); 
 user = wdUser.getSAPUser(); 
 userContext = GPContextFactory.getContextManager().createUserContext(user); 
 process = GPProcessFactory.getDesigntimeManager().getActiveTemplate(GP_ID, userContext); 
 rtm = GPProcessFactory.getRuntimeManager(); 
 roles = rtm.createProcessRoleInstanceList(); 
 
 params = GPStructureFactory.getStructure(process.getInputParameters()); 
 params.setAttributeValue("ORDER_ID", wdContext.currentSalesOrderModelResponseResultElement().getOrderID()); 
 params.setAttributeValue("CLIENT_ID", wdContext.currentCustomerDataElement().getCustomerID()); 
 
 processName = "Request ofequipment " + wdContext.currentSalesOrderModelResponseResultElement().getOrderID(); 
 IGPProcessInstance prInstance = rtm.startProcess(process, processName, processName, user, roles, params, user); 
} catch(Exception e) { 
 logger.traceThrowableT(Severity.ERROR, "Request Equipment Error: ", e); 
} 
//----- CODE -
// 
 
//----- EXCEPTION -
// 
com.sap.caf.eu.gp.exception.api.GPEngineException: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=1;SAPQNEDB.CAF_GP_PFWRUSRPT, DRIVER=3.53.95
at com.sap.caf.eu.gp.exception.impl.ExceptionUtil.convertTo(ExceptionUtil.java:36)
at com.sap.caf.eu.gp.process.rt.impl.GPRuntimeManager.startProcess(GPRuntimeManager.java:150)
at com.gmodelo.meta.vac018.wd.b.equipmentrequestcomp.EquipmentRequestComp.createEquipmentRequest(EquipmentRequestComp.java:1123)
at com.gmodelo.meta.vac018.wd.b.equipmentrequestcomp.wdp.InternalEquipmentRequestComp.createEquipmentRequest(InternalEquipmentRequestComp.java:1184)
at com.gmodelo.meta.vac018.wd.b.equipmentrequestcomp.EquipmentAssignationView.onActionExecuteRequest(EquipmentAssignationView.java:346)
at com.gmodelo.meta.vac018.wd.b.equipmentrequestcomp.wdp.InternalEquipmentAssignationView.wdInvokeEventHandler(InternalEquipmentAssignationView.java:587)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:131)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:72)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:156)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:91)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:161)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:109)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:96)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:469)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1431)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1251)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:158)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:81)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:507)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:527)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingPortal(ApplicationSession.java:472)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:251)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:699)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:231)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:231)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:205)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:93)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:105)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.dispatch(ApplicationHandle.java:320)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
at com.sap.tc.webdynpro.portal.pb.impl.LocalApplicationProxy.sendDataAndProcessActionInternal(LocalApplicationProxy.java:1043)
at com.sap.tc.webdynpro.portal.pb.impl.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:287)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1569)
at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:357)
at com.sap.portal.pb.PageBuilder$PhaseListenerImpl.doPhase(PageBuilder.java:2110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:219)
at com.sap.tc.webdynpro.clientserver.phases.PortalDispatchPhase.execute(PortalDispatchPhase.java:52)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:161)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:109)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:96)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:469)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1431)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1251)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:158)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:81)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:507)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:527)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:458)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:249)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:699)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:231)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:231)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:205)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:93)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:105)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
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:71)
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:71)
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:71)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:295)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
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:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: com.sap.sql.DuplicateKeyException: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=1;SAPQNEDB.CAF_GP_PFWRUSRPT, DRIVER=3.53.95
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonPreparedStatement.java:355)
at com.sap.sql.jdbc.common.CommonPreparedStatement.execute(CommonPreparedStatement.java:917)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.execute(PreparedStatementWrapper.java:269)
at com.sap.caf.eu.gp.model.pfw.core.impl.UserProvidedDataManager.setTexts(UserProvidedDataManager.java:326)
at com.sap.caf.eu.gp.model.pfw.core.impl.UserProvidedDataManager.updateTexts(UserProvidedDataManager.java:357)
at com.sap.caf.eu.gp.model.pfw.core.impl.ProcessRuntime.startProcess(ProcessRuntime.java:1141)
at com.sap.caf.eu.gp.process.rt.impl.GPRuntimeManager.startProcess(GPRuntimeManager.java:148) 
//----- EXCEPTION -
// 
 
Regards 
FSC 
Edited by: Fernando Salgado on Mar 9, 2011 12:02 AM

Hey Anil,
maybe this thread will help:
https://forums.sdn.sap.com/click.jspa?searchID=734730&messageID=2934036
Regards
Dominic

Com.sap.sql.DuplicateKeyException

Hi
I am trying to send a response that i get as an inline content to my mail. I used the following in the module processor
Module Name : localejbs/AF_Modules/MessageTransformBean
Type : Local Enterprise Bean
Module Key : mail
Transform.ContentDisposition inline;filename="Response.txt"
Transform.ContentDescription Response
Transform.ContentType text/plain;name="Response.txt"
But when i check my RWB i get the following error message
2005-09-26 13:47:51 Success Trying to put the message into the send queue.
2005-09-26 13:47:51 Error Putting message into send queue failed, due to: Message ID 4336cff8-97a3-5ad5-e100-0000ac16041b(INBOUND) already exists in database: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPX10DB.SYS_C00275497) violated.
2005-09-26 13:47:51 Error Delivery of the message to the application using connection AFW failed, due to: Message ID 4336cff8-97a3-5ad5-e100-0000ac16041b(INBOUND) already exists in database: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPX10DB.SYS_C00275497) violated.
Any suggestions friends as to why this is occurring.
cheers
Sameer

It seems when message is persisted by adapter engine there is some duplicate value going.
There could be a possibilty of datbase table overflow where messages are persisted.
You can check and analyse that.
Hope it helps,
cheers,
Satish

Error in file receiver channel "Unknown payload format 0 in the message"

hello
there is an errror in my receiver file channel with the status "Unknown payload format "
my channel is file receiver channel.
we implemented one sap note 1295430 and after that channnel is giving the error.
Please forward your views.
thanks.

Hi there,
First of all, what TBDL means - It means that the message was successfully delivered from Integration Server and that the messages are handed over to the Messaging System.
TBDL occurs when the message is put into the receiving queue of the Messaging System.
What can be done?
Go to Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>/<PROTOCOL>
If this was executed successfully, then the MS returns HTTP 200 to the Integration Server and the status TBDL moves to DELIVERING (check whether you have authorization to go to the above link).
--> Log-in to SAP using - XIAPPLUSER & XIAFUSER, and check if they are blocked
--> Check the messages:
AF
com.sap.aii.adapterframework.serviceuser.language
com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
com.sap.aii.adapterframework.serviceuser.pwd
AS
com.sap.aii.applicationsystem.serviceuser.language
com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
com.sap.aii.applicationsystem.serviceuser.pwd
Also, worth reading - /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Let us know if you have more questions.
regards,
Neetesh

Error in File Receiver Channel

Dear All,
I am Getting below error in File Receiver Channel.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: FTPEx: User ABC cannot log in.
Regards,
Manikandan

Hi Manikandan,
Check the username and the password for the FTP server. If the username or the password is wrong then you would be able to post the message.
Also, there might be a timout issue, In the timeout parameter enter some value.
Ref: FTP Server connection Problem
Check and update us.
Thanks,

NoClassDefFoundError: com/sap/sql/log/OpenSQLException

I have developed a Java project. It consists of 2 SQLJ files and then a Java class. When I try to execute the Java program, I get a Java error:
java.lang.NoClassDefFoundError: com/sap/sql/log/OpenSQLException
at com.mbb.crrs.business.report.dao.ReportDAO.<init>(ReportDAO.sqlj:23)
at com.mbb.crrs.business.report.dao.Test.main(Test.java:24)
Exception in thread "main"
I notice a similar problem on message: Re: Which jar to include com.sap.sql.log.OpenSQLException
Is that something that I need to maintain for it to work? Thank you.

Hi,
the problem one year ago was that the SQLException class was not available through remote access. I don't know if that might have been changed meanwhile in the latest release.
I implemented a simple work around: I caught every SQL-exception in the method where it was thrown, wrapped the exception message and any nested exception in a self written exception and threw this new exception. That worked fine.
Regards, Astrid

Com.sap.sql.log.OpenSQLException during EntityManager Call

Hi!
I deployed an EJB3 session bean on the NW 7.1.
The aim is to use JPA with this bean.
I configured the "persistence.XML" for the bean project and packed it into the jar File and a "data-source-aliases.xml" which is included in the ear file. The packaging of the ear-file is done with the developerStudio and deployed on the NW 7.1
Then I created a dataSource project which contains the "data-sources.xml" and deployed this too.
Here is my data-sources.xml:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE data-sources SYSTEM 'data-sources.dtd'>
<data-sources>
 <data-source>
 <data-source-name>JPA_SDN_EXAMPLE_DS_555</data-source-name>
 <driver-name>ora10</driver-name>
 <sql-engine>native_sql</sql-engine>
 <jdbc-1.x>
 <driver-class-name>oracle.jdbc.driver.OracleDriver</driver-class-name>

 <url>jdbc:oracle:thin:@10.XXX.7.27:1521:orcl</url>
 <user-name>bdeadm</user-name>
 <password>dmin</password>

 </jdbc-1.x>
 </data-source>
</data-sources>
My deployed session bean looks like this:
@Stateless(name="WorkerBean")
public class WorkerBean implements WorkerRemote {
 @PersistenceContext(unitName="JPAModel")
 private EntityManager em;
 public String sayHello() {
The last step was the deploment of the oracle driver on the NW7.1 under the "Application Resources Overview". The driver I named "ora10".
Now if I call my Bean shown above with its Entity Manager Call for the injection I got the following exception:
Caused by: com.sap.sql.log.OpenSQLException: Error while accessing porting layer for ORACLE database via getSessionId().
 at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:148)
 at com.sap.sql.jdbc.direct.DirectConnectionFactory.createPooledConnection(DirectConnectionFactory.java:532)
 at com.sap.sql.jdbc.direct.DirectConnectionFactory.createDirectPooledConnection(DirectConnectionFactory.java:157)
 at com.sap.sql.jdbc.direct.DirectConnectionFactory.createDirectPooledConnection(DirectConnectionFactory.java:117)
 at com.sap.sql.connect.factory.PooledConnectionFactory.createPooledConnection(PooledConnectionFactory.java:119)
 at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledConnection(DriverPooledConnectionFactory.java:38)
I have no idea, whats wrong. Perhaps my driver is wrong or not set properly ?
Can anybody help me please ?
Thanks in advance,
Hendrik
Edited by: henne123 on May 18, 2009 6:19 PM

I have tried that.
[EXCEPTION]
*com.sap.sql.log.OpenSQLException: The SQL statement "SELECT * FROM EPD.SAPEPDDB.UME_EP_SLD" contains the syntax error[s]: - Open SQL syntax error: table names must not specify a catalog name (delete "EPD". before "SAPEPDDB"."UME_EP_SLD")*
Database name must be Ok, because i can access to other tables which are in the same DB...
Thanks for your help

Com.sap.sql.log.OpenSQLException: table or view not exists

Hi!.
I'm developing a Portal Component over NW EP 2004s (7.0) which access to SQL Server database. I have created three tables on the system db (EPD). Connection is Ok, over datasource object, but i can't make a SELECT operation to my new tables.
Hovewer, making a SELECT operation over older system tables is OK.
I have adjusted permissions on my new tables, similar to the older tables. The table's owner is the same too.
The exception i get is:
**Exception of type com.sap.sql.log.OpenSQLException caught: The SQL statement "SELECT * FROM "SAPEPDDB"."UME_EP_UNLOCKUSERS"" contains the semantics error[s]: - 1:24 - the table or view >>UME_EP_UNLOCKUSERS<< does not exist**
[EXCEPTION]
*com.sap.sql.log.OpenSQLException: The SQL statement "SELECT * FROM "SAPEPDDB"."UME_EP_UNLOCKUSERS"" contains the semantics error[s]: - 1:24 - the table or view >>UME_EP_UNLOCKUSERS<< does not exist*
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:38)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.CommonStatementImpl.executeQuery(CommonStatementImpl.java:114)
at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeQuery(StatementWrapper.java:172)
at com.uralita.database.DbManager.executeQuery(DbManager.java:105)
at com.uralita.ListaSistemas$ListaSistemasDynPage.getSystemsR3(ListaSistemas.java:184)
at com.uralita.ListaSistemas$ListaSistemasDynPage.doInitialization(ListaSistemas.java:93)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:105)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)
at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
at java.lang.Thread.run(Thread.java:534)
Caused by: com.sap.sql.sqlparser.CommonSQLParserException: - 1:24 - the table or view >>UME_EP_UNLOCKUSERS<< does not exist
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:171)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
... 19 more
caused by
com.sap.sql.sqlparser.CommonSQLParserException: - 1:24 - the table or view >>UME_EP_UNLOCKUSERS<< does not exist
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:171)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.CommonStatementImpl.executeQuery(CommonStatementImpl.java:114)
at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeQuery(StatementWrapper.java:172)
at com.uralita.database.DbManager.executeQuery(DbManager.java:105)
at com.uralita.ListaSistemas$ListaSistemasDynPage.getSystemsR3(ListaSistemas.java:184)
at com.uralita.ListaSistemas$ListaSistemasDynPage.doInitialization(ListaSistemas.java:93)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:105)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)
at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
at java.lang.Thread.run(Thread.java:534)
Someone has been getting this problem? Any idea?
Thanks!

I have tried that.
[EXCEPTION]
*com.sap.sql.log.OpenSQLException: The SQL statement "SELECT * FROM EPD.SAPEPDDB.UME_EP_SLD" contains the syntax error[s]: - Open SQL syntax error: table names must not specify a catalog name (delete "EPD". before "SAPEPDDB"."UME_EP_SLD")*
Database name must be Ok, because i can access to other tables which are in the same DB...
Thanks for your help

Missing com.sap.engine.lib jar file?

Hi all,
Please send the com.sap.engine.lib.jar file to me, It's missing in the installation.
Regards,
CSP

Hi Pradeep,
I think, you can download this from sap service market place.
Regards
Kapil

Writing to 2 different directory using file receiver channel

I have a scenario where i am picking multiple files from one server and writing it on another. While writing the files, i want to write them to different folders using one communication channels based on the filename. is it possible? if yes how?

You have to go for dynamic configuration UDF in the mapping.
Refer to the below document
http://wiki.scn.sap.com/wiki/display/XI/Dynamic+file+name+and+directory+in+Receiver+File+Adapter+-+summary+of+possibilities
Also http://****************/Tips/XI/ASMA/Index.htm
You just need to add filters/fix value lookup and pass it to UDF to determine the target directory
Message was edited by: Hareesh Gampa

Com.sap.km.cm.docs file corruption error

Problem Description
Within the Portal there are several html files served up to a user through the KM repository. These html files contain links that open up 'pdf' files stored within the KM repository. These links are served to the user via the 'com.sap.cm.km.docs' par file. There seems to be some problem with this par file which streams a file across to an end-users browser from the KM repository.
For some users, when they click on a link to a pdf file they get a 'File corrupted' message on their browser's end. They always get this error no matter how many times they open it up. Other users on other desktops can click on the link and receive the file without any error. Also the same user can open up links to other pdf files without a problem.
Has anybody faced this problem. This is a very sproadic incidence that happens. When we do a binary comparison of the file sent by com.sap.km.cm.docs par file there is a binary difference however the size are same.
Please let me know if you know what the problem could be or have come across the same.

Hello! Ankur,
We had the same problem and we successfully resolved it. The problem resides in PDF readers, please fallow the below steps to solve it.
1) Open Adobe Acrobat reader.
2) Go to Edit -> Preferences option as shown in the screenshot below.
3) On the Preferences window that opens, select Internet from the various options present on the left side.
4) On the right hand side options, select the Display PDF in browser option.
5) Uncheck Allow Fast Web view.
This will really helps in opening PDF documents from KM.
Please award point if this solution helps you.
Thanks!
Regards,
Kishore

Adapter Module Filename in File Receiver Channel

Hi All,
is it possible to set the Filename in File Receiver Adapter from Adapter Module?
I know that it is possible to read the data
Channel ch = new Channel(moduleContext.getChannelID());
path = ch.getValueAsString("file.targetDir");
I Need to set the filename in Adapter Module, using of Payload is not possible because Payload is not xml.
Dynamic Parameters in Message Header is not possible because it is an multi mapping process an i need dynamic Filename for each Part
payload after mapping is like
MainDocument
SubMainDocument
MainDocument
SubMainDocument
i need special Name for each SubMainDocument in FileReceiverAdapter
regards
ralf

Hello Stefan,
interface mapping is an mapping like this:
outbound_interface => Inbound_Interface1
                             => Inbound_Interface2
                            => Inbound_Interface3
in sxmb_moni this looks like this
Soap_Header
Soap_Body
Payloads
     =>MainDocument ( application/xml )
    => SubMainDocument ( text/xml )
     =>MainDocument ( application/xml )
    => SubMainDocument ( text/xml )
First SubMainElement is routing to FileReceiverAdapeter A   where Filename has to be like "NameA%nr%"
second SubMainElement is routing to FileReceiverAdapeter B   where Filename has to be like "NameB%nr%"
%nr% is som value from the Payload.
Payload is not xml because using of Conversion Argent!!
I Think there is only one Dynamic in Header for all subelements, i have test it!
ralf

BCM/SWIFT payment, parameter file Receiver channel

Iu2019m using the u201CSWIFT_payload_parFile_Splitu201D Operation Mapping for the FILEACT payment transaction.
The result should be
1) payload file
2) parameter file (*.par)
This seems to work just fine. My problems starts with the receiver channel for the *.par file.
I need to know more about how to setup the modules and parameters in the "*.par" receiver channel.
Is there a configuration guide for this?
Thanks.
Frank

Hi Frank,
I am facing similar issue. I am able to generate the parameter file but the overrides section contains only one parameter "Request Type" whereas there are other parameters that are mandatory. How do I get these filled?
Regards,
Deepthi

Com.sap.sql.DuplicateKeyException in file receiver channel

Similar Messages

Maybe you are looking for