ODBC incompatibility with varchar type microsoft sql server 2005

Hi,
My details:
OS: Oracle Solaris 10
Oracle version: 10.2.0.3
MSSQL version: SQL Server 2005 SP2
HSODBC driver: datadirect
I configurerd the HSODBC driver on solaris to communicate from oracle to MSSQL.
Everything works fine, except he don't show the nvarchar columns of MSSQL.
Can anyone help me with that??
Thx

Nigel Guest wrote:
Hi,
Has anyone successfully used the Microsoft SQL Server 2005 JDBC Driver (version 1.1) with XA connections ?yes.
If so, I have the following question:
As this driver appears to support both TX & XA in the same jar file, how would I go about setting up a connection pool in weblogic to only use XA ?
Is it a connection parameter ?
thanks for any advice..
/NigelIf you want an XA pool, specify the
driver's XA DataSource as the class
to use.

Similar Messages

License type of SQL Server 2005 Best Practices Analyzer

Hi everybody.
I need to install in my organization the software "SQL Server 2005 Best Practices Analyzer" but I need to know if this application it's free licensing. I have seen on several web sites about this tool it's free but not in official microsoft
web page. So, where can I find the official microsoft information about the type of licensing of "SQL Server 2005 Best Practices Analyzer" ?
Thanks of your support

Hello Erland.
I followed your advice and I have read the terms of use of this software. I stop at point 3 (which I highlighted). Based on this point, I doubt it is about using this application. Furthermore nowhere says that this software is free to use.
Would appreciate if someone can clarify this to me.
=============================================================
MICROSOFT SOFTWARE LICENSE TERMS
MICROSOFT SQL SERVER 2005 BEST PRACTICES ANALYZER:
These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its affiliates) and you.
Please read them. They apply to the software named above, which includes the media on which you received it, if any.
The terms also apply to any Microsoft
* updates,
* supplements,
* Internet-based services, and
* support services
for this software, unless other terms accompany those items.
If so, those terms apply.
BY USING THE SOFTWARE, YOU ACCEPT THESE TERMS.
IF YOU DO NOT ACCEPT THEM, DO NOT USE THE SOFTWARE.
If you comply with these license terms, you have the rights below.
1.
INSTALLATION AND USE RIGHTS. You may install and use any number of copies of the software on your devices.
2.
INTERNET-BASED SERVICES. Microsoft provides Internet-based services with the software.
It may change or cancel them at any time.
3.
SCOPE OF LICENSE. The software is licensed, not sold. This agreement only gives you some rights to use the software.
Microsoft reserves all other rights.
Unless applicable law gives you more rights despite this limitation, you may use the software only as expressly permitted in this agreement.
In doing so, you must comply with any technical limitations in the software that only allow you to use it in certain ways.
You may not
* work around any technical limitations in the software;
* reverse engineer, decompile or disassemble the software, except and only to the extent that applicable law expressly permits, despite this limitation;
* make more copies of the software than specified in this agreement or allowed by applicable law, despite this limitation;
* publish the software for others to copy;
* rent, lease or lend the software;
* transfer the software or this agreement to any third party; or
* use the software for commercial software hosting services.
4.
BACKUP COPY. You may make one backup copy of the software.
You may use it only to reinstall the software.
5.
DOCUMENTATION. Any person that has valid access to your computer or internal network may copy and use the documentation for your internal, reference purposes.
6.
EXPORT RESTRICTIONS. The software is subject to United States export laws and regulations.
You must comply with all domestic and international export laws and regulations that apply to the software.
These laws include restrictions on destinations, end users and end use.
For additional information, see www.microsoft.com/exporting.
7.
SUPPORT SERVICES. Because this software is "as is," we may not provide support services for it.
8.
ENTIRE AGREEMENT. This agreement, and the terms for supplements, updates, Internet-based services and support services that you use, are the entire agreement for the software and support services.
9.
APPLICABLE LAW.
a. United States. If you acquired the software in the United States, Washington state law governs the interpretation of this agreement and applies to claims for breach of it, regardless of conflict of laws principles.
The laws of the state where you live govern all other claims, including claims under state consumer protection laws, unfair competition laws, and in tort.
b. Outside the United States. If you acquired the software in any other country, the laws of that country apply.
10.
LEGAL EFFECT. This agreement describes certain legal rights.
You may have other rights under the laws of your country.
You may also have rights with respect to the party from whom you acquired the software.
This agreement does not change your rights under the laws of your country if the laws of your country do not permit it to do so.
11.
DISCLAIMER OF WARRANTY. THE SOFTWARE IS LICENSED "AS-IS."
YOU BEAR THE RISK OF USING IT. MICROSOFT GIVES NO EXPRESS WARRANTIES, GUARANTEES OR CONDITIONS.
YOU MAY HAVE ADDITIONAL CONSUMER RIGHTS UNDER YOUR LOCAL LAWS WHICH THIS AGREEMENT CANNOT CHANGE.
TO THE EXTENT PERMITTED UNDER YOUR LOCAL LAWS, MICROSOFT EXCLUDES THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
12.
LIMITATION ON AND EXCLUSION OF REMEDIES AND DAMAGES. YOU CAN RECOVER FROM MICROSOFT AND ITS SUPPLIERS ONLY DIRECT DAMAGES UP TO U.S. $5.00.
YOU CANNOT RECOVER ANY OTHER DAMAGES, INCLUDING CONSEQUENTIAL, LOST PROFITS, SPECIAL, INDIRECT OR INCIDENTAL DAMAGES.
This limitation applies to
* anything related to the software, services, content (including code) on third party Internet sites, or third party programs; and
* claims for breach of contract, breach of warranty, guarantee or condition, strict liability, negligence, or other tort to the extent permitted by applicable law.
It also applies even if Microsoft knew or should have known about the possibility of the damages.
The above limitation or exclusion may not apply to you because your country may not allow the exclusion or limitation of incidental, consequential or other damages.
Please note: As this software is distributed in Quebec, Canada, some of the clauses in this agreement are provided below in French.

Downloadin of microsoft SQL server 2005 express edition service pack 3 (KB955706) fail everytime

i have been tryin to dl microsoft SQL server 2005 express edition service pack 3 (KB955706) for the past 2 months and always get the same prob. it always say error code:534- window has encounter an unkown error.
i got a feelin tat it is due to the update file bein corrupted as my lenovo laptop T400 crashed once. But i m not sure. any suggestion? pls dun tell me to look at microsoft web help. totally not much help....

Hello computer156,
I meant your operating system, Vista or XP? I think you problem has more to do with MS than with you machine.
Please check this site out.
Follow @LenovoForums on Twitter! Try the forum search, before first posting: Forum Search Option
Please insert your type, model (not S/N) number and used OS in your posts.
I´m a volunteer here using New X1 Carbon, ThinkPad Yoga, Yoga 11s, Yoga 13, T430s,T510, X220t, IdeaCentre B540.
TIP: If your computer runs satisfactorily now, it may not be necessary to update the system.
English Community Deutsche Community Comunidad en Español

Errors while migrating from Microsoft SQL Server 2005 to Oracle 9i

Hi All,
We are trying to completely move our application from Microsoft SQL Server 2005 Database to Oracle 9i. I am doing it using the latest version of Oracle SQL Developer (1.2 build 29.98).
When I right click my MSSQL server db and click "Capture Microsoft SQL server", it just shows a dialog with "Close" enabled.
Kindly help.
The migration Log has the following messages:
oracle.dbtools.metadata.persistence.PersistenceException: Unsupported feature
oracle.dbtools.metadata.persistence.PersistenceException: Unsupported feature
oracle.dbtools.metadata.persistence.PersistenceException: OALL8 is in an inconsistent state
oracle.dbtools.metadata.persistence.PersistenceException: Protocol violation
oracle.dbtools.metadata.persistence.PersistenceException: OALL8 is in an inconsistent state
oracle.dbtools.metadata.persistence.PersistenceException: Protocol violation
oracle.dbtools.metadata.persistence.PersistenceException: OALL8 is in an inconsistent state
oracle.dbtools.metadata.persistence.PersistenceException: Protocol violation
oracle.dbtools.metadata.persistence.PersistenceException: OALL8 is in an inconsistent state
oracle.dbtools.metadata.persistence.PersistenceException: Bigger type length than Maximum
oracle.dbtools.metadata.persistence.PersistenceException: Bigger type length than Maximum
oracle.dbtools.metadata.persistence.PersistenceException: OALL8 is in an inconsistent state
Error ocurred during capture: Protocol violation
oracle.dbtools.metadata.persistence.PersistenceException: OALL8 is in an inconsistent state
oracle.dbtools.metadata.persistence.PersistenceException: Protocol violation
oracle.dbtools.metadata.persistence.PersistenceException: OALL8 is in an inconsistent state
oracle.dbtools.metadata.persistence.PersistenceException: Protocol violation
oracle.dbtools.metadata.persistence.PersistenceException: OALL8 is in an inconsistent state
oracle.dbtools.metadata.persistence.PersistenceException: Bigger type length than Maximum
I cant figure out what do these messages mean.
Regards,
Sandeep

Pasting the errors on logging page, if this is of any help:
SEVERE     150     0     oracle.dbtools.raptor.utils.NLSUtils     Error loading nls:OALL8 is in an inconsistent state
SEVERE     151     1485     oracle.dbtools.raptor.utils.NLSUtils     Error loading nls:Protocol violation
SEVERE     152     15     oracle.dbtools.raptor.utils.NLSUtils     Error loading nls:OALL8 is in an inconsistent state
SEVERE     153     10954     oracle.dbtools.raptor.utils.NLSUtils     Error loading nls:Protocol violation
SEVERE     154     15     oracle.dbtools.raptor.utils.NLSUtils     Error loading nls:OALL8 is in an inconsistent state
SEVERE     155     2688     oracle.dbtools.raptor.utils.NLSUtils     Error loading nls:Protocol violation
SEVERE     156     1140     oracle.dbtools.raptor.utils.NLSUtils     Error loading nls:OALL8 is in an inconsistent state
SEVERE     158     62172     oracle.dbtools.raptor.utils.NLSUtils     Error loading nls:OALL8 is in an inconsistent state
SEVERE     160     3672     oracle.dbtools.raptor.utils.NLSUtils     Error loading nls:Protocol violation
SEVERE     161     63     oracle.dbtools.raptor.utils.NLSUtils     Error loading nls:OALL8 is in an inconsistent state
SEVERE     162     0     oracle.dbtools.raptor.utils.NLSUtils     Error loading nls:Protocol violation

Is there a way to convert Crystal Reports to Microsoft SQL Server 2005 reporting services?

Post Author: Lourdes Hernandez
CA Forum: General
Our department has always worked with and we love Crystal Reports. Unfortunately, certain reports now need to be converted to Microsoft SQL Server 2005 reporting services which from what I read I think they are *.rdl reports. Does Crystal reports have any way around this? I would have to learn this other tool when I'm already so happy with Crystal. I was thinking If I could just code the report in crystal and export it in a specific format that would be compatible Microsoft, the problem would be solved.
Any ideas would be greatly appreciated.

Post Author: bettername
CA Forum: General
Ditto!
There are some software packages to convert from CR to RS, but none work 100% AFAIK, and will require manual tuning.
Seems like a big hassle and learning curve just to get reports published via another method - I know I'd put up huge resistance if they tried to take my CR away from me!

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

Error during installation of Microsoft SQL Server 2005

Hello All,
During installation of Microsoft SQL Server 2005 I have got the below error message
"There was an unexpected failure during the setup wizard"
From this link http://support.microsoft.com/kb/916760 i came to know that this error occurs just because I used SQL Server 2005 installations from a folder on a network share.
After that i unstall everything & copy the installations in a local drive. But again when we restart the activity we got the same error message & the installation completed.
Any hint why this happens..
Thank You.
Kind Regards,
Jituda

Hello Jituda,
I think we need to focus on the error in the setup log first.
Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. Error information reported during run:
Source File Name: datastore\cachedpropertycollection.cpp
you might be able to see more detailed error information in the log.
You may check if the following links help:
http://www.sqlserverfaq.net/2008/12/17/sql-server-2005-setup-failing-to-install-on-cluster-with-unexpected-failure-while-performing-the-scc-checks/
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/f998b073-4378-4d02-95ac-c9afb31c7a60
In addition, to clarify, the SQL4SAP.VBS script does not support Microsoft Cluster Service (MSCS). If you want to run the
script in an MSCS configuration, you get an error message. In MSCS configuration need to install the SQL Server database software manually instead of using the script. Please see the corresponding SAP product installation guide under http://service.sap.com/instguides
Kind regards,
Qingqing Wang

Windows Authentication using Microsoft SQL Server 2005 JDBC Driver

Hi,
I am using Microsoft SQL Server 2005 JDBC Driver to connect to SQL Server 2000 database, can anyone tell me the connection URL for windows authentication. SQL authentication is working fine.
DataDirect has drivers for windows authentication but I am not using it.
Regards
Arup

You can't do it with the Microsoft driver. There's a free driver called jTDS that may be able to (I don't know).
(edit) Looking at their FAQ it looks like it does:
http://jtds.sourceforge.net/faq.html

Migrate oracle database to Microsoft sql server 2005

Hi All,
I have to migrate production oracle database to Microsoft sql server 2005. Below are the details:
Oracle database version: 8.1.7.4
Platform : Aix
Kindly help me out

Well, the traditional way would be to dump out all your data from Oracle tables as comma delimited flat files and import into SQL server. Plenty of examples online, like this is one by Mark Powell: http://www.jlcomp.demon.co.uk/faq/flatfile.html
Or if you have the budget you could think about buying a data mapping tool like File-Aid
As mentioned by another poster, you will still need to figure out how to replace all your triggers, stored procedures, etc on your new platform of course.

Microsoft SQL Server 2005 JDBC Driver

Hi
how can i use Microsoft SQL Server 2005 JDBC Driver to coonect to db???

com.microsoft.jdbc.sqlserver.SQLServerDriver is a SQL Server 2000 class.
Also the port setting in the connection url jdbc:sqlserver://localhost:<port> is not 1433 as in SQL Server 2000.
In the connection URL, <port> is obtained from the SQL Server configuration Manager. When the SQL Server 2005 is restarted the port number changes.
To obtain the <port> in the SQL Server Configuration Manager select the node SQL Server 2005 Network Configuration>Protocols. Right-click on TCP/IP node and select Properties. Select the IP Addresses tab. In IP ALL the TCP Dynamic Ports specifies the <port> value.

Error with Forms6i accesing Microsoft SQL Server 7

Hello every body, this is my problem:
- Forms6i
- OCA 6.0.5.35
- Microsoft Sql Server 7.0
I can access to SQL Server database with Oracle SQL*Plus release 8.0.6.0.0 with no problem. But developing a form when i try to
create a new data block with the wizard
i put the name of the table and when i push
the "refresh" button i get this message:
"FRM-10095 asertion failed" and no columns displayed.
Thanks in advanced.
null

sandeepjava wrote:
java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
Add the mentioned class (or in this specific case, the JAR file with the mentioned class) to the classpath of your runtime environment and you're fine.

Required Microsoft Sql Server 2005 Server Roles for JDBC Connection

Hi!
I have developed a database in MS SQL Server 2005, to which I would require only bulkadmin server role from an external java application, because I only need to update rows, insert values or use select queries in the database.
The problem is that, using either the Microsoft JDBC Driver 1.1 or the Java JDBC ODBC Driver and the Windows XP Data Base (ODBC) configurations, I need a user with sysadmin server role inside Sql Server, otherwise JDBC won't connect to the database using the selected user. Even if I leave the sql login with setupadmin or any server role lower than sysadmin, the connection is refused.
Is there no way to connect using JDBC to MS Sql Server 2005 other than granting the connected user sysadmin rights? My code looks as follows:
String driver = "com.microsoft.sqlserver.jdbc.SQLServerDriver";
String url = "jdbc:sqlserver://FIREBLADE\\SQLEXPRESS";
String user = "username";
String password = "password$$";
Connection conn;
Class.forName(driver);
conn = DriverManager.getConnection(url,user,password);
if (conn != null)
System.out.println("\nSQL Server Connection established ...\n");
I have heard that Java JDBC connections to Microsoft require high-level access, and if that's the case I would rather migrate my database to MySql.
Any informed answer is more than welcome. Thanks for reading my post!

Well i personally prefer usage of open source MS SQL SERVER 2k jdbc driver called jtds instead of the driver provided by MS themselves(which is proproteriry) as i had similar problem which i personally encountered when i was using it.
go through the below link for further info.
http://jtds.sourceforge.net/
REGARDS,
RaHuL

Issue with migration DB from SQL Server 2005 to Oracle 11.2 using SQL Developer Migration workbench

Hi,
We face an issue while migrating an SQL Server 2005 DB to Oracle 11.2. It fails during the process. I hope someone on the forum has seen this before and can give us some advice.
I use the latest version of SQL Developer with JRE included (3.2.20.09). The JDBC driver to connect to SQL Server 2005 is 1.2.0
Here are the steps we take in the Migration Workbench wizard:
I made an online extract of the SQL Server database.
Using the workbench in SQL Developer I created a migration repository in schema PDM_MIGRATION.
Next I start the migration, it captures the tables fine, but immediately after the start of the conversion I get a failed message without further explanations.
This is the content of the error xml:
<?xml version="1.0" encoding="windows-1252" standalone="no"?>
<log>
<record>
<date>2013-08-14T16:23:32</date>
<logger>oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle</logger>
<level>SEVERE</level>
<class>oracle.dbtools.migration.workbench.core.logging.MigrationLogUtil</class>
<message>Ongeldig naampatroon.: PDM_MIGRATION .MIGR_FILTER</message>
<param>oracle.dbtools.migration.workbench.core.logging.LogInfo@4c12ab</param>
<exception>
    <message>oracle.dbtools.migration.convert.ConvertException: Ongeldig naampatroon.: PDM_MIGRATION .MIGR_FILTER</message>
    <frame>
      <class>oracle.dbtools.migration.convert.ConverterWorker</class>
      <line>1078</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.convert.ConverterWorker</class>
      <line>316</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>1002</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>303</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>205</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>159</line>
    </frame>
    <frame>
      <class>oracle.dbtools.raptor.backgroundTask.RaptorTask</class>
      <line>193</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask$Sync</class>
      <line>303</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask</class>
      <line>138</line>
    </frame>
    <frame>
      <class>oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$RaptorFutureTask</class>
      <line>515</line>
    </frame>
    <frame>
      <class>java.util.concurrent.Executors$RunnableAdapter</class>
      <line>441</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask$Sync</class>
      <line>303</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask</class>
      <line>138</line>
    </frame>
    <frame>
      <class>java.util.concurrent.ThreadPoolExecutor$Worker</class>
      <line>886</line>
    </frame>
    <frame>
      <class>java.util.concurrent.ThreadPoolExecutor$Worker</class>
      <line>908</line>
    </frame>
    <frame>
      <class>java.lang.Thread</class>
      <line>662</line>
    </frame>
</exception>
</record>
<record>
<date>2013-08-14T16:23:32</date>
<logger>oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle</logger>
<level>SEVERE</level>
<class>oracle.dbtools.migration.workbench.core.logging.MigrationLogUtil</class>
<message>Ongeldig naampatroon.: PDM_MIGRATION .MIGR_FILTER</message>
<param>oracle.dbtools.migration.convert.ConverterWorker.copyModel(ConverterWorker.java:1078)</param>
<param>oracle.dbtools.migration.convert.ConverterWorker.runConvert(ConverterWorker.java:316)</param>
<param>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask.doConvert(FullMigrateTask.java:1002)</param>
<param>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask.doMaskBasedActions(FullMigrateTask.java:303)</param>
<param>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask.doWork(FullMigrateTask.java:205)</param>
<param>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask.doWork(FullMigrateTask.java:159)</param>
<param>oracle.dbtools.raptor.backgroundTask.RaptorTask.call(RaptorTask.java:193)</param>
<param>java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)</param>
<param>java.util.concurrent.FutureTask.run(FutureTask.java:138)</param>
<param>oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$RaptorFutureTask.run(RaptorTaskManager.java:515)</param>
<param>java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)</param>
<param>java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)</param>
<param>java.util.concurrent.FutureTask.run(FutureTask.java:138)</param>
<param>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)</param>
<param>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)</param>
<param>java.lang.Thread.run(Thread.java:662)</param>
<param>oracle.dbtools.migration.workbench.core.logging.LogInfo@5dc1bc</param>
<exception>
    <message>oracle.dbtools.migration.convert.ConvertException: Ongeldig naampatroon.: PDM_MIGRATION .MIGR_FILTER</message>
    <frame>
      <class>oracle.dbtools.migration.convert.ConverterWorker</class>
      <line>1078</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.convert.ConverterWorker</class>
      <line>316</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>1002</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>303</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>205</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>159</line>
    </frame>
    <frame>
      <class>oracle.dbtools.raptor.backgroundTask.RaptorTask</class>
      <line>193</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask$Sync</class>
      <line>303</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask</class>
      <line>138</line>
    </frame>
    <frame>
      <class>oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$RaptorFutureTask</class>
      <line>515</line>
    </frame>
    <frame>
      <class>java.util.concurrent.Executors$RunnableAdapter</class>
      <line>441</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask$Sync</class>
      <line>303</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask</class>
      <line>138</line>
    </frame>
    <frame>
      <class>java.util.concurrent.ThreadPoolExecutor$Worker</class>
      <line>886</line>
    </frame>
    <frame>
      <class>java.util.concurrent.ThreadPoolExecutor$Worker</class>
      <line>908</line>
    </frame>
    <frame>
      <class>java.lang.Thread</class>
      <line>662</line>
    </frame>
</exception>
</record>
<record>
<date>2013-08-14T16:23:32</date>
<logger>oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle</logger>
<level>WARNING</level>
<class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
<message>Building converted model: FAILED : Database Migration : FAILED</message>
<param>oracle.dbtools.migration.workbench.core.logging.LogInfo@15a3779</param>
</record>
Does anybody know what this error means and what steps we should take to continue the migration?
I see the PDM_MIGRATION.MIGR_FILTER is a type.
Many thanks in advance,
Kris

Hi Wolfgang,
Thanks for your reply.
This is how the type MIGR_FILTER looks like:
create or replace
TYPE MIGR_FILTER IS OBJECT (
FILTER_TYPE INTEGER, -- Filter Types are 0-> ALL, 1->NAMELIST, 2->WHERE CLAUSE, 3->OBJECTID LIST
OBJTYPE VARCHAR2(40),
OBJECTIDS OBJECTIDLIST,
NAMES NAMELIST,
WHERECLAUSE VARCHAR2(1000));
I think the repository user has the correct privileges. This is the overview of privileges it has:
SQL> select * from dba_sys_privs where GRANTEE in ('PDM_MIGRATION') order by GRANTEE;
GRANTEE PRIVILEGE ADM
PDM_MIGRATION ALTER SESSION NO
PDM_MIGRATION CREATE CLUSTER NO
PDM_MIGRATION CREATE DATABASE LINK NO
PDM_MIGRATION CREATE PROCEDURE NO
PDM_MIGRATION CREATE SEQUENCE NO
PDM_MIGRATION CREATE SESSION NO
PDM_MIGRATION CREATE SYNONYM NO
PDM_MIGRATION CREATE TABLE NO
PDM_MIGRATION CREATE TRIGGER NO
PDM_MIGRATION CREATE VIEW NO
PDM_MIGRATION UNLIMITED TABLESPACE NO
SQL> select * from dba_role_privs where GRANTEE in ('PDM_MIGRATION') order by GRANTEE;
GRANTEE GRANTED_ROLE ADM DEF
PDM_MIGRATION CONNECT NO YES
PDM_MIGRATION RESOURCE NO YES
Best regards,
Kris

MicroSoft SQL Server 2005

Hi Experts,
Please let me know if we can use ODI with Mircosoft SQL Server 2005.
The Drive list is showing only MS SQL Sever 2000.
Thanks and Regards,
Andy

Hi,
Yes you can definitely use sql server 2005, you just need to manually enter the driver name and url.
e.g.
com.microsoft.sqlserver.jdbc.SQLServerDriver
jdbc:sqlserver://<sqls machine>:1433;databaseName=<db name>;integratedSecurity=false
Cheers
John
http://john-goodwin.blogspot.com/

Windows 8 Photo gallery can't start because Microsoft SQL server 2005 compact edition is missing?

I've installed & uninstalled MS SqlSever 2005 in my system (OS - Windows 8). When am try to access my photo gallery on desktop, I'm getting above mentioned error. How come photo gallery is dependent on MS SqlServer 2005 compact edition? Now,
I've installed & using MS SqlServer 2008.

ErikEJ,
I tried the link you provided and it points to the SQL Server 2005 Compact Edition that will not install in Windows 8. IS there some other package you are trying to send us to? I cannot install / run Photo Gallery because it needs SQL Server 2005 Compact
Ed and the latter when run reports it is not compatible with my operating system, ie., Windows 8 Pro, x64.
Can you help?
TigerWizard
Brenda W [email protected]; [email protected]

ODBC incompatibility with varchar type microsoft sql server 2005

Similar Messages

Maybe you are looking for