Use of Macromedia JDBC Drivers is restricted

We are building a new CF9 server. We installed the developer version and things appeared to work OK. When we set our single-server license (single server, not Enterprise) we get this message when trying some of our queries against a SQL Server database (did not try against Oracle, we only use SQL Server for this application).
Error Executing Database Query.
Use of Macromedia JDBC Drivers is restricted. Drivers can only be used with Macromedia server products. Please check that your license supports the requested driver.
One of the other threads here indicates that JDBC drivers are only enabled for the Enterprise version. Another thread however seems to indicate that we would need to reinstall and make sure that the correct drivers were selected during the install process. This part *did* work during the developer period (which I believe enables all Enterprise features).
Can standard version support JDBC? If not, can we use something else than JDBC? We don't want Enterprise.

First, yes, CF Standard supports JDBC. All CF database connections, regardless of version or license, use JDBC. The difference between Standard and Enterprise with regard to JDBC drivers is limited to the bundled Oracle driver included with Enterprise, Developer and Trial - this is not available for Standard.
Second, there's no relevant option for which JDBC drivers you get during the install process, regardless of version. There is an option for the JDBC-ODBC bridge, SequeLink, but that's not relevant to this.
Now, to fix your problem. First, make absolutely sure you're not using the Oracle driver! I know you said you're not, but better safe than sorry.
After that, the easiest approach would probably be to just completely uninstall CF and reinstall it with the correct license - at least, that would be the quickest without doing additional digging. However, I'm sure with a bit of tinkering you can fix your problem without uninstalling - I'm just not sure on the direction and amount of time that tinkering would take.
Alternatively, you could open a support ticket with Adobe, although honestly it would probably take you less time to just uninstall and reinstall CF.
Dave Watts, CTO, Fig Leaf Software

Similar Messages

  • Upgrade 10G to use 10G thin jdbc drivers- OCI

    This is wierd...
    If I upgrade 10G app server to use the 10G thin JDBC drivers, and set up a data source to use the thin drivers, is there any way that I could score a[b] ORA-01010 invalid OCI operation error when I'm not using an OCI driver?
    Anyone else seen this...again, it makes no sense...

    You can not and should not use JDK 1.2 with 8i drivers.
    If you want to use JDK 1.2 drivers, download the 8.1.6 SDK
    from external site.
    Please, please, please READ the FAQ at www.oracle.com/java/jdbc
    before posting
    Premal Mehta (guest) wrote:
    : Hi,
    : Sorry for multiple posting. Previous posting has incomplete
    : information. Here's the whole scenerio...
    : I have Oracle 8i installed on my server. I have downloaded
    : JDBC drivers for Oracle 8i from Oracle site. When I try to run
    a
    : sample example from the demo files given, I get a Windows
    : internal Error "Exception: Access Violation (0xc0000005),
    : Address: 0x6ee0fb83". I am using Oracle 8i on Win NT 4.0 with
    : SP4, IIS4.0 with 128 MB RAM.
    : Also, I am trying to use OCI8 JDBC drivers with JDK 1.2. The
    : classpath is set for classes111.zip files.
    : I am unable to run applets with JDBC also. On using thin
    : drivers, it gives "SO Exception" error.
    : I have tried many options but it dosent seem to work.
    Please
    : help as this is very urgent.
    Oracle Technology Network
    http://technet.oracle.com
    null

  • Using third party jdbc drivers in Portal server

    I have an application that runs inside the WebLogic Portal server. The portal server
    is configured to work with Oracle using the default oracle driver that comes with
    weblogic.
    My application, however, also needs to connect to a database. I am using the oracle-oci
    driver ( type 2 - provided by oracle) in my application.
    However, intermittantly i am getting an exception as follows:
    An unexpected exception has been detected in native code outside the VM.
    Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6044c4bc
    Function name=kpufhndl
    Library=D:\oracle\ora817\bin\OraClient8.Dll
    Current Java thread:
         at weblogic.db.oci.OciLob.native_finalize(Native Method)
         at weblogic.db.oci.OciLob.finalize(OciLob.java:654)
         at weblogic.db.oci.OciLob.closeLob(OciLob.java:589)
         at weblogic.jdbc.oci.Clob.close(Clob.java:176)
         at weblogic.jdbc.oci.Clob.closeLob(Clob.java:169)
         at weblogic.jdbc.oci.Connection.closeLob(Connection.java:582)
         at weblogic.jdbc.oci.Statement.close(Statement.java:393)
         at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:923)
         at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1114)
         at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
         at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
         at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    This is not happening always.
    Another related question is can the portal server use my driver instead of its
    own. If somebody from BEA is listening in, will BEA support such an installation?
    Any ideas are welcome.

    Hi,
    Unfortunately there was a regression bug around using the Generic JDBC connector to a Foreign Database in this Technology Preview (3). I'm not able to give you good news as I don't have a workaround for you either.
    You could use SQLDeveloper to connect to the database for live work, unfortunately that will not help if you wanted to create offline objects of some sort using JDeveloper.
    regards
    Susan
    http://www.susanduncan.blogspot.com

  • How to use third party jdbc drivers ?

    Hi,
    Im new to sun one app server.i have some existing CMP
    bean (currently testing under J2EE RI).database used is
    SQL server 2000 and using a 3 rd party JDBC Driver.
    my question is. if i switch to sun one app server, do i need
    anyother third party stuff to support CMP using SQL
    Server? (other than the exisiting jdbc driver andSQL Server).
    I read somewhere that in sun one we need to get a
    persistance manger from the 3 rd part. is it necessary?
    can i use my plain jdbc driver with the builtin persistance
    manager of sun one app server?. how can i do that ?
    thanks in advance
    -mr ex

    Hi,
    Persistence manager from 3rd party is not required.You
    can use the built in persistence manager of Sun one application server.
    You can refer the following link for creating new persistence manager
    http://docs.sun.com/source/816-7156-10/agj2eres.html#47595
    Get back in case of issues

  • CFMX8 - Enterprise OR Standard to use DataDirect JDBC drivers?

    Simple question here, I hope? I am migrating an application
    to CFMX8. This app connects to Informix. The best performance I've
    seen so far to do so is using DataDirect's JDBC driver. What I know
    is that DataDirect created a JDBC driver that ships with CFMX. What
    I don't know is why it
    seems CF somehow restricts access to that driver to
    Enterprise edition?!? Below are steps I have done.
    Using tech note
    shown
    here I did install the updated Macromedia drivers and created a
    DSN to the Informix database, but upon trying to save the DSN
    details, an error appeared stating:
    quote:
    java.sql.SQLException: Use of Macromedia JDBC Drivers is
    restricted. Drivers can only be used with Macromedia server
    products. Please check that your license supports the requested
    driver.
    This is pretty vague! Can anyone confirm that this is ONLY a
    Standard Ed. vs. Enterprise Ed. issue? Or is something else the
    matter?

    The Macromedia drivers are not available in standard edition
    of ColdFusion. They are availbale in enterprise and developer
    edition of ColdFusion.

  • JDBC Drivers incompatibility

    Hi,
    Using the latest JDBC drivers (in order to allow make
    use of the new GeoRaster capability), it is no longer
    possible to extract standard OrdImage's from the Database.
    I get get following Exception:
    java.lang.NoClassDefFoundError: oracle/jdbc/driver/ClientDataSupport
    at oracle.sqlj.runtime.OraCustomization$OraStatementCache.getClientDataSupport(OraCustomization.java:219)
    at sqlj.runtime.profile.ref.StatementCacheCustomization.getProfile(StatementCacheCustomization.java:130)
    at oracle.sqlj.runtime.OraCustomization.getProfile(OraCustomization.java:179)
    at sqlj.runtime.profile.ref.ProfileImpl.getConnectedProfile(ProfileImpl.java:176)
    at sqlj.runtime.ref.ProfileGroup$ConnectedGroup.getProfile(ProfileGroup.java:194)
    at sqlj.runtime.ref.ConnectionContextImpl.getConnectedProfile(ConnectionContextImpl.java:492)
    at sqlj.runtime.ExecutionContext.registerStatement(ExecutionContext.java:606)
    at oracle.ord.im.OrdImageBase._setProperties(OrdImageBase.java:618)
    at oracle.ord.im.OrdImage.setProperties(OrdImage.java:451)
    Is there anything that can be done ?
    (Apart from building a custom JDBC library comprising
    of components of the old and new one)
    Thanks,
    Ronan

    Found a solution !
    Removing the "ordImage.setProperties();" line of code
    resolved this issue.
    Ronan

  • How to use Multiple JDBC Drivers?

    Hi,
    I'm working with an application that connects to an Oracle 8 database and Oracle 10 databases as a single user/schema and then the application users all share the single Oracle user. When we use an Oracle 8 JDBC driver, then a module that inserts a large number of records (1500+) into an oracle table behaves inconsistently and either times out, pauses inserting records for exactly 1 hour, or throws an error. It also seems somewhat inconsistent from user to user.
    The problem goes away when we use an Oracle 10 or Oracle 11 JDBC driver. However, the Oracle 10 JDBC driver has a problem with truncating the hh:mi:ss from datetime column types to 00:00:00. This is a known Oracle error and I know there is a flag that can fix this with the Oracle 10 driver. However, with the way the JDBC driver gets installed in the application, we are unable to set that flag.
    Oracle 11 JDBC driver also doesn't have the Oracle 8 issue inserting a large number of records. However, we need to connect to an Oracle 8 database and Oracle 11 JDBC does not support that. The database is still active but being retired soon so no chance of upgrading to a newer Oracle version.
    I asked on the application forum (it's SAP Manufacturing Intelligence and Integration - MII) and was told the following. Data Server is a name for the connection to the database.
    "If the class packages are the same (assuming so since all of the oracle drivers I've seen use the same driver) then you can't have 2 at the same time, since they will overlap and you can't prioritize or point one data server to 8 and the other to 11."
    My experiments with trying to use two drivers have also shown this to be the case for what I tried.
    Any ideas or thoughts of how to make this work? We are using a JDK 1.5.
    Thanks for the help.
    Kerby Johnson

    The most reliable way would be to load each driver (and all code using it) using its own classloader.
    But that would likely be overly complicated.
    The most viable solution will likely be (especially as this is a short term project, you say it's going to be retired soon) to ensure a commit after every smaller subset of the total data volume and keep using the Oracle 8 drivers.
    Try forcing a commit after say every 100 records and see if you still have the timeout problems. Most likely this will take care of your problems at the cost of a slight performance decrease (but better somewhat less than optimal performance than risk database corruption or crashing applications, right?).

  • Problem using production version of SQL Server 2005 JDBC drivers

    A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
    We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
    Regards,
    Sabrina
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)     
         ... 11 more
    Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
    javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
         at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
         ... 12 more

    SabrinaL wrote:
    A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
    We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
    Regards,
    SabrinaHi. Have you done all the XA-related install for the new MS driver? (put the XA
    dll in the DBMS environment etc)? Is your DBMS on a 32-bit machine or 64-bit machine?
    Does the driver present a dll for each of those? You can also get good JDBC help
    from MS via their microsoft.public.sqlserver.jdbcdriver newsgroup.
    Joe Weinstein at BEA
    >
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)     
         ... 11 more
    Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
    javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
         at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
         ... 12 more

  • Error when using JDBC drivers

    Hi ..
    We have successfully deployed the JDBC drivers but in RWB(Communication channel monitoring) ,when executing we are getting an error
    Received XI System Error. ErrorCode: EXCHANGE_PROFILE_ACCESS ErrorText:   ErrorStack: Error while reading exchange profile for system PI7 and client 001
    2006-12-05 12:33:25 Error Transmitting the message to endpoint http://sap1:8001/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: EXCHANGE_PROFILE_ACCESS:.
    <b></b><i></i>
    Any suggestions
    Thanks
    Gopal
    Message was edited by:
            Gopal krishnan
    Message was edited by:
            Gopal krishnan

    Hi..
    I did it but here i am wondering becoz my RFC connection SAPSLDAPI works fine
    But at transaction SLDCHECK..it throws an error like
    Calling function LCR_LIST_BUSINESS_SYSTEMS
    Retrieving data from the SLD server...
    Function call returned exception code     4
    => Check whether the SLD is running!
    Summary: Connection to SLD does not work
    => Check SLD function and configurations
    But the SLD URL pops up and opens wih put any error.in a same fashion,it happens in SXMB_ADM--> integration engine config.it says connections to SLD doesnot work
    any idea to verify
    Thanks
    Gopal

  • Using INET and DATADIRECT JDBC Drivers to connect MS SQL Server 2005

    Hi,
    I have reqmt to connect SQL server 2005 from ODI using INET and DATADIRECT JDBC drivers to test Local characters Encoding.
    In my case, Oracle is the Source and SQL Server 2005 is the Target. I have problem while interfacing Local Characters to SQL Server 2005 using com.microsoft.sqlserver.jdbc.SQLServerDriver driver( which is default driver provided by ODI). To fix local charatcters issue, I want to try using INET or DATADIRECT JDBC drivers. Please provide me the below of any one has used these Drivers to connect SQL Server 2005 from ODI.
    We are trying to connect to MS SQL Server 2005 from ODI Topology Mgr using INET and DATADIRECT JDBC Drivers. We need the following info to connect to the same,
    --> What are list of the drivers need to be placed in OraHome_1\oracledi\drivers path?
    --> Where can i get the latest driver versions.
    --> What are the JDBC DRIVER and URL formats.
    --> Any other additional configurations?
    --> Does these drivers support interfacing of Local character data.
    Please respond...
    Regards,
    Anil

    Check this article [HOW TO: SQL & JAVA|http://www.shahriarnk.com/Shahriar-N-K-Research-Embedding-SQL-in-C-Sharp-Java.html] for details on how to connect to SQL Server database from C#.NET database applications as well as Java database applications. It also describes how to pass embedded SQL queries (SELECT, INSERT, UPDATE, DELETE), calling stored procedures, pass parameters etc.

  • OAS and using JDBC-drivers from EJB

    Hi.
    I have a problem with accessing the database from EJB-components
    deployed to OAS 4.0.8. The database is 8.1.5-version. I'm trying
    to use a connection exactly like it is documented in OAS-EJB-
    documents, the connection string looks like this:
    Connection conn = DriverManager.getConnection
    ("jdbc:oracle:jts8:@ora8i");
    And this is the error that above sentence it generates:
    "Sub Protocol must be specified in connection URL".
    The DAD(ora8i) is created in OAS.
    Now, I don't even know if this uses JDBC/OCI or thin since the
    documented connection-string doesn't contain that information. I
    quess it must use OCI-drivers, at least I should use them and
    they should be installed with OAS.
    So:
    * I should use only jts-enabled JDBC-drivers when developing EJB-
    components, is this right?
    * How can I connect to the database (from OAS 4.0.8 to Oracle
    8i), the string please?
    Thanks,
    [email protected]
    null

    Hi Suresh,
    There is lot of Documentation available on this, check these links
    http://help.sap.com/saphelp_nwce10/helpdata/en/45/07d2eeea3e0485e10000000a155369/frameset.htm
    http://help.sap.com/saphelp_nwce10/helpdata/en/45/08546ff5200486e10000000a155369/frameset.htm
    Venkat.

  • Thin JDBC Drivers Insert Strings Incorrectly

    Can anyone confirm or deny this.
    I've downloaded the latest Oracle 8i JDBC drivers. If I create a table:
    CREATE TABLE Moo (stringCol VARCHAR(10) NOT NULL);
    and I try to insert an empty String into Moo.stringCol, the JDBC drivers try to insert Null instead! Yet if I try and insert a String of one character in length, it inserts it correctly.
    Clearly it would seem the JDBC drivers are at fault.
    Anyone come across this?

    No, the drivers are performing correctly. In Oracle, an empty string in a varchar or varchar2 column is considered NULL. Regardless of what protocol or language you use to access the database, this will hold true.
    Justin

  • 3rd Party Access 2000 JDBC Drivers

    Wondering if anyone can recommend or rate any 3rd party MS Access JDBC drivers - I am running an app using Tomcat 4.0.2, on Windows 2K, currently using the JDBC/ODBC bridge from Sun, looking for something a little more specific and reliable for my app - company willing to spend the $$ to get something good.
    Thanks!
    Geoff

    hi Geoff ,
    I would recommend you the aveconnect driver from Atinav. It is a type 3 driver, and is a reliable and nice implementation. We have been using it for quite some time now and our developers here have seen it to be quite efficient and good.
    this url may help you..
    http://www.atinav.com/products/aveconnect/MSAccess.htm
    they provide a 30 day trial, and was worth a buy..
    hope that helps,
    -Jer

  • Mysql jdbc drivers not found in weblogic server

    I want to create a connection pool in weblogic server,
    and use mysqldatabase.
    My drivers is "org.gjt.mm.mysql.Driver"
    I put the jar in "D:\bea\weblogic700\server\lib" ,but when i apply ,there is
    an error blow:
    Error creating connection pool
         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:635)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:419)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)<2003-4-6 ����10��00��34��> <Error> <JDBC> <001060> <Cannot startup connection pool "mssqlserverPool" weblogic.common.ResourceException: Cannot load driver class: org.gjt.mm.mysql.Driver>
    Can anybody tell me why,thanks!

    Weblogic has been designed for nannies...
    I've developed a application which uses internally my own jdbc-driver.
    After months of really hard work on tomcat (the application works fine) I've tried migrate it to weblogic.
    But ...
    In weblogic seems mandatory to put the jdbc drivers out of the war!!!. Brilliant!!!
    If I move the driver out, I need move the 50% of the application out, also!
    If I move part of the application out, nothing works, because... �are the class loaders distinct?. And I'll need to do a lot of extra work because one day one weblogic architect had a great great inspiration.
    In the future I'll suggest to my customers to run and not stop when they listen the WEBLOGIC word.
    Regards,
    Pablo

  • Use of oracle.jdbc.driver now deprecated.

    Hi all,
    Just thought of sharing this note with us.,(if its new ..)
    http://otn.oracle.com/docs/products/oracle9i/doc_library/901_doc/java.901/a90211/overvw.htm#1008871
    Extract ...,
    Beginning in Oracle9i, the Oracle extensions to JDBC are captured in the package oracle.jdbc. This package contains classes and interfaces that specify the
    Oracle extensions in a manner similar to the way the classes and interfaces in java.sql specify the public JDBC API.
    Your code should use the package oracle.jdbc instead of the package oracle.jdbc.driver used in earlier versions of Oracle. Use of the package
    oracle.jdbc.driver is now deprecated, but will continue to be supported for backwards compatibility.
    All that is required to covert your code is to replace "oracle.jdbc.driver" with "oracle.jdbc" in the source and recompile. This cannot be done piece-wise.
    You must convert all classes and interfaces that are referenced by an application. Conversion is not required, but is highly recommended. Future releases of Oracle
    may have features that are incompatible with use of the package oracle.jdbc.driver.
    The purpose of this change is to enable the Oracle JDBC drivers to have multiple implementations. In all releases up to and including Oracle9i, all of the Oracle
    JDBC drivers have used the same top level implementation classes, the classes in the package oracle.jdbc.driver. By converting your code to use
    oracle.jdbc, you will be able to take advantage of future enhancements that use different implementation classes. There are no such enhancements in Oracle9i, but
    there are plans for such enhancements in the future.
    Regards
    Elango.

    The two main things that would have to change
    - driver : com.microsoft.sqlserver.jdbc.SQLServerDriver
    - url: jdbc:microsoft:sqlserver://localhost:1433
    It may be that this page will help you
    http://msdn.microsoft.com/data/learning/jdbc/
    You also need to make sure that the files Msbase.jar , Msutil.jar and Mssqlserver.jar are all available in the "classpath"
    For a web app, that means these files should be in the WEB-INF/lib directory.
    Good luck,
    evnafets

Maybe you are looking for