HELP!! SQL Server SP3 breaks JDBC driver connections

Anybody ran into this problem? Just installed Sql Server 2k SP3 and all my jdbc calls fail. JDBC driver for Microsoft works find.

Have you find a solution to your problem. I ran into the same problem. One of my
client still use WLS 5.1 and has the problem as soon SP3 applied to MSSQL 2000/DBMS.
I create a new accounnt in DBMS and it's not working. I tried several different
type 4 JDBC drivers(MS, DataDirect...) and here is what I get, HELP!!!!!:
Thu Jan 30 17:40:08 CST 2003:<I> <JDBC Pool> Sleeping in createResource()
Thu Jan 30 17:40:09 CST 2003:<E> <JDBC Pool> Failed to create connection pool
"E
dSoftSQLPool"
weblogic.common.ResourceException: weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(String.java:511)
at com.microsoft.jdbc.base.BaseURLParser.parseURLSubProtocol(Unknown Sou
rce)
at com.microsoft.jdbc.base.BaseURLParser.parse(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:146)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:108)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
cator.java:792)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
ava:416)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:330)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:141)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:255)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java
:62)
"Jeff Reester" <[email protected]> wrote:
>
Joseph Weinstein <[email protected]> wrote:
nslsk wrote:
Anybody ran into this problem? Just installed Sql Server 2k SP3 andall my jdbc calls fail. JDBC driver for Microsoft works find.
Show us the failure info (the whole stacktrace). Are you saying that
the weblogic jdbc driver
fails, but the jdbc driver from MS works?
Joe
We are seeing the same. Upgraded MS SQL Server 2000 SP2 to SP3. We
cannot create
the connection pool. We are running Weblogic Server 5.1.0 Service Pack
11. With
the Weblogic mssqlserver4v70 SP11 JDBC drivers.
[exec] Sun Jan 26 16:08:31 EST 2003:<I> <JDBC Pool> Creating connection
pool
odbcPool with:
[exec] aclName=weblogic.jdbc.connectionPool.odbcPool maxCapacity=200
url=jdbc20:weblogic:mssqlserver4
allowShrinking=true poolName=odbcPool refreshTestMinutes=6 testConnsOnReserve=true
props=user=xxxxxx;server=Metaprise_UnitTest_415@
VUABCDEFG:1433;capacityIncrement=1 testTable=ec_webconnect_check shrinkPeriodMins=12
initialCapacity=4 loginDelaySecs=1 driver=MSSQLDriver20
[exec] Sun Jan 26 16:08:31 EST 2003:<I> <JDBC Pool odbcPool> pool
odbcPool
will be tested at a 6 minute interval.
[exec] Delaying 1 seconds before making a odbcPool pool connection.
[exec] Sun Jan 26 16:08:32 EST 2003:<I> <JDBC Pool> Sleeping in
createResource()
[exec] Sun Jan 26 16:08:33 EST 2003:<E> <JDBC Pool> Failed to create
connection
pool "odbcPool"
[exec] weblogic.common.ResourceException: weblogic.common.ResourceException:
[exec] Could not create pool connection. The DBMS driver exception
was:
[exec] java.sql.SQLException: I/O exception while talking to the
server,
java.io.EOFException Unable to connect, please check your server's version
and
availability.
[exec] at weblogic.jdbcbase.mssqlserver4.TdsStatement.microsoftLogin(TdsStatement.java:2830)
[exec] at weblogic.jdbc20.mssqlserver4.MicrosoftConnection.beginLogin(MicrosoftConnection.java:42)
[exec] at weblogic.jdbcbase.mssqlserver4.TdsConnection.login(TdsConnection.java:64)
[exec] at weblogic.jdbc20.mssqlserver4.MicrosoftConnection.login(MicrosoftConnection.java:53)
[exec] at weblogic.jdbcbase.mssqlserver4.BaseConnection.prepareConnection(BaseConnection.java:186)
[exec] at weblogic.jdbc20.mssqlserver4.Driver.newConnection(Driver.java:32)
[exec] at weblogic.jdbcbase.mssqlserver4.ConnectDriver.connect(ConnectDriver.java:148)
[exec] at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:164)
[exec] at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:123)
[exec] at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:840)
[exec] at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:416)
[exec] at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:330)
[exec] at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:106)
[exec] at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:220)
[exec] at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
[exec] at java.lang.reflect.Method.invoke(Native Method)
[exec] at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
[exec] at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
[exec] at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
[exec]
[exec] at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:172)
[exec] at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:123)
[exec] at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:840)
[exec] at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:416)
[exec] at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:330)
[exec] at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:106)
[exec] at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:220)
[exec] at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
[exec] at java.lang.reflect.Method.invoke(Native Method)
[exec] at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
[exec] at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
[exec] at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
[exec]
[exec] at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:140)
[exec] at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:840)
[exec] at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:416)
[exec] at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:330)
[exec] at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:106)
[exec] at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:220)
[exec] at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
[exec] at java.lang.reflect.Method.invoke(Native Method)
[exec] at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
[exec] at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
[exec] at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
[exec]
Jeff

Similar Messages

MS SQL Server 2000 and JDBC Driver Problem

I was wondering if you could help me. I installed Java 1.4.1 on my Win2K machine along with MS SQL Server 2000 JDBC Service Pack 1 drivers.
The drivers and JDK installed perfectly and I properly set my class path. Yet everytime I try to execute my code I get the: java.lang.ClassNotFoundException: com.microsoft.jdbc.sqlserver.SQLServerDriver error.
Any idea why? Is it posisible that the JDBC drivers are not comaptible with Java 1.4? I also installed 1.3.1 and I get the same issue. Let me know if you have any insisghts. Much thanks.
[email protected]

Those drivers are perfectly compatible with JDK 1.4.1. I've used them successfully.
CNF Exception ALWAYS means that the class loader can't find the JAR in the CLASSPATH. You said you "properly" set your CLASSPATH. Am I right in assuming that you mean a Win2K environment variable?
I think that's a bad idea. I don't have one on my machines at all.
I always set the CLASSPATH myself when I compile and run an app, to make sure that I always have exactly what I need.
If you're running Tomcat, it doesn't even look at the system CLASSPATH as far as I know. If you're using this in a Web app, but those JARs in your WEB-INF/lib directory and deploy your stuff as a WAR file. Tomcat will find it in the CLASSPATH for sure then.
Let me know if either of those suggestions hits the mark. If not, send more info and I'll try again. - MOD

How to connect Sql Server 2000 using JDBC ODBC Driver

How to connect Sql Server 2000 using JDBC ODBC Driver ?
plz Send Syntax.
thanks

In SQL Server 2000 the driver class is com.microsoft.jdbc.sqlserver.SQLServerDriver
The connection URL for the default SQL Server 2000 database is jdbc:sqlserver://localhost:1433
Class.forName(
"com.microsoft.sqlserver.jdbc.
SQLServerDriver");
String url =
"jdbc:sqlserver://localhost:1433";
Connection conn = DriverManager.
getConnection(
url, "sa", "sqlserver");

Trouble connecting to the Microsoft SQL Server 2005 using JDBC Connection

Hi,
I am unable to connect to the Microsoft SQL Server 2005 using JDBC Connection. Kindly tell me steps to connect to the SQL Server using JDBC. The error message that I am getting while creating a data source is :
java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during start of application "sap.com/JDBCConnector_KedDS.xml". [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 13169050:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "KedDS".
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:4761)
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 ManagedConnectionFactoryImpl.
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:78)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1779)
... 42 more
Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
Found in negative cache
------------------------- Loader Info -------------------------
ClassLoader name: [library:KedDriver]
Parent loader name: [Frame ClassLoader]
No references !
Resources:
E:\usr\sap\J2E\JC01\j2ee\cluster\server0\bin\ext\KedDriver\sqljdbc.jar
E:\usr\sap\J2E\JC01\j2ee\cluster\server0\bin\core_lib\opensqlport.jar
Loading model: {parent,local,references}
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360)
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:74)
... 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 13169050:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "KedDS".
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:4761)
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 ManagedConnectionFactoryImpl.
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:78)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1779)
... 42 more
Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
Found in negative cache
------------------------- Loader Info -------------------------
ClassLoader name: [library:KedDriver]
Parent loader name: [Frame ClassLoader]
No references !
Resources:
E:\usr\sap\J2E\JC01\j2ee\cluster\server0\bin\ext\KedDriver\sqljdbc.jar
E:\usr\sap\J2E\JC01\j2ee\cluster\server0\bin\core_lib\opensqlport.jar
Loading model: {parent,local,references}
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360)
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:74)
... 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:4761)
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:1011)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
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:1296)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
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:1296)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
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:1267)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
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)

i'm using jcreator pro
jdk i.6
mssql server 2005
and downloaded the jdbc driver( i noticed that the msutil.jar and msbase.jar are not in the folder avalable on microsoft site Microsoft SQL Server 2005 JDBC Driver so i installed
Microsoft SQL Server 2000 Driver for JDBC 1st and just changed the jqljdb.jar file with the one available in Microsoft SQL Server 2005 JDBC Driver )
and set the path of the CLASSPATH to a folder which name has no spaces
and tried Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
and Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
and tried compiling and running with command prompt
and still have the same exception which occurs at runtime
"An exception has occured: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver"
i really need help

Urgent OmniPortlet JDBC SQL Server - Unable to establish the connection

Not sure if this is the correct forum but as there is another JDBC question regarding portlets in this forum I have to give this a try as it is URGENT I get this solved.
Please see my post in the Portal General Forum
OmniPortlet DataDirect JDBC SQL Server - Unable to establish the connection
Thanks!

Not sure if this is the correct forum but as there is another JDBC question regarding portlets in this forum I have to give this a try as it is URGENT I get this solved.
Please see my post in the Portal General Forum
OmniPortlet DataDirect JDBC SQL Server - Unable to establish the connection
Thanks!

Connecting to MS SQL Server with JTDS DBC Driver version 11.1.58.17

The version 1.5.4 supposed to allow you to connect to SQL Servers (JTDS DBC Driver version 11.1.58.17) but in fact you cannot. That is, even to SQL Express2005.
The earlier JTDS could in fact supported connecting to SQL Server 2005 as well as SQL Express as I wrote in my earlier article,
http://www.packtpub.com/article/oracle-sql-developer-tool-1.5-sql-server-2005
The new driver does not enable the connection with similar syntax while connecting to SQL Server 2005. Is it a problem with the driver?

Thanks a lot.
That appears to be a good link. Why does this process have to be so convoluted? First of all the user is directed to something that is not going to work (I mean the Oracle's JTDS 11.1.58.17 stuff) and to use Source Forge you need to do further work. Does not make sense from the usability point of view, does it?
Anyway is SQL Server 2008 is supported in this version?

Java.sql.SQLException: Error accessing jdbc driver

Hi,
We are using WebLogic Server 7.0 as Application Server.
We now create a connection pool named regPool and
a Tx datasource named regDS.
When we get the connection from the datasource, exception occurred.
java.sql.SQLException: Error accessing jdbc driver: driverURL =
jdbc:weblogic:pool:regPool, props = {enableTwoPhaseCommit=false,
jdbcTxDataSource=true, connectionPoolID=regPool}
at
weblogic.jdbc.jts.Driver.wrapAndThrowSQLException(Driver.java:323)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:377)
at weblogic.jdbc.jts.Driver.connect(Driver.java:129)
at
weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java
:265)
So I guess that why we can't use CMP for finding data. Here is the error when we call the finder.
javax.ejb.FinderException: Exception in findAllEmr while preparing or
executing statement: 'null'
java.sql.SQLException: Cannot obtain connection after 30 seconds. ,
Exception = Access not allowed
java.sql.SQLException: Cannot obtain connection after 30 seconds. ,
Exception = Access not allowed
at
weblogic.jdbc.jts.Connection.wrapAndThrowSQLException(Connection.java:694)
According to the exception message, it looks
like the connection fail between WLS and Oracle 9.2.
Here is a scenario I think you should need to know.
I change the table-name in the weblogic-cmp-rdbms-jar.xml
to a name that doesn't exist in the database.
Then, re-package the EJB, copy it to server and restart the server.
A exception occurred that says the table doesn't exist.
So, in this case, it looks like the datasource works and
connection is fine.
Any recommendation will be appreciated.
Jimmy Chang

Hi!
I am a default user to the databse server. I connect to the database with '\' as the username and blank passoword(I mean with Network authentication may be).When I am trying to create connection using
con = DriverManager.getConnection("jdbc:oracle:thin:@DRACINAL2:BSAJ", "/","" )
it gives me followint error
ava.sql.SQLException: Null user or password not supported in THIN driver
     void oracle.jdbc.dbaccess.DBError.throwSqlException(java.lang.String, java.lang.String, int)
     void oracle.jdbc.dbaccess.DBError.throwSqlException(int, java.lang.Object)
     void oracle.jdbc.dbaccess.DBError.check_error(int)
     oracle.jdbc.dbaccess.DBConversion oracle.jdbc.ttc7.TTC7Protocol.logon(java.lang.String, java.lang.String, java.lang.String, java.util.Properties)
     void oracle.jdbc.driver.OracleConnection.<init>(oracle.jdbc.dbaccess.DBAccess, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.util.Properties)
     java.sql.Connection oracle.jdbc.driver.OracleDriver.getConnectionInstance(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.util.Properties)
     java.sql.Connection oracle.jdbc.driver.OracleDriver.connect(java.lang.String, java.util.Properties)
     java.sql.Connection java.sql.DriverManager.getConnection(java.lang.String, java.util.Properties, java.lang.ClassLoader)
     java.sql.Connection java.sql.DriverManager.getConnection(java.lang.String, java.lang.String, java.lang.String)
     void textPack.GenTextFile.main(java.lang.String[])
How should I go about it?
Thanks for your help.
-Sreekanth Varidhireddy

Java.sql.SQLException: Cannot load JDBC driver class 'null'

Hi,
I am a beginner of using jdbc, i use the tomcat4.1.x, mysql3.23.54 and it's jdbc driver 2.0.14. I place the drive <in jar file> in tomcat/commons/lib and configure the server.xml, web.xml and some testing coding. But there are some error like the following:
java.sql.SQLException: Cannot load JDBC driver class 'null'
     at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:529)
     at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:312)
     at foo.DBTest.init(DBTest.java:18)
     at org.apache.jsp.test_jsp._jspService(test_jsp.java:48)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:136)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:204)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
of course its some of the error code and there are more.
Why I have this problems and how can I fix it? Can someone help me??
Thanks,
Tong
I place my test.jsp at tomcat/webapps/DBTest and DBTest.java at tomcat/webapps/DBTest/WEB-INF/classes/foo
additional of the tomcat/conf/server.xml
<Resource name="TestDB" auth="Container" type="javax.sql.DataSource" description="MySQL TestDB"/>
<ResourceParams name="TestDB">
<parameter><name>factory</name>
<value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
</parameter>
<parameter><name>maxActive</name><value>10</value></parameter>
<parameter><name>maxIdle</name><value>1</value></parameter>
<parameter><name>maxWait</name><value>10000</value></parameter>
<parameter><name>username</name><value>javauser</value></parameter>
<parameter><name>password</name><value>javadude</value></parameter>
<parameter>
<name>driverClassName</name>
<value>org.gjt.mm.mysql.Driver</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:mysql://localhost:3306/javatest?autoReconnect=true</value>
</parameter>
</ResourceParams>
tomcat/webapps/DBTest/WEB-INF/web.xml :
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app PUBLIC
"-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<description>MySQL Test App</description>
</web-app>

Post the part of your code that loads the driver and connects. My guess is you are using a variable for the name of the driver and the variable has not been set to anything(intially set to null).
Thanks
Cardwell

Error oracle.sql.* and oracle.jdbc.driver.* not found when using oracle as a database

I am using oracle as database and weblogic 4.5. I have copied the classes12.zip file in lib directory of weblogic. I am getting the error that oracle.sql.* and oracle.jdbc.driver.* not found when i am importing these packages in a jsp file. what i need to do to import oracle driver packages?I put it in the classpath also.
Please Advice!
Thanks in advance
AnuPama

Hi Anupama,
First of all I would be surprised if you would not like to use the connection pooling feature of weblogic (in which case you might not be needing the import the classes directly), and would like to open direct connections to your database. Anyways for doing that I would recommend you to check out the readme doc that ships
along with the jdbc oracle (classes12.zip etc). I am giving an excerpt over here:
These are a few simple things that you should do in your JDBC program:
1. Import the necessary JDBC classes in your programs that use JDBC.
For example:
import java.sql.*;
import java.math.*;
2. Register the Oracle driver before before calling other JDBC APIs.
(This is not needed if you are using the JDBC Server-side Internal
Driver because registration is done automatically in the server.)
To register the Oracle driver, make sure the following statement
is executed at least once in your Java session:
DriverManager.registerDriver(
new oracle.jdbc.driver.OracleDriver());
3. Open a connection to the database with the getConnection call.
Different connection URLs should be used for different JDBC
drivers. The following examples demonstrate the different URLs.
For the JDBC OCI8 Driver:
Connection conn = DriverManager.getConnection(
"jdbc:oracle:oci8:@<database>",
"scott", "tiger");
where <database> is either an entry in tnsnames.ora or a SQL*net
name-value pair.
For the JDBC Thin Driver, or Server-side Thin Driver:
Connection conn = DriverManager.getConnection(
"jdbc:oracle:thin:@<database>",
"scott", "tiger");
where <database> is either a string of the form
<host>:<port>:<sid> or a SQL*net name-value pair.
For the JDBC Server-side Internal Driver:
Connection conn = DriverManager.getConnection(
"jdbc:oracle:kprb:");
Note that the trailing ':' character is necessary. When you use
the Server-side Internal Driver, you always connect to the
database you are executing in. You can also do this:
Connection conn
= new oracle.jdbc.driver.OracleDriver().defaultConnection();
Hope this helps,
Thanks,
Anupama wrote:
I am using oracle as database and weblogic 4.5. I have copied the classes12.zip file in lib directory of weblogic. I am getting the error that oracle.sql.* and oracle.jdbc.driver.* not found when i am importing these packages in a jsp file. what i need to do to import oracle driver packages?I put it in the classpath also.
Please Advice!
Thanks in advance
AnuPama--
Apurb Kumar

Java.sql.SQLException: Cannot load JDBC driver

THis topic has been discussed many many times but I still not able to connect to Oracle 8i from my servlet using Tomcat 4.1.12 on hp-ux and java1.3
I always got: java.sql.SQLException: Cannot load JDBC driver class 'null'
In server.xml:
<Context Path="/MyApp" docBase="MyApp" debug="0" reloadable="true" >
<Resource name="jdbc/ora" auth="Container" type="javax.sql.DataSource"/> <ResourceParams name="jdbc/ora" >
<parameter>
<name>username</name>
<value>myname</value>
</parameter>
<parameter> <name>password</name>
<value>mypassword</value>
</parameter>
<parameter> <name>driverClassName</name>
<value>oracle.jdbc.driver.OracleDriver</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:oracle:thin:@myhostname:1521:ora</value>
</parameter> </ResourceParams>
</Context>
In MyApp/WEB-INF/web.xml:
<resource-ref>
<res-ref-name>jdbc/ora</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
The Oracle jdbc jar file classes12.jar is under common/lib in Tomcat's home. read Permission is there.
In the servlet:
init(ServletConfig config):
Context init = new InitialContext();
Context ctx = (Context) init.lookup("java:comp/env");
dataSource = (DataSource) ctx.lookup("jdbc/acdb");
doPost(..)
the error occured at :
synchronized (dataSource){
con = dataSource.getConnection();}
Thanks in advance!

Everything looks correct to me, except for one thing.
In your web.xml you have this:
<res-ref-name>jdbc/ora</res-ref-name> In your server.xml, you have this tag, which matches your web.xml:
<ResourceParams name="jdbc/ora" > But in your Java code, you've got this:
dataSource = (DataSource) ctx.lookup("jdbc/acdb"); When I've successfully set up a Web app data source, all three names had to agree. You either need to change your Java lookup name to "jdbc/ora" or change the web.xml and server.xml to "jdbc/acdb".
See if that does it. Everything else sounds correct to me. - MOD

MS SQL Server 7 thru JDBC:ODBC bridge

Hi,
I am trying to access MS SQL server 7 thru JDBC ODBC bridge. I am finding my varchar data is being truncated to 255 characters. Any help on this would be appreciated.

Any body know of a good type 4 jdbc driver for SQL
Server 7. There is one for SQL server 2000
downloadable from micrsoft site, but does it work for
sql server 7 too ?Older betas of this driver suported SQL Server 7, but I believe the plan is to specifically remove that capability in its final release.
My biased opinion would be to try the driver from DataDirect. http://www.ddtek.com Its their driver (an older version) that Microsoft has licensed for MS SQl 2000.
Getting it from DataDirect has a couple obvious advantages:
1. Its a later, more stable, better performing version
2. It will continue to Support MS SQL 7
3. It's suported by 24/7 phone,email and web tech support.
4. And, early this week, you should be able to get the latest 3.0 release which promises to be even more robust, in addition to conforming to the new specs.
5. its not free, but then again- you get what you pay for...

Java.sql.SQLException:[SAP_NWMss][SQLServer JDBC Driver][SQLServer]

Hi,
When i am tring to open UWL iview from my portal. I am getting following exception.
java.sql.SQLException:[SAP_NWMss][SQLServer JDBC Driver][SQLServer]
But no where i am connecting to SQL database in my portal. Please help me in this context.
Regards,
Davood.

Hi Uday,
I created an instance SQL01 for DB. I see this instance as running. The TCP/IP port of this instance is 1433.
When I am trying to install NW 7.0 from install.bat C:\usr\sap\F48\install, I get this error. I tried connecting to the database directly (using Query Analyzer) and I am able to login with the user id and password provided in the log file.
Please let me know how to proceed.
Regards
Nikhil

MS SQL Server Stored Procedure - JDBC Receiver Adapter

Hi,
I am calling a stored procedure in MS SQL Server using the JDBC Receiver Adapter. The stored procedure takes 1 input parameter which is a VARCHAR field. The stored procedure's input parameter and the input parameter are identical. My target structure looks like:-
<STATEMENT>
<storedProcedureName action="EXECUTE">
<TABLE>SP_REPROCESS</TABLE>
<input1 isInput="true" type="VARCHAR">1</input1>
</storedProcedureName>
</STATEMENT>
I am getting the following error:-
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'SP_REPROCESS' (structure 'STATEMENT'): com.microsoft.sqlserver.jdbc.SQLServerException: String or binary data would be truncated.
Any suggestions.
Thanks.
Krishnan
Edited by: Krishnan on Jul 17, 2008 7:07 AM
Edited by: Krishnan on Jul 17, 2008 7:07 AM
Edited by: Krishnan on Jul 17, 2008 7:48 AM

hi,
can anyone help me to fix this issue.
In MONI, i am able to see the output xml as :-
<?xml version="1.0" encoding="UTF-8"?>
<ns0:REPROCESS_DATA_MT xmlns:ns0="http://abc.com/db/integration">
<STATEMENT>
<storedProcedureName action="EXECUTE">
<TABLE>SP_REPROCESS</TABLE>
<input1 isInput="true" type="VARCHAR">1</input1>
</storedProcedureName>
</STATEMENT>
</ns0:REPROCESS_DATA_MT>
in the communication channel monitoring --> in the JDBC receiver channel, I am getting the following error:-
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'SP_REPROCESS' (structure 'STATEMENT'): com.microsoft.sqlserver.jdbc.SQLServerException: String or binary data would be truncated.
thanks.
krishnan

How to insert chinese data into MS SQL Server 2000 through JDBC

I am trying to insert chinese data into MS SQL server 2000 using JDBC. how to do this?
can anybody help me.
thanx.

I am trying to insert chinese data into MS SQL server 2000 using JDBC. how to do this?
can anybody help me.
thanx.

MS SQL Server Analysis Services (SSAS) OLAP Connection - Dimension descriptions

Hello,
We are trying to create some reports on BO 4.0 on top of BPC 10 MS information.
In order to overcome some issues related to standard connector between BO and BPC (XMLA Planning and consolidation 10 for Microsoft platform), we created a new connection based on discussion MS SQL Server Analysis Services (SSAS) OLAP Connection - Business Intelligence (BusinessObjects) - SCN Wiki
However we have a major issue with this approach. We cannot see on BO dimension member descriptions.
Is there anything that we missed?
Could you help?
Regards,
Vitor Ramalho

Bill,
So, what you need is a model like SQL Server failover cluster instances. (before sql server 2012)
In SQL Server 2012, AlwaysOn replaces SQL Server failover cluster, and it has been seperated to
AlwaysOn Failover Cluster Instances (SQL Server) and
AlwaysOn Availability Groups (SQL Server).
Since your requirement is not in database level, I think the best option is to use AlwaysOn Failover Cluster Instances (SQL Server).
As part of the SQL Server AlwaysOn offering, AlwaysOn Failover Cluster Instances leverages Windows Server Failover Clustering (WSFC) functionality to provide local high availability through redundancy at the server-instance level—a
failover cluster instance (FCI). An FCI is a single instance of SQL Server that is installed across Windows Server Failover Clustering (WSFC) nodes and, possibly, across multiple subnets. On the network, an FCI appears to be an instance of SQL
Server running on a single computer, but the FCI provides failover from one WSFC node to another if the current node becomes unavailable.
It is similar to SQL Server failover cluster in SQL 2008 R2 and before.
Please refer to these references:
Failover Clustering in Analysis Services
Installing a SQL Server 2008 R2 Failover Cluster
Iric Wen
TechNet Community Support

HELP!! SQL Server SP3 breaks JDBC driver connections

Similar Messages

Maybe you are looking for