Compatibility of Weblogic 6.1 Oracle Thin Driver for Oracle 9i. - URGENT Reply Needed..Thanks.

Hi, We are using Weblogic 6.1. We are currently using JDBC Oracle Thin Driver (ClassName
: oracle.jdbc.driver.OracleDriver) that is built into Weblogic 6.1 (weblogic.jar).
Our database is Oracle 8.1.7.4. We want to upgrade to Oracle 9i (Oracle version
9.2.0.4). I would like to know the compatibility of this built-in Driver for Weblogic
6.1 with Oracle 9i (9.2.0.4) and can I continue to use the same JDBC driver. Also
we have plans to upgrade our Weblogics to 8.1 version. Can we continue to use
the same Oracle Thin driver that comes as part of WLS 8.1, for Oracle 9.2.0.4.
I need this reply ASAP. I appreciate any help in this regard.
Thanks, Venkatesan.

Thank you very much for your reply.
Joe Weinstein <[email protected]> wrote:
Hi. The driver we shipped will still work with the later DBMS, but there
have been many improvements and fixes to Oracle's dirver since then,
so I highly recommend that you download Oracle's latest appropriate
thin driver, and make sure it gets into the -classpath argument that
the weblogic startup script creates for the server.
Every release of weblogic will tend to include the latest oracle
thin driver available at the time, so the 8.1 will contain a newer one
than
the 6.1.
Joe
Venkatesan wrote:
Hi, We are using Weblogic 6.1. We are currently using JDBC Oracle ThinDriver (ClassName
: oracle.jdbc.driver.OracleDriver) that is built into Weblogic 6.1(weblogic.jar).
Our database is Oracle 8.1.7.4. We want to upgrade to Oracle 9i (Oracleversion
9.2.0.4). I would like to know the compatibility of this built-in Driverfor Weblogic
6.1 with Oracle 9i (9.2.0.4) and can I continue to use the same JDBCdriver. Also
we have plans to upgrade our Weblogics to 8.1 version. Can we continueto use
the same Oracle Thin driver that comes as part of WLS 8.1, for Oracle9.2.0.4.
I need this reply ASAP. I appreciate any help in this regard.
Thanks, Venkatesan.

Similar Messages

  • How to set oracle thin driver for jdbc2.0 in WLS6.1?

    I want to use oracle thin driver for jdbc2.0 in WLS6.1.
    I just set it like what it look in jdbc1.2.
    In my code, I import the classes under package oracle.sql.* and oracle.jdbc.*.
    When I cast the connection from (DataSource)ctx.lookup("myPool").getConnection();
    to oracle.jdbc.OracleConnection,
    it raise the exception java.lang.ClassCastException: weblogic.jdbc.rmi.SerialConnection.
    Can any one tell me how to solve it? Thanks

    Hi Andy,
    You can not cast a connection returned from datasource
    to oracle.jdbc.OracleConnection as it's a kind of an RMI
    stub thus has nothing to do with oracle. Could you tell us
    what you're going to acomplish? We'll try to offer a solution.
    Regards,
    Slava Imeshev
    "Andy Qiu" <[email protected]> wrote in message
    news:3d74787c$[email protected]..
    >
    I want to use oracle thin driver for jdbc2.0 in WLS6.1.
    I just set it like what it look in jdbc1.2.
    In my code, I import the classes under package oracle.sql.* andoracle.jdbc.*.
    When I cast the connection from(DataSource)ctx.lookup("myPool").getConnection();
    to oracle.jdbc.OracleConnection,
    it raise the exception java.lang.ClassCastException:weblogic.jdbc.rmi.SerialConnection.
    Can any one tell me how to solve it? Thanks

  • Oracle JDBC Thin Driver for oracle 9.2.0.4

    Hi,
    It would be nice if someone please guide me to the download of Oracle JDBC Thin Driver for oracle 9.2.0.4.
    Thanks in anticipation

    user566773,
    As far as I know, all Oracle JDBC drivers are meant to be backward compatible.
    According to the table on the following Web page, the latest Oracle JDBC driver can be used with Oracle 9.2.0.x DBMS.
    http://www.oracle.com/technology/tech/java/sqlj_jdbc/index.html
    Good Luck,
    Avi.

  • JDBC thin driver for oracle 7.1.3

    Hi,
    we r using Oracle 7.1.3. i would like to know where i can get the
    thin driver for java compatible with the oracle version 7.1.3 so
    that i need not install an oracle client in the clients pc.
    thanks
    veera
    null

    Jay (guest) wrote:
    : BUBBA (guest) wrote:
    : : Veera Nagendran (guest) wrote:
    : : : Hi,
    : : : we r using Oracle 7.1.3. i would like to know where i can
    : get
    : : the
    : : : thin driver for java compatible with the oracle version
    : 7.1.3
    : : so
    : : : that i need not install an oracle client in the clients pc.
    : : : thanks
    : : : veera
    : : Thedatabase you're using went out of support over 2 years
    ago.
    : : oracle doesn't provide jdbc drivers for anything less than
    : : supported version 7.3.4.
    : So why does Oracle make this claim
    : "The Thin driver does not require Oracle software on the client
    : side. It connects to any Oracle database of version 7.2.x and
    : higher. The driver requires a TCP/IP listener on the server
    : side. " ???
    : Jay
    re-read my earlier reply -- the comment was :
    Thedatabase you're using went out of support over 2 years
    ago. oracle doesn't provide jdbc drivers for anything less
    than the minimum supported version ---> 7.3.4.At no time did i refer to the client s/w being required !!
    also it was not tested against unsupported version of the
    rdbms ...
    also rdbms 7.1.3 isn't y2k compliant.
    use it at your own risk..
    what "claim" are you saying oracle made ??
    null

  • Problem in WSAD 5.0.0 with Oracle thin Driver

    Hi All,
    Can anyone help me to solve the following problem while using a batch update
    java.lang.NullPointerException
         at oracle.jdbc.dbaccess.DBData.clearItem(DBData.java:431)
         at oracle.jdbc.dbaccess.DBDataSetImpl.clearItem(DBDataSetImpl.java:3528)
         at oracle.jdbc.driver.OraclePreparedStatement.clearParameters(OraclePreparedStatement.java:3401)
         at oracle.jdbc.driver.OracleCallableStatement.clearParameters(OracleCallableStatement.java:818)
         at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.resetStatement(WSJdbcConnection.java:1767)
         at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.prepareCall(WSJdbcConnection.java:1381)
         at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.prepareCall(WSJdbcConnection.java:1346)
         at com.americanexpress.statdc.manual.dao.ManualStatLoadDAO.loadStatItems(ManualStatLoadDAO.java:668)
         at com.americanexpress.statdc.manual.dao.ManualStatLoadDAO.submitStatItems(ManualStatLoadDAO.java:609)
         at com.americanexpress.statdc.manual.ejb.ManualStatLoadEJBBean.submitStatItems(ManualStatLoadEJBBean.java:252)
         at com.americanexpress.statdc.manual.ejb.EJSRemoteStatelessManualStatLoadEJB_38e2da07.submitStatItems(EJSRemoteStatelessManualStatLoadEJB_38e2da07.java:472)
         at com.americanexpress.statdc.manual.ejb._ManualStatLoadEJB_Stub.submitStatItems(_ManualStatLoadEJB_Stub.java:451)
         at com.americanexpress.statdc.manual.businessdelegate.ManualStatLoadBusinessDelegate.submitStatItems(ManualStatLoadBusinessDelegate.java:86)
         at com.americanexpress.statdc.manual.handlers.InputterStatDataRequestHandler.processRequest(InputterStatDataRequestHandler.java:123)
         at com.americanexpress.util.frontservlet.FrontServlet.processRequest(Unknown Source)
         at com.americanexpress.util.frontservlet.FrontServlet.doPost(Unknown Source)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
         at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
         at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
         at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
         at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
         at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:76)
         at com.americanexpress.statdc.infrastructure.filter.StatDCGZipFilter.doFilter(StatDCGZipFilter.java:59)
         at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:132)
         at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:71)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:1064)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:598)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:206)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:80)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:214)
         at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
         at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:116)
         at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
         at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
         at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
         at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:623)
         at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:447)
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672)
    This exception is occuring at the time of preparing the Callable Statement.
    We are using WSAD 5.0.0 with JDK 1.3.1, Oracle thin driver for Oracle 9i.
    Thanks in advance.
    Regards,
    Shesha

    Hi,
    This problem is caused by bug in the jdbc oracle driver:
    oracle.jdbc.dbaccess.DBData.clearItem(DBData.java:431)
    Line 431 looks like:
    /* 431 */ if(m_items == null && i >= m_items.length) // it never works!
    NullPointerException occures when you call
    java.sql.CallableStatement.clearParameters()
    1. Avoid to call this method in your code.
    2. Websphere also calls this method in the WSJdbcConnection.class (while reusing the statement after caching it).
    You may force websphere not to reuse your statement for example by adding timestamp to it as comment:
    String timestamp = String.valueOf(System.currentTimeMillis());
    String myCommand = "call myprocedure( ?, ?) -- " + timestamp);
    conn.prepareCall(myCommand);

  • Package (import oracle.jdbc.driver.*) not found -----URGENT--------

    Hi All,
    i've been using oracle thin driver for oracle 9i server since a long. but now it gives error like
    package import oracle.jdbc.driver.* not found
    it seems some problem in classpath.
    but i've inludeed classes111.zip/classes12.zip to classpath and with this was working fine. dunno what's the problem . kindly mail me at the earliest to:[email protected]
    also i'm working with Tomcat server.
    to run the servlet i don't want to type the absolute url like
    http://localhost:8080/servlet/test rather http://localhost/test .so how to config it . can ne one tell me asap.
    with thanx abd rgds
    Sayed
    so can u tell me

    1. Copy classes12.zip to %TOMCAT_HOME\common\lib
    2. Go to %TOMCAT_HOME\common\lib dir, rename classes12.zip to classes12.jar
    I think someone else has reply same problem before, next time you can do a search before post your problem.

  • Problems with Oracle Thin Driver

    Hi,
    I'm having major problems configuring the Oracle Thin Driver for use
    with CMP Entity Beans. What am I doing wrong?
    Configuration: Windows 2000 Professional, WebLogic 6.1, Oracle 8.1.6,
    Oracle Thin Driver 8.1.7 (classes12.zip is the first thing in the
    classpath)
    I first created the connection pool through the console, here's the
    generated xml:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    MaxCapacity="2" Name="myXAPool"
    Properties="user=XXX;url=jdbc:oracle:thin:@192.168.0.145:1521:db;password=XXX;dataSourceName=myXAPool"
    Targets="server"/>
    The connection pool deployed fine, so I went ahead and created the TX
    DataSource through the console:
    <JDBCTxDataSource JNDIName="mySource" Name="myXASource"
    PoolName="myXAPool" Targets="server"/>
    The log file shows that the TX DataSource was also created. Next step
    was deploying the application. I created a new application through the
    console and uploaded the ear file containing the application (several
    SessionBeans, EntityBeans and a web application). Upon loading the first
    CMP EntityBean (They have "mySource" set as the name of the DataSource
    in the <data-source-name> tag), the following error showed up in the
    log:
    <04.10.2001 09:02:50 CEST> <Info> <EJB> <EJB Deploying file:
    ContractClassStopover.jar>
    <04.10.2001 09:02:51 CEST> <Error> <J2EE> <Error deploying application
    ContractClassStopover:
    Unable to deploy EJB: ContractClassStopoverBean from
    ContractClassStopover.jar:
    The Entity EJB requires the table: CONTRACT_CLASS_STOPOVER to be
    accessible. Please ensure that this table exists and is accessible.
    >
    <04.10.2001 09:02:51 CEST> <Error> <Management> <Error deploying
    application .\config\server\applications\app.ear:
    java.lang.reflect.UndeclaredThrowableException>
    The table exists, so I had a look at the jdbc log file. Here's what
    happened in there:
    DRVR FUNC OracleConnection.OracleConnection(par, pc, autoCommit=false)
    DRVR FUNC
    OracleConnection.initialize(ur="jdbc:oracle:thin:@192.168.0.145:1521:db",
    us="XXX", access)
    DRVR FUNC OracleConnection.initClientDataSupport()
    DRVR OPER OracleConnection.setAutoCommit(autoCommit=false)
    DRVR OPER OracleConnection.getAutoCommit() returned false
    DRVR DBG1 OracleXAResource.start():start
    DRVR DBG1 Should use OracleXid for 8.1.6 database
    DRVR OPER OracleConnection.getTransactionIsolation() returned 2
    DRVR OPER OracleConnection.isReadOnly()
    DRVR OPER OracleConnection.getCatalog()
    DRVR OPER OracleConnection.getAutoCommit() returned false
    DRVR OPER OracleConnection.close()
    DRVR OPER OracleConnection.close()
    DRVR FUNC OracleConnection.OracleConnection(par, pc, autoCommit=false)
    DRVR FUNC
    OracleConnection.initialize(ur="jdbc:oracle:thin:@192.168.0.145:1521:db",
    us="XXX", access)
    DRVR FUNC OracleConnection.initClientDataSupport()
    DRVR OPER OracleConnection.setAutoCommit(autoCommit=false)
    DRVR OPER OracleConnection.getAutoCommit() returned false
    SQLException: SQLState() vendor code(-6)
    java.sql.SQLException: XA error: XAER_PROTO : Routine was invoked in an
    inproper context start() failed on resource 'myXAPool' null
    at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1044)
    at
    weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1010)
    at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:148)
    at
    weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:226)
    at
    weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
    at
    weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
    at
    weblogic.ejb20.utils.TableVerifier.checkTableAndColumns(TableVerifier.java:125)
    at
    weblogic.ejb20.utils.TableVerifier.verifyTableAndColumnsExist(TableVerifier.java:226)
    at
    weblogic.ejb20.utils.TableVerifier.verifyTableExistsAndCreateMaybe(TableVerifier.java:294)
    at
    weblogic.ejb20.cmp11.rdbms.PersistenceManagerImpl.verifyTablesExist(PersistenceManagerImpl.java:172)
    at
    weblogic.ejb20.cmp11.rdbms.PersistenceManagerImpl.setup(PersistenceManagerImpl.java:120)
    at
    weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:197)
    at
    weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:173)
    at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
    at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:793)
    at
    weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1250)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:939)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
    at weblogic.j2ee.Application.addComponent(Application.java:160)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:482)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:926)
    at
    weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:913)
    at
    weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:898)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:618)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy68.addTarget(Unknown Source)
    at
    weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:833)
    at
    weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:930)
    at
    weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:852)
    at
    weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:768)
    at
    weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:701)
    at
    weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:198)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy5.update(Unknown Source)
    at
    weblogic.management.console.webapp._domain.__upload_app._jspService(__upload_app.java:150)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:263)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at
    weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:190)
    at
    weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
    at
    weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
    at
    weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:172)
    at
    weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:263)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2390)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1959)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Can someone please help me figure out what's going wrong here?
    Thanks in advance,
    Nils
    ============================
    [email protected]

    Thanks for the reply!! I was expecting something like this. I will look
    into an upgrade to 8.1.7.
    Take care,
    Nils
    Priscilla Fung wrote:
    >
    Hi,
    You need to use an Oracle 8.1.7 server for XA features. Refer to Third Party
    JDBC XA drivers doc for more info: http://e-docs.bea.com/wls/docs61/jta/thirdpartytx.html#1070650
    Regards,
    Priscilla
    Nils Winkler <[email protected]> wrote:
    Hi,
    I'm having major problems configuring the Oracle Thin Driver for use
    with CMP Entity Beans. What am I doing wrong?
    Configuration: Windows 2000 Professional, WebLogic 6.1, Oracle 8.1.6,
    Oracle Thin Driver 8.1.7 (classes12.zip is the first thing in the
    classpath)
    I first created the connection pool through the console, here's the
    generated xml:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    MaxCapacity="2" Name="myXAPool"
    Properties="user=XXX;url=jdbc:oracle:thin:@192.168.0.145:1521:db;password=XXX;dataSourceName=myXAPool"
    Targets="server"/>
    The connection pool deployed fine, so I went ahead and created the TX
    DataSource through the console:
    <JDBCTxDataSource JNDIName="mySource" Name="myXASource"
    PoolName="myXAPool" Targets="server"/>
    The log file shows that the TX DataSource was also created. Next step
    was deploying the application. I created a new application through the
    console and uploaded the ear file containing the application (several
    SessionBeans, EntityBeans and a web application). Upon loading the first
    CMP EntityBean (They have "mySource" set as the name of the DataSource
    in the <data-source-name> tag), the following error showed up in the
    log:
    <04.10.2001 09:02:50 CEST> <Info> <EJB> <EJB Deploying file:
    ContractClassStopover.jar>
    <04.10.2001 09:02:51 CEST> <Error> <J2EE> <Error deploying application
    ContractClassStopover:
    Unable to deploy EJB: ContractClassStopoverBean from
    ContractClassStopover.jar:
    The Entity EJB requires the table: CONTRACT_CLASS_STOPOVER to be
    accessible. Please ensure that this table exists and is accessible.
    >
    <04.10.2001 09:02:51 CEST> <Error> <Management> <Error deploying
    application .\config\server\applications\app.ear:
    java.lang.reflect.UndeclaredThrowableException>
    The table exists, so I had a look at the jdbc log file. Here's what
    happened in there:
    DRVR FUNC OracleConnection.OracleConnection(par, pc, autoCommit=false)
    DRVR FUNC
    OracleConnection.initialize(ur="jdbc:oracle:thin:@192.168.0.145:1521:db",
    us="XXX", access)
    DRVR FUNC OracleConnection.initClientDataSupport()
    DRVR OPER OracleConnection.setAutoCommit(autoCommit=false)
    DRVR OPER OracleConnection.getAutoCommit() returned false
    DRVR DBG1 OracleXAResource.start():start
    DRVR DBG1 Should use OracleXid for 8.1.6 database
    DRVR OPER OracleConnection.getTransactionIsolation() returned 2
    DRVR OPER OracleConnection.isReadOnly()
    DRVR OPER OracleConnection.getCatalog()
    DRVR OPER OracleConnection.getAutoCommit() returned false
    DRVR OPER OracleConnection.close()
    DRVR OPER OracleConnection.close()
    DRVR FUNC OracleConnection.OracleConnection(par, pc, autoCommit=false)
    DRVR FUNC
    OracleConnection.initialize(ur="jdbc:oracle:thin:@192.168.0.145:1521:db",
    us="XXX", access)
    DRVR FUNC OracleConnection.initClientDataSupport()
    DRVR OPER OracleConnection.setAutoCommit(autoCommit=false)
    DRVR OPER OracleConnection.getAutoCommit() returned false
    SQLException: SQLState() vendor code(-6)
    java.sql.SQLException: XA error: XAER_PROTO : Routine was invoked in
    an
    inproper context start() failed on resource 'myXAPool' null
    at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1044)
    at
    weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1010)
    at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:148)
    at
    weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:226)
    at
    weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
    at
    weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
    at
    weblogic.ejb20.utils.TableVerifier.checkTableAndColumns(TableVerifier.java:125)
    at
    weblogic.ejb20.utils.TableVerifier.verifyTableAndColumnsExist(TableVerifier.java:226)
    at
    weblogic.ejb20.utils.TableVerifier.verifyTableExistsAndCreateMaybe(TableVerifier.java:294)
    at
    weblogic.ejb20.cmp11.rdbms.PersistenceManagerImpl.verifyTablesExist(PersistenceManagerImpl.java:172)
    at
    weblogic.ejb20.cmp11.rdbms.PersistenceManagerImpl.setup(PersistenceManagerImpl.java:120)
    at
    weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:197)
    at
    weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:173)
    at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
    at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:793)
    at
    weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1250)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:939)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
    at weblogic.j2ee.Application.addComponent(Application.java:160)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:482)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:926)
    at
    weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:913)
    at
    weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:898)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:618)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy68.addTarget(Unknown Source)
    at
    weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:833)
    at
    weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:930)
    at
    weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:852)
    at
    weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:768)
    at
    weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:701)
    at
    weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:198)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy5.update(Unknown Source)
    at
    weblogic.management.console.webapp._domain.__upload_app._jspService(__upload_app.java:150)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:263)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at
    weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:190)
    at
    weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
    at
    weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
    at
    weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:172)
    at
    weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:263)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2390)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1959)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Can someone please help me figure out what's going wrong here?
    Thanks in advance,
    Nils
    ============================
    [email protected]
    ============================
    [email protected]

  • Update Batching With Oracle Thin Driver

    executeBatch() method throws missing IN or Out Parameters when used with Oracle
    thin driver(jdbc.oracle.driver.OracleDriver)

    Thanks for the reply. But, I tried it and I still get the same problem. Now
    I am running on Solaris 7. Does that make a difference?
    -Sudheendra
    "Slava Imeshev" <[email protected]> wrote in message
    news:[email protected]..
    Hi Sudheendra,
    Here is the patch for 5.1 put it as the first thing
    in weblogic.classpath.
    Regards,
    Slava Imeshev
    "Sudheendra Galgali" <[email protected]> wrote in message
    news:3b69a4be$[email protected]..
    I am having a similar problem with WL 5.1, service pack 9 with Oracle Thin
    drivers. I am unable to find patch CR047274 either. Help please!
    "Soumik" <[email protected]> wrote in message
    news:[email protected]..
    executeBatch() method throws missing IN or Out Parameters when used with
    Oracle
    thin driver(jdbc.oracle.driver.OracleDriver)

  • Performance problems using WLS6.1 with the thin driver for Ora9i from OTN

    Hello everyone,
    Has anyone been experimenting with the thin driver for Oracle 9i under WLS6.1. I got it running, but
    I get extremely bad performance when having multiple concurrent accesses. It works more or less in
    single user mode. Also it seems not to support XA transactions?
    When could we expect the driver from BEA to be out?
    Thanks in advance!
    Samuel Kounev
    TU-Darmstadt, Germany

    I had done this from the very beginning, but I was still getting very bad performance under
    concurrent accesses. I even followed Sree's instructions and removed the old thin driver from
    weblogic.jar, but this didn't help. I am now trying to get the OCI driver for 9i running and hope
    this will solve the problem.
    Samuel
    Tamilselvan Ramasamy wrote:
    You have to use Oracle's Oracle 9i thin driver .
    put this driver infront of the classpath i.e before weblogic_sp.jar and
    weblogic.jar
    /selvan
    "Sree Bodapati" <[email protected]> wrote in message
    news:[email protected]..
    The BEA driver is available in WLS6.1SP2 which is GA.
    hth
    sree
    "Samuel Kounev" <[email protected]> wrote in message
    news:[email protected]..
    Hello everyone,
    Has anyone been experimenting with the thin driver for Oracle 9i under
    WLS6.1. I got it running, but
    I get extremely bad performance when having multiple concurrent accesses.
    It
    works more or less in
    single user mode. Also it seems not to support XA transactions?
    When could we expect the driver from BEA to be out?
    Thanks in advance!
    Samuel Kounev
    TU-Darmstadt, Germany

  • JDBC Thin Driver for Tomcat 6

    I just upgraded to Tomcat 6. For older version of Tomcat I was using ojdbc14.jar and for Tomcat 6 I am still using ojdbc14.jar.
    Everything is working but wanted to know if there is a newer version of the Oracle Thin Driver for JDBC?

    There is one version per release of the database (with sometimes minor releases for bugfixes released later. which will have the same filename but different internal version numbers).
    Only exception I know of is Oracle 11 which ships with both 1.5 and 1.6 compiled drivers.

  • Specifying "ARRAYSIZE" in Oracle ODBC Driver for 7.3.4

    Is it possible to specify the ARRAYSIZE parameter in the Oracle ODBC Driver for Oracle 7.3.4?
    Other vendors provide this facility when creating the data source using ODBC administrator.
    If anyone can clarify, it will be a great help.
    Regards,
    Premanand

    Hello,
    Take a loot at http://www.connx-net.com/rdb.htm they have a 64 bit ODBC OLE DB JBC and .NET solution.
    Regards,
    Ant

  • Can't create connection pool using weblogic 6.1 with Oracle thin driver

    Hi !
    I have tried to create a connection pool from adminconsole. My CLASSPATH setting
    is as follows :
    F:\SOAP\soap-2_2\lib;F:\SOAP\soap-2_2;
    D:\Oracle\Ora81\jdbc\lib\classes12.zip;
    D:\Oracle\Ora81\jdbc\lib\nls_charset12.zip;
    D:\Oracle\Ora81\jdbc\lib\classes111.zip;
    F:\SOAP\soap-2_2\lib\jaf-1.0.1\activation.jar;
    D:\Oracle\Ora8\Apache\Jsdk\src\javax\servlet\http;
    D:\Oracle\Ora81\Apache\Jsdk\src\javax\servlet;
    D:\Oracle\Ora81\lib;
    F:\ant\jakarta-ant1.\bin;
    E:\weblogic\oci\classes;
    E:\weblogic\oci\classes\weblogic\xml\license;
    E:\weblogic\oci\license;
    E:\bea\wlserver6.1\lib;
    E:\PetStoreHome\petstore1.3;
    Following is the configuration.
    #Oracle thin driver Method #2
    weblogic.jdbc.connectionPool.thin=\      
    url=jdbc:oracle:thin:@test:1521:PROJECT,\      
    driver=oracle.jdbc.driver.OracleDriver,\
         initialCapacity=4,\
         maxCapacity=10,\
         capacityIncrement=1,\
         props=user=xxx;password=xxx;server=test
    #Add a TXDataSource for the connection pool:
    weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.thin=thin
    # Add an ACL for the connection pool:
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.thin=everyone
    I did append the file weblogic.properties with the above config. Now when I start
    the Weblogic server I get the following error :
    Starting WebLogic Server ....
    <Nov 29, 2001 2:24:16 PM EST> <Notice> <Management> <Loading configuration file
    .\config\petstore\config.xml ...>
    <Nov 29, 2001 2:24:22 PM EST> <Notice> <WebLogicServer> <Starting WebLogic Admin
    Server "petstoreServer" for domain "petstore">
    <Nov 29, 2001 2:24:26 PM EST> <Notice> <Management> <Starting discovery of Manag
    ed Server... This feature is on by default, you may turn this off by passing -Dw
    eblogic.management.discover=false>
    <Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data Source creation:
    weblogic.common.ResourceException: DataSource(jdbcthin.SignOnDB) can't be creat
    ed with non-existent Pool (connection or multi) (thin)>
    <Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data Source creation:
    weblogic.common.ResourceException: DataSource(jdbcthin.EstoreDB) can't be creat
    ed with non-existent Pool (connection or multi) (thin)>
    <Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data Source creation:
    weblogic.common.ResourceException: DataSource(jdbcthin.InventoryDB) can't be
    cr
    eated with non-existent Pool (connection or multi) (thin)>
    <Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data Source creation:
    weblogic.common.ResourceException: DataSource(weblogic.jdbc.jts.thin) can't be
    created with non-existent Pool (connection or multi) (thin)>
    <Nov 29, 2001 2:24:41 PM EST> <Notice> <Management> <Application Poller not star
    ted for production server.>
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    After the server has booted, your browser should
    automatically launch and point to the WebLogic Server
    Tour running on this server. If your browser fails to
    launch, point your browser to the URL
    "http://burtsun:7001"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    <Nov 29, 2001 2:24:41 PM EST> <Notice> <WebLogicServer> <ListenThread listening
    on port 7001>
    <Nov 29, 2001 2:24:41 PM EST> <Notice> <WebLogicServer> <SSLListenThread listeni
    ng on port 7002>
    <Nov 29, 2001 2:24:42 PM EST> <Notice> <WebLogicServer> <Started WebLogic Admin
    Server "petstoreServer" for domain "petstore" running in Production Mode>
    Could anyone please help me ?
    Thanks
    ..Madhuri

    Madhuri wrote:
    >
    Hi Joe !
    I didn't get what you would like to point out. Actully, I am using same config.,
    but not to disclose the info. I gave you @test and username/password xxx/xxx.Ok. Now, assuming your pool looks like what I showed, the issue is probably
    that there are multiple Oracle driver zips around, and your standlaone program
    is using a different, newer, better one than the server. Our weblogic jar files
    include a classes12.zip Oracle thin driver, but there are multiple versions of
    classes12.zip, and the latest from oracle is better than the one we sealed into
    our packaging. Please use jave -verbose to identify exactly which Oracle sip file
    you are using in the successful case, then make sure this zip file comes before
    any weblogic stuff in your weblogic server's classpath, so we'll use the same
    driver. This should work. Edit the script you sue to start weblogic to verify
    the classpath does end up with the oracle driver ahead of all weblogic stuff.
    Joe
    >
    Please let me know.
    Thanks
    .Madhuri
    Joseph Weinstein <[email protected]> wrote:
    Madhuri wrote:
    Hi Joe !
    Here is the sample java code. Please let me know how I can test thisin weblogic
    6.1.
    Thanks
    .MadhuriWell fine! That was easy. Your pool definition didn't have the same URL
    or
    user or password as this code. Try this for your pool definition:
    weblogic.jdbc.connectionPool.thin=\
    url=jdbc:oracle:thin:@adl-gbsdevel:1521:PROJECT,\
    driver=oracle.jdbc.driver.OracleDriver,\
    initialCapacity=10,\
    maxCapacity=10,\
    capacityIncrement=1,\
    testConnsOnReserve=true,\
    testTable=dual,\
    props=user=mkelkar;password=mkelkar
    Let me know,,,
    Joe
    Joseph Weinstein <[email protected]> wrote:
    The key is in the log:
    Could not create pool connection.
    The DBMS driver exception was:
    java.sql.SQLException: invalid arguments in call
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
    Now we need to simplify the problem. Please make a simple 15-line
    standalone
    Java program like you'd find with the Oracle driver's examples, with
    no
    weblogic code in the picture. Just make a JDBC connection using Oracle's
    driver, and show me that code. Then I can translate that into a pool
    definition.
    Joe
    Madhuri wrote:
    Hi Joe !
    Thanks for your prompt reply. I tried the way you suggested but
    it
    still it gives
    me the same error. I am attching here the weblogic.log file.
    Thanks again
    ..Madhuri
    Joseph Weinstein <[email protected]> wrote:
    We'd want to see the log during booting, where the pool
    is being created to see why that failed. Try a pool
    definition with no blank lines, no whitespace at the
    end of lines, and no server property. The thin driver
    doesn't like that:
    weblogic.jdbc.connectionPool.thin=\
    url=jdbc:oracle:thin:@test:1521:PROJECT,\
    driver=oracle.jdbc.driver.OracleDriver,\
    initialCapacity=4,\
    maxCapacity=10,\
    capacityIncrement=1,\
    props=user=xxx;password=xxx
    Joe
    Madhuri wrote:
    Hi !
    I have tried to create a connection pool from adminconsole. My
    CLASSPATH
    setting
    is as follows :
    F:\SOAP\soap-2_2\lib;F:\SOAP\soap-2_2;
    D:\Oracle\Ora81\jdbc\lib\classes12.zip;
    D:\Oracle\Ora81\jdbc\lib\nls_charset12.zip;
    D:\Oracle\Ora81\jdbc\lib\classes111.zip;
    F:\SOAP\soap-2_2\lib\jaf-1.0.1\activation.jar;
    D:\Oracle\Ora8\Apache\Jsdk\src\javax\servlet\http;
    D:\Oracle\Ora81\Apache\Jsdk\src\javax\servlet;
    D:\Oracle\Ora81\lib;
    F:\ant\jakarta-ant1.\bin;
    E:\weblogic\oci\classes;
    E:\weblogic\oci\classes\weblogic\xml\license;
    E:\weblogic\oci\license;
    E:\bea\wlserver6.1\lib;
    E:\PetStoreHome\petstore1.3;
    Following is the configuration.
    #Oracle thin driver Method #2
    weblogic.jdbc.connectionPool.thin=\
    url=jdbc:oracle:thin:@test:1521:PROJECT,\
    driver=oracle.jdbc.driver.OracleDriver,\
    initialCapacity=4,\
    maxCapacity=10,\
    capacityIncrement=1,\
    props=user=xxx;password=xxx;server=test
    #Add a TXDataSource for the connection pool:
    weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.thin=thin
    # Add an ACL for the connection pool:
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.thin=everyone
    I did append the file weblogic.properties with the above config.
    Now
    when I start
    the Weblogic server I get the following error :
    Starting WebLogic Server ....
    <Nov 29, 2001 2:24:16 PM EST> <Notice> <Management> <Loading
    configuration
    file
    \config\petstore\config.xml ...>
    <Nov 29, 2001 2:24:22 PM EST> <Notice> <WebLogicServer> <Starting
    WebLogic
    Admin
    Server "petstoreServer" for domain "petstore">
    <Nov 29, 2001 2:24:26 PM EST> <Notice> <Management> <Starting
    discovery
    of Manag
    ed Server... This feature is on by default, you may turn this
    off
    by
    passing -Dw
    eblogic.management.discover=false>
    <Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data
    Source
    creation:
    weblogic.common.ResourceException: DataSource(jdbcthin.SignOnDB)
    can't
    be creat
    ed with non-existent Pool (connection or multi) (thin)>
    <Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data
    Source
    creation:
    weblogic.common.ResourceException: DataSource(jdbcthin.EstoreDB)
    can't
    be creat
    ed with non-existent Pool (connection or multi) (thin)>
    <Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data
    Source
    creation:
    weblogic.common.ResourceException: DataSource(jdbcthin.InventoryDB)can't be
    cr
    eated with non-existent Pool (connection or multi) (thin)>
    <Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data
    Source
    creation:
    weblogic.common.ResourceException: DataSource(weblogic.jdbc.jts.thin)can't be
    created with non-existent Pool (connection or multi) (thin)>
    <Nov 29, 2001 2:24:41 PM EST> <Notice> <Management> <Application
    Poller
    not star
    ted for production server.>
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    After the server has booted, your browser should
    automatically launch and point to the WebLogic Server
    Tour running on this server. If your browser fails to
    launch, point your browser to the URL
    "http://burtsun:7001"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    <Nov 29, 2001 2:24:41 PM EST> <Notice> <WebLogicServer> <ListenThreadlistening
    on port 7001>
    <Nov 29, 2001 2:24:41 PM EST> <Notice> <WebLogicServer> <SSLListenThreadlisteni
    ng on port 7002>
    <Nov 29, 2001 2:24:42 PM EST> <Notice> <WebLogicServer> <Started
    WebLogic
    Admin
    Server "petstoreServer" for domain "petstore" running in ProductionMode>
    Could anyone please help me ?
    Thanks
    ..Madhuri
    Name: weblogic.log
    weblogic.log Type: Text Document (application/x-unknown-content-type-txtfile)
    Encoding: base64
    Name: PrintColumns.java
    PrintColumns.java Type: Visual Cafe File (application/x-unknown-content-type-VisualCafeFile.Document)
    Encoding: base64

  • CachedRowSet problem in Weblogic 6.1 and Oracle thin driver 9.0.1

    Has anyone used the CachedRowSet class successfully? (this classes are
    new and from the JDBC extension pack)
    I am experiencing "Not in a transaction" errors when executing
    cachedrowset.populate(resultset), even though I'm inside a correct
    ut.begin and ut.commit transaction.
    Note I don't have these problems when I don't use the CachedRowSet
    classes.
    If I remove the setFetchSize(50) line, then I receive the ORA-01002:
    fetch out of sequence error, which is discussed in another post on
    this newsgroup.
    I don't have any of these problems at all, if I use the Oracle Thin
    Driver directly (i.e. not using Weblogic 6.1).
    -H
    Example of code:
    stmt = getConnection().createStatement();
    stmt.setFetchSize(50);
    stmt.executeQuery("SELECT * FROM ASSET");
    rs = stmt.getResultSet();
    crs = new CachedRowSet();
    crs.populate(rs);

    Hi Arturo,
    What kind of a problem do you have? Any stacktraces?
    Regards,
    Slava Imeshev
    "Arturo Fernandez" <[email protected]> wrote in message
    news:[email protected]..
    Hi! I have a problem with CLOB column in Oracle 8.1.7. My enviroment
    is:
    Windows 2000, BEA WLS 6.1 and Oracle 8.1.7. I'm trying to use
    'classes12.zip' provided by Oracle. I added 'classes12.zip' to
    CLASSPATH after than 'weblogic.jar' in my startup server script, but
    it fails when trying to retrieve a CLOB data from database. Script
    includes:
    setCLASSPATH=.\classes12_01.zip;.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;
    >
    But this driver and the code runs sucessfully with the same database
    and weblogic 5.1. I'm interesting in use this driver and this code
    because i'm trying to migrate two applications from WLS 5.1 to WLS 6.1
    I cannot find a solution.
    Can everybody help me, please? It's urgent for me...

  • Using oracle thin driver from Weblogic server 6.1

    Hi
    I need to know which driver is best for establishing JDBC Connection i.e.
    whether to use JDriver provided with Weblogic or to go using Oracle thin driver.
    Can some one tell the detailed procedure involved in configuring oracle thin driver
    in Weblogicserver 6.1.
    Thanks in advance,
    S Gopikrishna

    I would recommend using the thin driver where ever possible, their are
    certain problems with thin driver which are more in the area of XA support
    you can check weblogic documentation for pointers on this. Oracles latest
    thin driver is pretty stable as they have fixed a bunch of problems.
    heres how to use thin driver:
    create the connection pool using the following url
    jdbc:oracle:thin:@<mc-name or ip-address>:<port-no>:<oracle sid>
    and driver: oracle.jdbc.driver.OracleDriver
    You dont have to install the thin driver its bundled with the product.
    hth
    sree
    "S Gopikrishna" <[email protected]> wrote in message
    news:3c34a0e5$[email protected]..
    Hi
    I need to know which driver is best for establishing JDBC Connection
    i.e.
    whether to use JDriver provided with Weblogic or to go using Oracle thin
    driver.
    Can some one tell the detailed procedure involved in configuring oracle thin
    driver
    in Weblogicserver 6.1.
    Thanks in advance,
    S Gopikrishna

  • WebLogic 5.1.0 & Oracle 8.1.7 thin driver for jdk 1.3.1

    We're currently using Oracle 8.1.6, and need to upgrade to 8.1.7.
    Platform: Solaris 2.6
    WebLogic: 5.1 Service Pack 9
    JDK : 1.3.1
    Regarding the thin drivers, my understanding is that w/ 8.1.7, we can use either
    8.1.7 OR 9.0.1 thin drivers. Has anyone seen issues using either thin driver
    w/ Oracle 8.1.7 and WebLogic?
    Thanks in advance!
    -Chad Baker

    Regarding the thin drivers, my understanding is that w/ 8.1.7, we can use either
    8.1.7 OR 9.0.1 thin drivers. Has anyone seen issues using either thin driver
    w/ Oracle 8.1.7 and WebLogic?Chad,
    We've used both thin drivers successfully under WebLogic 5.1, and
    have been using the 9.0.1 thin driver under Weblogic 6.1 without any
    problems. We moved to the 9.0.1 driver because it's the first driver
    version to implement
    PreparedStatement.setTimestamp(Timestamp,Calendar).
    Recently, we started looking at using JMS and may need to use
    distributed
    transactions, and we're concerned about transaction support in the
    thin
    driver. Various WebLogic docs, like
    http://e-docs.bea.com/wls/docs61///notes/issues.html#1048698, mention
    that 8.1.7 has XA threading issues that cause problems in distributed
    transactions. In one place, they mention that they may have a
    workaround, but it's unclear what the status of that is. And it looks
    like they definitely haven't gotten to testing
    the 9.0.1 driver. If you're interested in distributed transactions,
    you might want to investigate that first.
    Jim

Maybe you are looking for