Known Oracle Thin Driver Issue :: Need an Equivalent for the Class

Hi,
We are working on an effort to migrate a J2EE application from WebLogic to OC4J. We noticed that one of the classes used the WebLogic implementation of the BLOB Data Type ( weblogic.jdbc.vendor.oracle.OracleThinBlob ). The original developers decided to use this class against the Oracle SQL API after reading this link :-
http://support.bea.com/application_content/product_portlets/support_patterns/wls/CLOBBLOBDataTypeHandlingIssuesPattern.html#Known_Oracle_Thin_Driver_Issue
We are porting our code to Oracle Application Server 10.1.3.1.0 that uses the latest JDBC Implemation Code ( The Manifest FIle lists the version as Oracle JDBC Driver version - 10.1.0.5.0 ).
Can you please tell me if We may have a serious impact is using Oracle SQL API instead of the WebLogic BLOB Implementation ?
Regards,
Sandeep

As mentionned in the link, this issue is fixed in 9.2 and 10g driver.
Kuassi

Similar Messages

  • 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

  • Web Logic 6.1 JDBC Pooling with the Oracle Thin Driver

    Hi,
    We're slowly getting through a WebLogic 4.5.1 to 6.1 conversion for a small application
    at my company. Initially, we had trouble getting the Oracle thin driver working.
    We've finally cracked this nut. Now we're trying to get pooling working, and
    cannot find an example of doing this with the Oracle thin driver.
    Would anyone be able to provide:
    1. the portion of the config.xml that pertains to building a connection pool using
    the Oracle thin driver
    2. the two lines of code for loading the driver and getting a connection from
    this pool
    i.e.
    Driver d = (Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
    Connection c = d.connect("jdbc:weblogic:pool:myPool", null);
    Thanks very much!
    Jeff Ryan
    The Hartford

    "Jeff Ryan" <[email protected]> wrote:
    >
    1. the portion of the config.xml that pertains to building a connection
    pool using
    the Oracle thin driver
    You don't usually edit the config.xml unless it is absolutely necessar. Instead,
    you can config the pool in the GUI admin console, quite easily. After you successfully
    configed the pool in the console, it is written into the config.xml file for you.
    Only thing special when config the pool is the name of the driver and the url.
    url: jdbc:oracle:thin@dbhost:dbport:dbinstance
    driver: oracle.jdbc.driver.OracleDriver
    If you prefer, you can also config the pool from the command line. It is detailed
    in the "Weblogic Server Command-line Interface Reference".
    2. the two lines of code for loading the driver and getting a connection
    from
    this pool
    i.e.
    Driver d = (Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
    Connection c = d.connect("jdbc:weblogic:pool:myPool", null);
    Again, you don't use the connection directly. Instead, you use "Data Source".
    Data source in weblogic is just a connection object factory associated with a
    JNDI name. You can therefore lookup the data source with the JNDI name and from
    the data source object, you get the connectin object. No need to explicitly load
    the driver class.
    There are plenty of example codes available in the weblogic examples installed
    with 6.1, that uses the data source.
    Charles

  • Jdbc connection using oracle thin driver( using jdk1.4 and oracle8 )

    hello ..
    while i was tring to connection using oracle thin driver and jdk1.4 am getting the below error message. i have set the class path for the driver also. am using oracle8 personal edition and jdk1.4.
    [java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
            at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
            at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
            at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:333)
            at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:404)
            at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.ja
    va:468)
            at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
            at java.sql.DriverManager.getConnection(DriverManager.java:512)
            at java.sql.DriverManager.getConnection(DriverManager.java:171)
            at Connexa.main(Connexa.java:18)[/b]
    Press any key to continue...
    my program is....
    import java.sql.*;                                          
    import java.io.*;
    import java.util.*;
    import oracle.jdbc.driver.*;
    // needed for new BFILE class
    import oracle.sql.*;
       public class Connexa {
      public static void main (String args []) throws Exception {
            Statement stmt=null; 
      try{
        // Load the Oracle JDBC driver                            
        //DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
    Class.forName("oracle.jdbc.driver.OracleDriver");
        // Connect to the database
        // You can put a database name after the @ sign in the connection URL.
    Connection conn =
    DriverManager.getConnection("jdbc:oracle:thin:@127.0.0.1:1521:orcl","scott","tiger");
        //Connection conn =
        //  DriverManager.getConnection ("jdbc:odbc:datasource", "system", "manager");
        stmt = conn.createStatement ();
    catch (SQLException e)
          e.printStackTrace();

    The code itself is fine; the problem is with one of:
    1) the connection URL
    2) intermediate networking
    3) the database itself
    1) your connection URL is "jdbc:oracle:thin:@127.0.0.1:1521:orcl"
    - is Oracle really running on the default port, 1521
    - is the installation SID really "orcl"
    2) lots of possibilities, but only a couple are likely
    - is TCP/IP configured and running on your host
    - is there a persoanl firewall rpduct running? perhaps it's blocking the connection
    3) Is Oracle running?
    Is the listener running?

  • 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.

  • 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

  • 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]

  • JDBC logging disabled with Oracle thin driver

    Hi,
    I am trying to turn on JDBC logging through the weblogic console application (WL
    6.1 with CMP). In the jdbc log file I do not see the SQL statments.
    It looks like logging is somehow disabled (check one of the logs statements below)
    by some means. Any ideas, I am making use of oracle thin driver.
    Thanks
    Mohit
    Following log messages are generated!!!!!!
    DriverManager.initialize: jdbc.drivers = null
    JDBC DriverManager initialized
    registerDriver: driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
    DriverManager.getDriver("jdbc:oracle:thin:@(description=(address=(host=192.168.161.120)(protocol=tcp)(port=1521))(connect_data=(sid=DOPERS01)))")
    trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
    getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
    DRVR OPER Disabled logging
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    registerDriver: driver[className=weblogic.jdbc.jts.Driver,weblogic.jdbc.jts.Driver@13eb9c]
    registerDriver: driver[className=weblogic.jdbc.pool.Driver,weblogic.jdbc.pool.Driver@4f83d1]
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing

    Mohit,
    Remove oracle/jdbc/driver/OracleLog from classes12.zip, and it should
    work (it needs to pick up only this class from weblogic.jar).
    Paul
    Hi,
    I am trying to turn on JDBC logging through the weblogic console application (WL
    6.1 with CMP). In the jdbc log file I do not see the SQL statments.
    It looks like logging is somehow disabled (check one of the logs statements below)
    by some means. Any ideas, I am making use of oracle thin driver.
    Thanks
    Mohit
    Following log messages are generated!!!!!!
    DriverManager.initialize: jdbc.drivers = null
    JDBC DriverManager initialized
    registerDriver: driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
    DriverManager.getDriver("jdbc:oracle:thin:@(description=(address=(host=192.168.161.120)(protocol=tcp)(port=1521))(connect_data=(sid=DOPERS01)))")
    trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
    getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
    DRVR OPER Disabled logging
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    registerDriver: driver[className=weblogic.jdbc.jts.Driver,weblogic.jdbc.jts.Driver@13eb9c]
    registerDriver: driver[className=weblogic.jdbc.pool.Driver,weblogic.jdbc.pool.Driver@4f83d1]
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing

  • Using oracle thin driver

    Hi,
    I have a problem in using oracle thin driver,ive downloaded oracle thin driver and classpath has been set for classes12.zip.Iam trying to connect to server:teams sid:teams .
    the following code compiles and throws error @ runtime
    ************************ code****************8
    import java.sql.*;
    public class ocdtest {
    public static void main(String arg[]){
    try {
    DriverManager.registerDriver (new oracle.jdbc.driver.OracleDriver());
    Connection conn = DriverManager.getConnection ("jdbc:oracle:thin:@teams:1521:teams", "raghu", "startoracle");
    Statement stmt = conn.createStatement ();
    ResultSet rset = stmt.executeQuery ("select login_name from login");
    while (rset.next ()){
    System.out.println (rset.getString ("login_name"));
    }catch(Exception e){
    System.out.println(e);
    ********************* code *********************************
    ********************** Exception *************************
    Exception in thread "main" java.lang.UnsatisfiedLinkError: get_env_handle
    at oracle.jdbc.oci8.OCIEnv.get_env_handle(Native Method)
    at oracle.jdbc.oci8.OCIEnv.getEnvHandle(OCIEnv.java:70)
    at oracle.jdbc.oci8.OCIDBAccess.logon(OCIDBAccess.java:359)
    at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:252)
    at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.ja
    va:365)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:260)
    at java.sql.DriverManager.getConnection(DriverManager.java:512)
    at java.sql.DriverManager.getConnection(DriverManager.java:172)
    at ocdtest.main(ocdtest.java:11)
    *******************************Exception **********************
    can anyone help me how to solve this problem.
    thanks in advance
    karthik

    Hi,
    The following code works
    import java.sql.*;
    public class ocdtest {
    public static void main(String arg[]){
    try {
              Class.forName("oracle.jdbc.driver.OracleDriver");
              Connection con=DriverManager.getConnection("jdbc:oracle:thin:@teams:1521:teams", "raghu", "startoracle");
              Statement s=con.createStatement();
              System.out.println("connected");
              ResultSet rs=s.executeQuery("select login_name from login where login_name='tom'");
              System.out.println("resultset");
              while(rs.next()){
                   System.out.println(rs.getString("login_name"));
    }catch(Exception e){
              System.out.println(e);
    all u need to download is classes12.zip and the patch for this zip .
    thanks and regards
    Karthik

  • Oracle/thin driver slow

    I am running a query on oracle 8.1.7.3 database. when I run it from the command line sqlplus it returns with the result in .5 seconds. when I try the same query from the jdbc thin driver ( 9.0.1 ), it just keeps waiting for 30 seconds.
    Is there a known problem with the oracle thin driver ? if so is there a way out of this ?
    Thanks,
    Dash.

    There's no reason why a driver would simply get slower from one version to another. The only explanation I see for this is that you are using scrollable or updatable result sets which is not quite the same as running the query. A scrollable/updatable result set creates a cursor with your query so it's way slower than a forward-only, read-only result set.
    As a result, the reason why an older version of a driver might be faster would be that it either did not implement scrollable result sets or it has introduced an option (in the URL or connection properties) to use regular or cursor result sets (e.g. the Microsoft and Data Direct drivers have an option for the type of result sets to be used; if this option is set to cursor, you can use any number of Statements per Connection at the cost of performance).
    Alin.

  • Error in creating Connection Pool using Oracle Thin Driver

    Hi,
    I am trying to create a connection pool in WS 5.1 with sp #6 using Oracle Thin Driver (oracle.jdbc.driver.OracleDriver) on a Sun box. But I am able to create the pool using weblogic.jdbc.oci.Driver. I get an DBMS Driver exception when I use thin driver. I have LD library path and weblogic class path set correctly. WL shows the following exception :
    weblogic.common.ResourceException: weblogic.common.ResourceException:
    Could not create pool connection. The DBMS driver exception was:
    java.sql.SQLException: Io exception: The Network Adapter could not establish the
    connection
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java)
    at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java)
    at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java)
    Any help on this is greatly appreciated.
    Thanks,
    Ramu

    Hi Ramu,
    Please post your connection pool setting here. You might have missed some
    port/server info. The driver is unable to connect to the db server here.
    sree
    "Ramu" <[email protected]> wrote in message
    news:3d5bbc3a$[email protected]..
    >
    Yes. I am trying to create a connection pool in weblogic and I have theweblogic
    class path setup correctly. It points to classes111.zip andnls_charset11.zip.
    >
    -Ramu
    "Neo Gigs" <[email protected]> wrote:
    Did you setup the JDBC library classpath correctly?
    For me, e.g. Oracle 7.3.4, the classpath should be:
    export CLASSPATH = /oracle7.3.4/jdbc/lib/classes.zip:%CLASSPATH%
    Noted that the JDBC classpath must be the first classpath element in
    the export
    statement.
    Neo

  • Using oracle thin driver with to_char gives invalid column name

    select x,y,z, to_char(event_time,'YYYY-MMM-DD') from eventtable;
    if i execute the above query using oracle thin driver it gives me invalid column name. It works fine if i use weblogic driver. So what could be the problem ???
    thanks.

    Sorry , forgot to add that 'YYYY-MM-DD' or 'YYYY-Month-DD' or 'Year-MM-DD' or 'Year-Month-DD' are also allowed(please cheek also for other combinations), not 'YYYY-MMM-DD'.
    Thanks

  • 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...

  • Multiple ResultSets with Oracle Thin Driver.

    Hi,
    I am using Oracle Thin Driver to Connect to the Oracle Database (8.1.7). I wanted to take advantage
    of the multiple Resultsets Scenario for fetching Data from the DB. Please have a look at the code
    fragment below.
    String sql = "select * from TAB1; select * from TAB2";
    Connection conn = getConnection();
    PreparedStatement stmnt = conn.prepareStatement(sql);
    stmnt.execute();
    However , I am getting the following Error.
    java.sql.SQLException: ORA-00911: invalid character
    Could anyone give me the possible reason/corrected syntax for the SQL.
    Thanks for any help in advance.

    It's unclear what your problem is...
    However...
    Oracle will only execute one SQL statement at a time in a Statement or PreparedStatement; therefore these can only return a single ResultSet.
    However, an Oracle stored procedure can be written to return multiple results; it can therefore be run from a CallableStatement and getMoreResults() is then used to get the additional ResultSet data.
    An example of doing this is here:
    http://edocs.beasys.com/wls/docs81/jdbc_drivers/oracle.html
    scroll towards the bottom and look for Listing 5-3

  • How to use oracle thin driver?...pls help

    Hello. I am trying to insert a word file into my Oracle 9i database using JSP. I have tomcat running as my standalone server. So far, i have been using the sun.jdbc.odbc driver to implement all my DB accesses. Recently however, i found out that in order to use Oracle specific objects such as BLOBS or BFILES, i have to use the oracle thin driver or OCI driver.
    So far, i have downloaded the thin driver and put it into the tomcat shared/common folder and also put the .jar file into my classpath. Now, i am having trouble as to how to call the oracle thin driver inside my JSP code.
    My previous code read as:
    Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
    Connection con = DriverManager.getConnection("jdbc:odbc:Andy","user","pass");
    How do i switch over to the oracle thin driver in JSP? Any help would be much appreciated. Thank you
    Andrew

    Class.forName ("oracle.jdbc.driver.OracleDriver");
    Connection conn = DriverManager.getConnection ("jdbc:oracle:thin:@hostname:port:SSID", "user", "password");

Maybe you are looking for