2LIS_02_SCL Datasource dataload issue

Hi Sdns,
i am using 2lis_02_scl datasource, i am seeing the strange behaviour of the datasource.
I have filled the setuptables without any issues. then i am trying to load the data to the BI by using the Repair Full request infopackage. I found that some of the PO docuements are missing in BI. i have done the extraction for the same misssing PO's in RSA3 in R/3.
In RSA3, i am able to the see the data for missing PO's but these PO's are not getting transferred to the BI firsttime.
i again loaded the data to the BI without any selections in infopackage also, i can able to get the data for some missing records but not all.
for more information, this is happening in Quality systems.
Please help me on this issue.
Thanks in Advance
karunakar
Edited by: karunakark on Apr 5, 2011 3:14 PM

Where are you checking the data in BW?
Is it the PSA or the DSO?
And, you said that you are able to see the Data in RSA3 for PO's which do not get loaded to BI.
Please try to fetch such a PO using Repair Full -> Infopackage Selection -> Po Number.
See if you are able to see the data in the PSA of 2LIS_02_SCL.

Similar Messages

REMNG (Invoice qunty) field not getting values 2LIS_02_SCL Datasource ?

Hi,
I have added the standard field REMNG field to the ds 2lis_02_scl and I am not seeing any values either in rsa3 or psa. Can anyone suggest if anyone have seen this problem before.
BTW in RSA6 ...field only is selected, so do we need to uncheck it ? As I dont see any code written in CMOD for it. Please suggest some clues.
Thanks,

HI,
After activating the datasource did you fill the setup tables again for that application.If not then give a try to it and see if it works or not.
In the mean time i will search on the same issue.
Hope it helps.
Regards,
AL

MS SQL Server JDBC 2.0 datasource creation issue using Visual Admin

Hi,
I need to create an MS SQL Server JDBC 2.0 DataSource using the Visual Admin (running on NetWeaver 2004 SP19). I'm using the Microsoft SQL Server 2005 JDBC driver. Have no problem creating a Version 1.x (no XA support) DataSource.
The issue is that when I try to create a Version 2.0 (with XA support) datasource I get the following exception: java.sql.SQLException: Invalid DataSource reference
This is the setup I used:
JDBC Version "2.0 (with XA support)
JDBC 2.0 Compliant:
object factory: com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory
datasource type: XADataSource
xads class name: com.microsoft.sqlserver.jdbc.SQLServerXADataSource
On the additional tab:
databaseName=fldev_jj
portNumber=1433
serverName=dbsrv61
user=fldev_jj
password=******
Even added the url, but that made no difference. Chose Vendor SQL,
and have initial connections set to 1. This url worked when used
with a version 1.x datasource.
What can I try to do to resolve this?
Full exception:
java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during start of application "factorylogic.com/FactoryLogicBusinessDS". [id = StartupError]
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:608)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4557350:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "FactoryLogicDS".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance XAManagedConnectionFactoryImpl.
     at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:131)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1760)
     ... 42 more
Caused by: java.sql.SQLException: Invalid DataSource reference.
     at com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory.getObjectInstance(Unknown Source)
     at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:129)
     ... 43 more
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:663)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
     ... 31 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4557350:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "FactoryLogicDS".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance XAManagedConnectionFactoryImpl.
     at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:131)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1760)
     ... 42 more
Caused by: java.sql.SQLException: Invalid DataSource reference.
     at com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory.getObjectInstance(Unknown Source)
     at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:129)
     ... 43 more
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:270)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:127)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
     ... 33 more
     at com.sap.engine.services.dbpool.exceptions.BaseRemoteException.writeReplace(BaseRemoteException.java:178)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1016)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
     at javax.management.MBeanException.writeObject(MBeanException.java:126)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1301)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
     at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:964)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1301)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1309)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
     at com.sap.engine.services.jmx.ResponseMessage.writeBody(ResponseMessage.java:177)
     at com.sap.engine.services.jmx.Message.writeMsg(Message.java:257)
     at com.sap.engine.services.jmx.Message.getMsg(Message.java:453)
     at com.sap.engine.services.jmx.Message.writeExternal(Message.java:505)
     at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1272)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1250)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:66)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Leaving the object factory empty is absolutely part of the solution.
I can now start the data source and it can get a connection.
The remaining problem is that the moment I try to do anything with xa (inside of netweaver, using the datasource) I get an xa error... Found a way around that by changing the datasource type from "XADataSource" to a "ConnectionPoolDatasource".
The problem with that is that I'm no longer sure it uses XA transactions...
Will do more testing...
Very helpful reply Yuri!
Thanks

ASO dataload issue

Hi,
We are facing an issue with ASO dataload.
When we load '0' values in ASO, we see them as #Missing in the smartview and in database->Preview data.This is impacting our formulas.
We did not replace '0' with #Missing in our rule files.
This works fine with BSO where we see '0' when the value is 0 and the rest as #Missing.
Can I get any help on this as what could have gone wrong..
Thanks in advance
Edited by: 844747 on Nov 23, 2012 6:14 AM

In one sense nothing has gone "Wrong" the default nature of ASO data loads is to exclude missing and zero rows. This is to keepp the DB small. Depending on what version you are on, you can overried this default behavour in EAS or MaxL.

Export DataSource Performance Issues

Hi,
System: BI 7 with DataStage and R3
Problem We just finished a technical upgrade to the BI 7 system from BW 30 and what has happened is post upgrade the export datasource setting for default data transfer has been changed.
Where can I change the settings for default data transfer (I know it can be changed in SBIW and SPRO for global settings). It is currently using dialog processes to transfer data but I want use background processes to transfer the data. I was not able to find anything about changing the type of process used for data transfer.
Thanks,
Rahul

Perhaps export-clixml has a performance issue based on the size of the XML object being processed. If so, anything you can do to limit the size should help. You way you have arrays of custom PSobjects, and seem to already writing each array out to a separate
XML file. Is there someway that you could chop it up a little finer? Say if an array has 50,000 elements, what if you would write it in 2500 element chunks to a series of xml files? You'd then have to read it back in in a way that re-establishes the original
array.
Or, if your PSobjects generally contain all of the properties of the corresponding AD object, you could consider that perhaps you do not need them all; or you could filter one small set of properties to one xml file and so on...
Al Dunbar -- remember to 'mark or propose as answer' or 'vote as helpful' as appropriate.

How to use EXIT_SAPLEINS_001 for delta with 2LIS_02_SCL datasource ?

Hi,
I'm facing a problem using 2LIS_02_SCL: the field MCEKET-WAMNG is not populated during delta extraction (it is populated correctly when I fill setup tables).
I have been told that I should use customer exit EXIT_SAPLEINS_001 in order to fill MCEKET-WAMNG at event ML u2013 delivery, because 2LIS_02_SCL does not takes this event into account (only MA, MB, MC and MD which can be verified in LBWE Events), this field is not passed to BW in delta.
I need help to implement this solution.
An example with ABAP code will appreciated.
M.B.

Hi,
May helpful to you
EXIT_SAPLRSAP_001 vs EXIT_SAPLEINS_001
EXIT_SAPLEINS_001
Regards,
Suman

IC Dataloading Issue

Hi, I had made a new cube ZIC_C04 which only has a few KFs and dimensions that i required in a report.
I didn't use IC_C03 because i had to put in some KFs and one dimension from the master data(which again was modified).The cube is being updated by 2LIS_03_BF only.
Now the issue is that when i am loading data into the cube the request monitor shows that it has completed successfully and sets the status to Green but the request itself remains yellow when i click on manage to see the status of the Request inside the cube.
Plz Let me know how to take care of this issue.

Hi Prasun,
Check whether your Infocube settings has automatic request processing ticked for Set quality status OK.
Infocube> manage> Environment-->Automatic Request Processing.
Hope this helps.
Regards,
Siva.

DataSource Preview Issue

Dear Gurus, I have created a DataSource for a flatfile and in the preview I see the data for 2 columns are displayed as "1,223,234" and "ABC,DEF,GHI" while in the file it is "1223234" and "ABCDEFGHI". Can anybody point out what I have to correct to get this right?

For key figures, the commas you are seeing in the preview is only display setup on your profile, you can check/change this,
System -> User Profile -> Own Data (Defaults Tab)
It has nothing to do with internal and external format. For changing internal to external formats we use conversion routines which can be applied only between PSA and data target. Run the infopackage and you will see data in PSA without error.
If this is a characteristic field and not a keyfigure, then check the order of all the fields in the file and the datasource, they should be listed in the same order.

Database Adapter - Datasource creation Issue - Using WLST

Hi ,
Im tring to create a weblogic multi data source in an osb cluistered env using the wlst script and getting an issue while updating the plan.xml via script.
im getting the plan path via this command in WLST planPath = get('/AppDeployments/DbAdapter/PlanPath')
but the issue is i dont get the complete path insted i get something like this 'osb_cluster/plans/DBAdapter/DbAdapterPlan.xml'
when i run the same script in single node environment , the script executes fine and update the plan path . Also i get the complete plan path url like this '/u9000/app/oracle/product/fmw/osb_11.1.1.5.0/Oracle_OSB/soa/connectors/DBAdapter/DBAdapterplan.xml'
is there any issue with my clustered environment . Any help is appreciated !
Thanks ,
karthik

Just one more question , even though config.xml has invalid plan path when i see the plan path from AdminConsole ->Deployments->DbAdapter , it is showing the right url there. Just wanted to understand how this plan path is referenced.I believe it can be referenced as a relative path form by weblogic... Not sure, but may be relative to domain root...

Customer Standard Dataloader issue

Hello,
I am trying to use the Dataloader to load the customer profile. I am not sure how to navigate sideways through the various tabs. For instance, I want to navigate from the top block to the 'Classification' tab so that I can populate the Profile Class.
Thank you
SK

I am trying to use the Dataloader to load the customer profile. I am not sure how to navigate sideways through the various tabs. For instance, I want to navigate from the top block to the 'Classification' tab so that I can populate the Profile Class.Do you mean DataLoad? If yes, please see the documentation -- http://www.dataload.com/help/index.htm
Thanks,
Hussein

BW - APO Datamart datasource migration issue

Hi,
Question : Can we migrate datasources exported as datamart from APO-DP system into BW, from 3.x to 7.0 or does it have to be a 3.x datasource with transfer rules, TS , update rules etc ...
1) I know we cannot migrate data marts with 8* or //8 but this datamart is replicated from our APO-DP system and begins with 9*.
Thanks .
HS

Hi Geetanjali,
Thanks for the reply.
My problem is that I am getting error message "No transfer structure available for infosource 9* in source system" when I run the infopkg to load in PSA ( which is default for 7.0 datasources).
This is the dataflow l I wanted to have which replaces old model as shown :
NEW 7.0 dataflow : Datasource -->infopkg --> psa --> dtp -->transformation --> cubes ( same source feeds 3 cubes ) .
OLD 3.x dataflow : DS >Infosource>Transfer rules--> infopkg --> update rules --> cubes.
Thanks .
HS

DataSource Connection Issues w/Authentication Sample App

Hi,
I'm trying to accomplish database provided authentication as described in this how to article:
http://www.oracle.com/technology/products/jdev/howtos/1013/oc4jjaas/oc4j_jaas_login_module.htm
I have enabled logging for the oc4j security module in the j2ee_logging.xml file for troubleshooting, and have been inspecting the log entries returned whilst attempting to login.
It seems my datasource is not connecting, and i can't work out why not.
The relevent log information is here :
14/08/2007 13:33:40 oracle.security.jazn.login.module.db.DBTableOraDataSourceLoginModule performDbAuthentication
FINE: [DBTableOraDataSourceLoginModule]User Han Solo not authenticated: username or password mismatch
14/08/2007 13:33:40 oracle.security.jazn.login.module.db.DBTableOraDataSourceLoginModule performDbAuthentication
FINE: [DBTableOraDataSourceLoginModule]Error: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
//oratestsvr:1521/BIDB
oratestsvr is the correct server name, and BIDB is the correct service name, i can successfully connect to this database via sqlplus.
The datasource definition in the embedded oc4j data_sources.xml file is:
<native-data-source name="OracleNativeDS" jndi-name="jdbc/OracleNativeDS" data-source-class="oracle.jdbc.pool.OracleDataSource" user="TIMESHEET_SYS" password="->DataBase_User_zdvhhyJa_CMhuW4MPzpmFZRhjNO9WQeI" url="jdbc:oracle:thin:@//oratestsvr:1521/BIDB" login-timeout="1000">
</native-data-source>
However changes to this file are not reflected in the log errors, i can alter the log response by changing the datasource definition found in 'embedded OC4j Server preferences.. -> Current Workspace -> Data Sources -> OracleNativeDS (appears to be the same definition)
I am unsure how to proceed as i can't find anything wrong with my datasource configuration, yet i keep getting the same connection error in the log.
Any idea's?
Thanks

Ah, fixed it.. the // slashes weren't needed.
url="jdbc:oracle:thin:@oratestsvr:1521:bidb"

Crystal 10 set datasource location issue

I am getting hung up when trying to set a datasource location in Crystal 10. I have tried uninstalling and reinstalling the software. Any ideas?

Hi,
Try with this:
1. Reduce the 'Hardware acceleration' setting in Microsoft Windows.
2. To access the 'Hardware acceleration' setting in Microsoft Windows:
Click Start > Settings > Control Panel > System > Display > Settings > Advanced > Troubleshooting.
There are typically six possible settings for 'Hardware acceleration': from 'None' to 'Full'.
If you are using Dual monitor run the CR application on primary monitor cause Dual monitor is not tested with Crystal Reports.
Regards,
Shweta

CRM DataSource having Issue in BW

HI Guys,
I am having problems with CRM7.0 DataSources (0CRM_SRV_CODES, 0CRM_SRV_PROCESS_H). Actually whats happening is when i check these DataSources in rsa3 in the CRM system I can see the data but when I try to run InfoPakage(initial) or delta on the BW side I m getting nothing, I have already checked and configured everything on source system(CRM7.0) and I also apply SAP note 692195 as well, but still could not able to get any data in the BW side. I also done replication on BW side and can also see both DataSources active in BWA7.
Kindly give me some suggestions to solve this problem, I will be very grateful.
Zeeshan

Hi Durgesh,
Thanks for your reply. Have checked all authorization. They are same on both side i.e., BW QA and CRM QA respective clients.
Another thing, I would like to bring into your knowledge that I am running InfoPackage manually on QA, not scheduling but for manually run, data not even fetched. Nor through scheduling.
Any suggestions would be highly appreciated as today is the last day of our QA readiness. Have to load CRM data at any cost.
Thanks.

Datasource pool issues in weblogic

Frequently,I am coming accross this error in my weblogic server log:Any pointers on how to resolve this? any help on this
Adminlog:
<Oct 15, 2013 12:11:35 PM GMT> <Info> <JDBC> <EPGCRMITG1> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-1d42ac6e:1419df56d93:-8000-0000000000003906> <1381839095305> <BEA-001128> <Connection for pool "LifeCycleDataSource-rac0" has been closed.>
####<Oct 15, 2013 12:11:35 PM GMT> <Info> <JDBC> <EPGCRMITG1> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-1d42ac6e:1419df56d93:-8000-0000000000003906> <1381839095354> <BEA-001128> <Connection for pool "LifeCycleDataSource-rac0" has been closed.>
####<Oct 15, 2013 12:11:35 PM GMT> <Info> <JDBC> <EPGCRMITG1> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-1d42ac6e:1419df56d93:-8000-0000000000003906> <1381839095356> <BEA-001128> <Connection for pool "LifeCycleDataSource-rac0" has been closed.>
####<Oct 15, 2013 12:12:36 PM GMT> <Warning> <JDBC> <EPGCRMITG1> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-1d42ac6e:1419df56d93:-8000-0000000000003906> <1381839156379> <BEA-001129> <Received exception while creating connection for pool "LifeCycleDataSource-rac0": IO Error: The Network Adapter could not establish the connection.>
####<Oct 15, 2013 12:12:36 PM GMT> <Info> <JDBC> <EPGCRMITG1> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-1d42ac6e:1419df56d93:-8000-0000000000003906> <1381839156381> <BEA-001156> <Stack trace associated with message 001129 follows:
java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection
    at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:482)
    at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:678)
    at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:238)
    at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:34)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:567)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:357)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:453)
    at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:1841)
    at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1741)
    at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1647)
    at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1636)
    at weblogic.common.resourcepool.ResourcePoolImpl.testUnusedResources(ResourcePoolImpl.java:2088)
    at weblogic.common.resourcepool.ResourcePoolImpl.access$1600(ResourcePoolImpl.java:41)
    at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2769)
    at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: oracle.net.ns.NetException: The Network Adapter could not establish the connection
    at oracle.net.nt.ConnStrategy.execute(ConnStrategy.java:398)
    at oracle.net.resolver.AddrResolution.resolveAndExecute(AddrResolution.java:438)
    at oracle.net.ns.NSProtocol.establishConnection(NSProtocol.java:711)
    at oracle.net.ns.NSProtocol.connect(NSProtocol.java:257)
    at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1222)
    at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:330)
    at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:678)
    at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:238)
    at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:34)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:567)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:357)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:453)
    at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:1841)
    at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1741)
    at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1647)
    at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1636)
    at weblogic.common.resourcepool.ResourcePoolImpl.testUnusedResources(ResourcePoolImpl.java:2088)
    at weblogic.common.resourcepool.ResourcePoolImpl.access$1600(ResourcePoolImpl.java:41)
    at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2769)
    at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: java.net.SocketTimeoutException: connect timed out
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
    at java.net.Socket.connect(Socket.java:579)
    at oracle.net.nt.MetricsEnabledSocket.connect(TcpNTAdapter.java:631)
    at oracle.net.nt.TcpNTAdapter.connect(TcpNTAdapter.java:164)
SOA Log:
<BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "ecoxproduct" failed with exception: "oracle.jdbc.xa.OracleXAException".>
####<Oct 16, 2013 3:53:48 PM GMT> <Info> <JDBC> <EPGCRMITG1> <soa_server1> <[ACTIVE] ExecuteThread: '62' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-3ffef6c2:141a29a60f1:-8000-00000000000ff280> <1381938828168> <BEA-001128> <Connection for pool "ecoxproduct" has been closed.>
####<Oct 16, 2013 3:53:48 PM GMT> <Warning> <JTA> <EPGCRMITG1> <soa_server1> <[ACTIVE] ExecuteThread: '62' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-3ffef6c2:141a29a60f1:-8000-00000000000ff280> <1381938828181> <BEA-110484> <The JTA health state has changed from HEALTH_OK to HEALTH_WARN with reason codes: Resource ecoxproduct_base_domain declared unhealthy.>
####<Oct 16, 2013 3:53:48 PM GMT> <Info> <JDBC> <EPGCRMITG1> <soa_server1> <[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-3ffef6c2:141a29a60f1:-8000-00000000000ff282> <1381938828653> <BEA-001128> <Connection for pool "AIAJMSDS-rac0" has been closed.>
####<Oct 16, 2013 3:53:54 PM GMT> <Error> <JDBC> <EPGCRMITG1> <soa_server1> <FabricScheduler_QuartzSchedulerThread> <<anonymous>> <> <0000K6YagLhE^M4pzSXBiW1ILeuk000002> <1381938834492> <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "SOALocalTxDataSource" failed with exception: "java.sql.SQLRecoverableException: IO Error: Connection reset".>
####<Oct 16, 2013 3:53:54 PM GMT> <Info> <JDBC> <EPGCRMITG1> <soa_server1> <FabricScheduler_QuartzSchedulerThread> <<anonymous>> <> <0000K6YagLhE^M4pzSXBiW1ILeuk000002> <1381938834493> <BEA-001128> <Connection for pool "SOALocalTxDataSource" has been closed.>
####<Oct 16, 2013 3:53:58 PM GMT> <Error> <JDBC> <EPGCRMITG1> <soa_server1> <MDSPollingThread-[soa-infra, jdbc/mds/MDS_LocalTxDataSource]> <<anonymous>> <> <0000K6YagLhE^M4pzSXBiW1ILeuk000002> <1381938838392> <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "mds-soa" failed with exception: "java.sql.SQLRecoverableException: IO Error: Connection reset".>
####<Oct 16, 2013 3:53:58 PM GMT> <Info> <JDBC> <EPGCRMITG1> <soa_server1> <MDSPollingThread-[soa-infra, jdbc/mds/MDS_LocalTxDataSource]> <<anonymous>> <> <0000K6YagLhE^M4pzSXBiW1ILeuk000002> <1381938838393> <BEA-001128> <Connection for pool "mds-soa" has been closed.>
####<Oct 16, 2013 3:53:58 PM GMT> <Error> <JDBC> <EPGCRMITG1> <soa_server1> <MDSPollingThread-[owsm, jdbc/mds/owsm]> <<anonymous>> <> <0000K6YagLhE^M4pzSXBiW1ILeuk000002> <1381938838393> <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "mds-owsm" failed with exception: "java.sql.SQLRecoverableException: IO Error: Connection reset".>
####<Oct 16, 2013 3:53:58 PM GMT> <Info> <JDBC> <EPGCRMITG1> <soa_server1> <MDSPollingThread-[owsm, jdbc/mds/owsm]> <<anonymous>> <> <0000K6YagLhE^M4pzSXBiW1ILeuk000002> <1381938838394> <BEA-001128> <Connection for pool "mds-owsm" has been closed.>
####<Oct 16, 2013 3:53:58 PM GMT> <Info> <JDBC> <EPGCRMITG1> <soa_server1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-3ffef6c2:141a29a60f1:-8000-00000000000ff284> <1381938838414> <BEA-001128> <Connection for pool "AIAJMSDS-rac0" has been closed.>
####<Oct 16, 2013 3:54:04 PM GMT> <Warning> <JDBC> <EPGCRMITG1> <soa_server1> <FabricScheduler_QuartzSchedulerThread> <<anonymous>> <> <0000K6YagLhE^M4pzSXBiW1ILeuk000002> <1381938844505> <BEA-001129> <Received exception while creating connection for pool "SOALocalTxDataSource": IO Error: The Network Adapter could not establish the connection.>
####<Oct 16, 2013 3:54:04 PM GMT> <Info> <JDBC> <EPGCRMITG1> <soa_server1> <FabricScheduler_QuartzSchedulerThread> <<anonymous>> <> <0000K6YagLhE^M4pzSXBiW1ILeuk000002> <1381938844506> <BEA-001156> <Stack trace associated with message 001129 follows:
This my connection pool parameters for "ecoxproduct":
Initial Capacity:1
Maximum Capacity:5
Minimun Capacity:1
Statement Cache Type:LRU
Statement Cache Size: 10
Test Reserved Connections: uncheked
Test Frequnct:120
Test Table Name:SQL SELECT 1 FROM DUAL
Seconds to trust ldle Poolconnection :10
Shrink Frequency:900 SEC
Connection cretion retry Frequncy   0
Inactiv Connection time out:0
Mixmunwaiting connetion:2147483647
Connection Reserve Timeout: 10 SEC
Thanku you
ram

Hi,
The database going down is most unlikely to happen,
Things to check here by DBA:-
1) If the SERVICE_NAME used in the JDBC string - This service_name might be intermittently unregistering itself from database listener
2) If the SID is used in the JDBC string - Check if you have used proper SID name in case of RAC
3) if SCAN_NAME is used - The scan_name also intermittently breaks the client connection.

2LIS_02_SCL Datasource dataload issue

Similar Messages

Maybe you are looking for