URGENT: SAP + SQL EM dead

Apologies for the cross post
Background:
No-one logged in license manager (apart from myself - manager)
No-one at the office (so no-one could have logged in)
Tried deleting a UDF on Item Master Data-> Warehouses. Got an error saying SERVER is still connected. We always get this unless we stop the mailer service. Hit ignore, then yes (to delete the UDF)
Hourglass appears, B1 looks dead (this is normal for a few minutes in this kind of operation). Did the same thing this morning, it took 5mins. After 20mins, nothing is happening. Not-normal.
Killed B1 (this is on my laptop), then tried going back in. Error (-1102)
Went onto my server, and tried accessing EM to see who was connected, tasks etc. to see what was going on. EM doesn't respond once I click "databases"
Look in taskmanager, and SQL is eating up RAM. Wait for a while -> Have to stop the SQL service/Kill EM.
Start the SQL service -> EM still doesn't respond when "databases" clicked. Restart server, no changes.
The only related SAP note requires me to be able to access my DB via EM to recreate the DB User, which I cannot do.
This is a live server, and people are going to come in on Monday expecting to work. Last backup is from Thursday night. Can anyone suggest what to do?!?!? Could my data really be damaged?
I promise I'll be a good boy and backup every time I touch a UDF from now on!

Apologies again for the cross post... a bit of a progress report
Looked at the SQL data folder and noticed that my log file for my "live" DB is 9gig!! The DB itself is only 9gig, and normally the log file is much much smaller (worst case maybe 300MB?).
Removing the database and the log file from the data directory makes SQL EM responsive, and I can log into my test databases etc with no problems.
So... the million dollar question is, what do I now do with a 9gig Database, and 9 gig log file which I can't use in my "data" directory?
Thanks
Rajiv

Similar Messages

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

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

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

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

Copy Tables between SAP's SQL DB to non-SAP SQL db

Hi All,
We have a requirement in which we have to extract selection fields from Material master, material BOM's, Process orders, material selling prices, etc.. from our SAP system ( runs on SQL DB )and send it to a non-SAP SQL db. Our non-SAP IT staff wants to copy the tables at the DB level, but our SAP resources suggest that a program be written to do the extract. Kindly advice which is the best and recommended option. The data has to be sent periodically.
Regards,
S

It is always not a good practice to access the base tables directly for any reason. You can either write a program or research on SQL Server Integration Services (SSIS) and identify OLE DB drivers to connect to SAP System. I know you can connect to SAP BW from SSIS using SAP BW OLE DB Driver. You can also connect to SAP System from .NET applications. I hope this information helps you.
Regards
RT

WT SynchManager instl. on a different Server other than SAP/SQL Server.

Hi,
Is it possible to move/install WebTools SynchManager on a different server other than the SAP/SQL Server? Please let us know.
Note:
1. We are aware of the recommendation: u201CInstall the SynchManager on the SAP Business One server on which the DI API is installedu201D in the "Business One Web Tools SynchManager Guide.pdf".
2. But, SAP/SQL Server at our Client is starving of RAM due to a high number of windows services/application trying to run at the same time (although the maximum amount of RAM possible under the current configuration is installed (4GB)).
3. So, we are evaluating as to which of these application (WebTools being one of them) can be moved to a different server.
Thanks and Regards,
Kafil Shumon.

Hi Kafil,
You can put the synchmanager on a different server as long as the DI API is installed and that server can access the B1 licensing server.

Is it possible to write an abap code be SAP SQL query.(ECC 6)

hello guys,
Is it possible to write an abap code be SAP SQL query.
Scenario : table A has a field say f1 of length 10 and table B has a field say s1 of lenght 20. in sap sql i am able to link all the other tables but i am not able to link
table Af1 --->Table Bs1. as the length doesnot match. so is it possibel that using abap code I can pick 10 characters from table A field f1 adjust it to 20 characters using abap and map it to field s1 of table B.
Please let me know how to accomplish this if possible.
thanks in advance!!

Herm,
Adding code is done in the infoset.
Please do following:
> Goto SQ02
> Type in the infoset that the basis for your query, <change>
> Press <code> OR <shift><f8>
> Tou'll see 4 tabs: Extras, Selections, Code, Enhancements.
> GoTo tab Code
> Choose the coding section (<f4> gives you an overview)
> Enter the code.
You may set a breakpoint to see what the query in SQ01 will do with it.
Succes!
Frank

Content of SAP SQL Database and backup

1. The SAP database / data files store in the folder <SID>DATA with extension mdf, what does it store? Does it content the structure of the database only or inclusive of the daily entry of the SAP data?
2. Will it be sufficient to backup the SAP SQL Database with the SQL database ONLINE for recovery purpose in case of server crash?

Alvin Teo wrote:
Markus,
Thank you for your response.
I would like to clarify further that other than the database is required to be backup, any other SAP related system file that require to be include in the backup file occasionally, like during daily or weekly backup?
Yes - the instance directory and the Windows OS including the registry
Apart from this, do you happen to know where can I obtain the documentation which can assist me to do hardware sizing for SAP systems?
Usually it´s done the following way:
- the customer creates a project under http://service.sap.com/quicksizer
- the hardware partner takes this project and offers a machine that fits
Markus

SAP SQL Anywhere Licensing

Hi all,
whre can I find more information about the licensing option of SAP SQL Anywhere for SAP BOBJ installations?
Are there any differences to Sybase ASE license?
Best regards
Arne

Hi Arne,
Not really for SAP BOBJ license part but yes some info regarding SQL Anywhere license in the below given link
http://www.sybase.in/detail?id=1056242
SAP Sybase SQL Anywhere 16 Separately Licensed Components
Tutorial: Installing and Using SAP Sybase SQL Anywhere Database Client
Also I suggest raise your query to SAP in XX-SER-LIKEY-SYB component.
Regards,
Rafikul

SAP SQL 2008 Database Backup

Hi,
One of our client is taking the SAP SQL database backup using BRTOOL, backup happen on Standalone LTO 5.
They are taking backup of 1.4 TB in 1hr 30 Min.
I would like to know is it possible to achieve same as max write speed of LTO 5 in 140 MBPS, if we consider the are getting max throughput rate then too it should take around 3 hr 40 Min.
If it is possible then it would be grateful if someone can explain how.
Thanks & Regards
Mitt Gori

Hi Mitt,
You may refer the details shared under thread Full Database Backup in DB13 for MS SQL Server ... | SCN on configuration of backups using db13 for MSSQL.
What it comes to my mind is ..
1) Can you check whether you have SSDs configured for the database
2) What is the Tape write speed.
Note: SSD disks can drastically improve the backup times as it has excellent read/write performance over SAS disk.
Hope this helps.
Regards,
Deepak Kori

URGENT: SAP + SQL EM dead

Similar Messages

Maybe you are looking for