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

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 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.

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

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

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

SQL exception in File Adapter.

Hi experts,
I have a sender adapter of type file to retrieve data from ftp conexion. If I use a ftp client I can see remove the files, but when I active the communication channel appears this error in the communication channel monitor:
Error: com.sap.aii.af.ra.ms.api.DeliveryException: Problem inserting 633c24f5-b66e-4216-17b8-b91aa544cfcc(OUTBOUND) into the database: java.sql.SQLException: ORA-01400: no se puede realizar una inserción NULL en ("SAPSR3DB"."XI_AF_MSG"."VERS_NBR")
Any idea?
What is the reason which a sql exception is raised?
Thanks in advance.
Jose Manuel

Check Temporary Tablespace is Empty.
Go thru this thread for other inputs to resolve ur problem :
java.sql.SQLException

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

Can I stop batch reading, if any error comes in a batch, in File Adapter

Hi All,
I am reading files in batches of 100 lines as there are 1000 records. Can I stop further reading of records from a file, If any error comes in any batch.
e.g. If my file adatpter is readinf 101 lines, if any error comes in this line, then it should stop reading line 102 and so on.
Regards

Hi Vikas,
I am not sure what you mean exaclty by stop reading - would you be fine if the other lines are rejected till end of file, if an error is encountered?
Then you can achieve that by ensuring that your schema does not have nxsd:uniqueMessageSeparator="${eol}" in the schema element.
http://download-west.oracle.com/docs/cd/B31017_01/integrate.1013/b28994/adptr_file.htm#CACEGBFD
I am not entirely sure if that would be a good design decision though.
Regards,
Shanmu.
Edited by: sthiagar on Feb 5, 2010 9:23 PM

Sener file adapter has read/pick the files first in first out method.

HI
In my Interface I am Using Sender as File adapter. As per my requirement Sender file adapter has to read the file from file directory. This directory having 1000u2019s of files with some files are same name (time stamp is different) and some files are different name here file adapter has to pick the file with mentioned name in File sender adapter like ZMPSMSGSTATUSMST-.xml .
But source file name is like <TABLENAME>-<TIME_STAMP>.XML (ZMPSWRKFLOWHIST-20090527-150522-628) in file directory.
The file adapter in XI will poll to this directory and picks the file in first- in first-out by sorting according to timestamp.
To do this configuration what I have to do in sender file adapter please give me your valuable inputs.

HI Abhi,
Thank you for your spot replay.
I tested now but i am geting below error.
Putting message into send queue failed, due to: com.sap.aii.af.ra.ms.api.DuplicateMessageException: Message ID f4ca4f86-9c5d-4bdd-1fb1-a6bd7cda99a8(OUTBOUND) already exists in database: com.sap.sql.DuplicateKeyException: [NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__XI_AF_MSG__491A1D0B'. Cannot insert duplicate key in object 'dbo.XI_AF_MSG'..
Could not archive file 'E:\file\in\ZMPSMSGSTATUSMST-20090527-150522-628.xml' after processing
but i am able to see this file in Archive foleder. once file is archivied sucessfully the same file is delted from source directory?
I given processing parametes queue name is TEST.
Thanks
srinivas
Edited by: srinivasreddy p on May 28, 2009 8:43 AM
Edited by: srinivasreddy p on May 28, 2009 8:52 AM

File Adapter archiving mode....

Putting message into send queue failed, due to: com.sap.aii.af.ra.ms.api.DuplicateMessageException: Message ID a7cbcf00-4e00-11db-bd7f-0018717400ed(OUTBOUND) already exists in database: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00135467) violated.
2006-09-27 17:17:47 Error Returning to application. Exception: com.sap.aii.af.ra.ms.api.DuplicateMessageException: Message ID a7cbcf00-4e00-11db-bd7f-0018717400ed(OUTBOUND) already exists in database: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00135467) violated
2006-09-27 17:17:47 Error Attempt to archive file "D:\SSNEDI\test\in\queue\20060926070906359.txt" after processing failed. Retry
source directory : D:\SSNEDI\test\in\queue
target directory : D:\SSNEDI\test\in\queue\FB
But, source directory not deleted 20060926070906359.txt.
Target directory exist file too.
what's the matter?

Hi Kim,
If it is in test mode,the file wont get deleted in your source direcory. So the adpater will keep polling the file and the server will be flooded with messages. If it is in the delete mode file will be deleted,archive mode it will be moved in to the archived directory but in the test mode file will not be deleted from your source directory and will be polled continously by the adapter.
Also go thro' this link:-
Re: Archiving ftp files
Hope this provides a solution.
Regards.
Praveen

Com.sap.aii.af.ra.ms.api.DuplicateMessageException - Msg Successful

Hi all,
We have a scenario where JDBC sender adapter polls - DB2 data base.
Picks up the records. Updates the records.Messages are sent out.
Everything is fine. The message is sent to IE and then to the receiver.
But I see a com.sap.aii.af.ra.ms.api.DuplicateMessageException in the audit log.
2008-11-21 00:00:26 Error Putting message into send queue failed, due to: com.sap.aii.af.ra.ms.api.DuplicateMessageException:
Message ID 56149940-20b1-472f-0905-893a906a65cf(OUTBOUND) already exists in database:
com.sap.sql.DuplicateKeyException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: #XIR1N5J;000000030F.
2008-11-21 00:00:26 Error Returning to application. Exception: com.sap.aii.af.ra.ms.api.DuplicateMessageException:
Message ID 56149940-20b1-472f-0905-893a906a65cf(OUTBOUND) already exists in database:
com.sap.sql.DuplicateKeyException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: #XIR1N5J;000000030F

HI
I think there is some issue with your query. Its either updating the same field or database got some error.
Check notes 962578 & 831162
Thanks
Gaurav

Com.sap.sql.DuplicateKeyException in File Adapter

Similar Messages

Maybe you are looking for