Connection Pool Failure: "No suitable driver"

Hi,
Upon server startup, I get the following result:
<Nov 7, 2001 4:18:32 PM CST> <Error> <JDBC> <Cannot startup connection pool "ora
cleTrufflePool" No suitable driver>
I assumed it was a path problem, but in the startWebLogic.cmd script I've set the PATH and CLASSPATH variables to the same as in a separate command window that can successfully dbping the Oracle db.
One thing I completely don't understand is what the URL value should be for the pool, and I can't see a pattern in the examples and docs I've found on this. Here are my pool settings, at any rate:
Name: oracleTrufflePool
URL: myOracleServerName
Driver Classname: weblogic.jdbc.oci.Driver
Properties:
user=user
password=password
server=myOracleServerName
ACLName: user
Password: password
As you can see, I also don't understand whether the Oracle user name and password must be duplicated in the Properties section, or should they really only be listed in the ACLName and Password fields (in the Server Console UI)?
TIA,
Steve

Hi. The issue is that the URL you give is not the URL the driver (weblogic.jdbc.oci.Driver)
wants. The URL should be "jdbc:webLogic:oci". The properties user, password and server
will be passed to the driver for conenction attempts. The ACL is for who gets to use the
pool, and the other password entry is only if you need the DBMS password to be encrypted
in the XML. If so, set that password value, and don't have it in the driver properties.
Joe
Steve Clark wrote:
>
Hi,
Upon server startup, I get the following result:
<Nov 7, 2001 4:18:32 PM CST> <Error> <JDBC> <Cannot startup connection pool "ora
cleTrufflePool" No suitable driver>
I assumed it was a path problem, but in the startWebLogic.cmd script I've set the PATH and CLASSPATH variables to the same as in a separate command window that can successfully dbping the Oracle db.
One thing I completely don't understand is what the URL value should be for the pool, and I can't see a pattern in the examples and docs I've found on this. Here are my pool settings, at any rate:
Name: oracleTrufflePool
URL: myOracleServerName
Driver Classname: weblogic.jdbc.oci.Driver
Properties:
user=user
password=password
server=myOracleServerName
ACLName: user
Password: password
As you can see, I also don't understand whether the Oracle user name and password must be duplicated in the Properties section, or should they really only be listed in the ACLName and Password fields (in the Server Console UI)?
TIA,
Steve

Similar Messages

  • Difference between using app server connection pooling and using the driver

    Hi all,
    How to get connection pooling with out application server and tomcat also?
    What is the difference between using app server connection pooling and using the driver supported connection pooling?
    Regards,
    Murali

    maybe the performance of App server pool is better than the JDBC pool,
    for you don't know wether the implementation of the JDBC interface is good or bad.

  • Can I create connection pool by oracle oci driver?

    Can I create connection pool by oracle oci driver?My weblogic's version is 6.1 sp2 and oracle is 9.0.1.2.
    I have some trouble with connection pool created by weblogic jDriver.
    I try to read Timestamp from table and I always get the exception.It told me that ORA-00932: inconsistent datatypes.
    So I created another pool by oracle thin driver and everything was right.Then I created other pool by oracle oci driver,but something were wrong. 'Could not create pool connection. The DBMS driver exception was:java.sql.SQLException: ORA-06401: NETCMN:Invalid driver designator'
    The oci pool's parameters are below lines.
    url: jdbc:oracle:oci:@COCO
    Driver Classname: oracle.jdbc.driver.OracleDriver
    Properties: user=scott;password=tiger;protocol=oci
    If I get connection directly,don't use connection pool,I can get right connection.But why didn't I create pool by oci driver?Maybe weblogic7 or weblogic8 will work good?

    Venkat Amirineni wrote:
    Hi Joe,
    I am also trying to create a connection pool using Oracle Oci XA. Weblogic
    type 2 oci threads hanging on native calls and suggested to go for thin drivers.
    But we want to try with Oracle Oci drivers.. Can you please tell us how to
    create a conn pool using Oracle Oci.. Just the driverclass and url is enough
    or need any classpath settings etc..
    Thanks in advance for your quick reply.Hi. As far as driver properties, just use what Oracle says to. Any pool properties
    that we recommend for XA would still apply. Note that Oracle themselves recommends
    the thin driver over their OCI one:
    http://download-west.oracle.com/docs/cd/B14117_01/java.101/b10979.pdf
    Joe

  • JDBC20 connect pool issue using OCI driver

     

    I tried to use:
    url=jdbc20:weblogic:oracle.
    driver=weblogic.jdbc20.oci.Driver
    and got the following error:
    <Jul 11, 2001 5:52:34 PM PDT> <Error> <JDBC Connection Pool> <Cannot
    startup connection pool "ExrGlobalDbPool" Cannot load driver class:
    weblogic.jdbc20.oci.Driver>
    "Chuan Li" <[email protected]> wrote in message news:<[email protected]>...
    If you use the driver provided by Oracle, then use the following:
    url=jdbc:oracle:oci8:
    driver=oracle.jdbc.driver.OracleDriver
    "Jeff Guo" <[email protected]> wrote:
    Hi,
    What is the correct way to define the url in the jdbc connection pool
    to
    support jdbc20
    features using Oracle OCI driver?
    Thanks!
    Jeff

  • JDBC connection pool failures when used by JMS stores

              We are using WebLogic 6.1 sp2. We defined a separate connection pool for use by
              a JMS Store.
              <JDBCConnectionPool Name="sybaseJMSPool"
              Targets="cluster00"
              InitialCapacity="2"
              MaxCapacity="10"
              DriverName="com.sybase.jdbc2.jdbc.SybDriver"
              Properties="[email protected]@;[email protected]@;charset=utf8"
              URL="jdbc:sybase:Tds:@jms.db.host@/@jms.db.name@"/>
              (note that the @xxx@ string are replaced by actual values).
              We are using Sybase Jconnect 5.5 to a Sybase ASE 12.5 database.
              We deployed this configuration on a number of environments (testing, staging,
              ..). The actual hardware and network configuration is different for the different
              system, but the WebLogic domain stays the same regarding this issue.
              On the test system we frequently get the following exceptions:
              <Aug 13, 2002 1:56:04 PM CEST> <Alert> <JMS> <www00-test> <node00>
              <ExecuteThread: '6' for queue: 'JMS.TimerClientPool'> <> <> <040048>
              <JMSServer "JMSServer00", store failure while writing message for topic
              OrderChangeTopic, java.io.IOException: JMS JDBC store, connection pool =
              <sybaseJMSPool>, prefix = <JMS00>: write failed
              java.sql.SQLException: JZ006: Caught IOException:
              com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
              closed.
              at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
              (ErrorMessage.java:715)
              at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
              at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
              at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
              at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
              at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
              at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
              (SybStatement.java:1625)
              at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
              (SybPreparedStatement.java:91)
              at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
              (P6LogPreparedStatement.java:179)
              at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
              at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
              at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
              at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              .>
              java.io.IOException: JMS JDBC store, connection pool = <sybaseJMSPool>, prefix
              = <JMS00>: write failed
              java.sql.SQLException: JZ006: Caught IOException:
              com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
              closed.
              at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
              (ErrorMessage.java:715)
              at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
              at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
              at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
              at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
              at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
              at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
              (SybStatement.java:1625)
              at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
              (SybPreparedStatement.java:91)
              at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
              (P6LogPreparedStatement.java:179)
              at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
              at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
              at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
              at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              at weblogic.jms.store.JDBCIOStream.throwIOException
              (JDBCIOStream.java:1213)
              at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1256)
              at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
              at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              Before that this message appeared:
              <Aug 13, 2002 11:31:16 AM CEST> <Error> <ConnectionManager> <www00-test>
              <node00> <ExecuteThread: '26' for queue: 'default'> <> <> <000000>
              <Closing: 'weblogic.rjvm.t3.T3JVMConnection@795af6' because of: 'Server
              received a message over an uninitialized connection: 'JVMMessage from: 'null'
              to: '-4555218188801970213S:192.168.13.1:[7001,7001,7002,7002,7001,7002,-
              1]:ADIS:node00' cmd: 'CMD_REQUEST', QOS: '101', responseId: '1',
              invokableId: '287', flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev
              offset: '34'''>
              This problem did not occur on another system which was used during a 2 day stress
              testing session.
              It seems that the problem occurs after a period in which no user request where
              made. The user requests trigger EJB's that start sending JMS messages.
              When the problem occurs, the JMS messaging systems seems to lock up as no messages
              are received anymore by the different listeners (MDBs).
              Undeploying and redeploying the JBDC connection pool solves the problem. This
              solution is unacceptable in case of a production system.
              A similarly defined connection pool, which is used by the EJBs to make database
              connection, does not manifest this problem.
              <JDBCConnectionPool Name="sybasePool"
              Targets="cluster00"
              InitialCapacity="10"
              CapacityIncrement="5"
              MaxCapacity="50"
              PreparedStatementCacheSize="150"
              DriverName="com.sybase.jdbc2.jdbc.SybDriver"
              Properties="[email protected]@;[email protected]@;JCONNECT_VERSION=6;charset=utf8"
              URL="jdbc:sybase:Tds:@db.host@/@db.name@"/>
              The JDBC connection pool is used as follows by the JDBC store
              <JMSJDBCStore ConnectionPool="sybaseJMSPool" Name="JDBCStore00" PrefixName="JMS00"/>
              <JMSServer Name="JMSServer00" Store="JDBCStore00" Targets="node00">
              <JMSTopic JNDIName="ADIS.JMSError" JNDINameReplicated="false" Name="ErrorTopic"/>
              <JMSTopic JNDIName="ADIS.Status"
              Name="StatusTopic" RedeliveryDelayOverride="300000"/>
              <JMSTopic JNDIName="ADIS.OrderChange" JNDINameReplicated="false"
              Name="OrderChangeTopic" RedeliveryLimit="3"/>
              </JMSServer>
              Turning on the "Test Reserved Connection" with a appropriate test table does not
              help.
              Some sources on the internet tell us that JZ0C0 errors in the Jconnect driver
              can be related to network problems. Nevertheless the connection pool should be
              able to cope with this.
              Can you provide any solution for this ? Or give us hints what can cause the problem
              

    Zhenhao Qi wrote:
    thanks! Joe.
    The SQL statement itself can no longer be simplified, the long excuation time is due to the database size and complicated Select criteria. I can easily reproduce the problem by using this SQL. I tried "BEA's Oracle driver (Type 4): Version 8.1.7,9.0.1,9.2.0". the question can be dissect into 2 pieces:
    1) why the jdbc connection (using oracle.jdbc.OracleDriver) won't return anything if the SQL execution time > 5min, that is probably the Oracle's problem
    2) why the occupied connection pool won't release even I set "Statementtimeout=600", this is Weblogic's problem.
    ZhenhaoHi. Yes, (1) is oracle's problem. (2) may also be. The JDBC spec has very few
    allowances for one thread to interrupt a second thread's JDBC call. If we
    transmit your timeout request by calling setQueryTimeout() on the oracle
    statement, and if you have a weblogic-controlled transaction we call
    Statement.cancel() on any ongoing statement, we end up relying on whether
    the Oracle driver implements and responds to those calls.
    Are you doing weblogic-controlled transactions? Are you/can you
    call Statement.setQueryTimeout() on your statements, or are these
    generated JDBC queries?
    If you can duplicate the problem using the weblogic.jdbc.oracle.OracleDriver
    we have some other debug avenues. This would be good even if you really
    want to use the thin driver, because we will do the same JDBC calls to
    either driver, and the debug would prove (if) we set up a query timeout
    and if we call cancel(). If we do, then we can know that it is the Oracle
    driver failing in these regards.
    Joe

  • Connection Pool Failure

    Hello. I'm using wls 5.1 and Oracle 8i and an unable to make a connection pool. I keep getting the following with the message below. Where and how do I change my path?
    weblogic.common.ResourceException: weblogic.common.ResourceException:
    Could not create pool connection. The DBMS driver exception was:
    java.sql.SQLException: System.loadLibrary threw java.lang.UnsatisfiedLinkError
    'no weblogicoci36 in java.library.path'.
    at weblogic.jdbcbase.oci.Driver.connect(Driver.java:116)

    Hi,
    You need to ensure that the ORACLE_HOME is set and PATH has
    %ORACLE_HOME%\bin;%ORACLE_HOME%\lib;%WL_HOME%\bin\oci816_8 (check verison of
    database) in the server startup script.
    hth
    sree
    "Purvi" <porgie_76@> wrote in message news:3c6306f9$[email protected]..
    Hello. I'm using wls 5.1 and Oracle 8i and an unable to make a connection
    pool. I keep getting the following with the message below. Where and how do
    I change my path?
    weblogic.common.ResourceException: weblogic.common.ResourceException:
    Could not create pool connection. The DBMS driver exception was:
    java.sql.SQLException: System.loadLibrary threw
    java.lang.UnsatisfiedLinkError
    'no weblogicoci36 in java.library.path'.
    at weblogic.jdbcbase.oci.Driver.connect(Driver.java:116)

  • HELP - DB2 v9 & App Server PE 9.0 - PING Connection Pool Failure - HELP

    I've been playing around with Studio Creator and DB2 v9 without any issues.
    So I figured I would installed App Server PE 9 and use this as my production server that I would deploy to from studio creator.
    However, in my efforts to set up db2/v9 I have been trying to ping a connection pool without any luck. I get the following message:
    Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Connection could not be allocated because: [sunm][DB2 JDBC Driver]Resource Limits Reached( ALLOCATE MEMORY FOR NEW SQLSTT FAILED ). Diagnostic Info: FUNCTION ID = 0049 , PROBE POINT = 0400 , TRACE POINT = 0030 , SUBCODE1 = 8B0F0000, SUBCODE2 = 78A68A98, SUBCODE3 = 00000000, ERROR MSG = Parser: Memory allocation error.
    My datasource class name is com.sun.sql.jdbcx.db2.DB2DataSource.
    And my resource type is javax.sql.datasource
    I have copied smbase.jar, smdb2.jar and smutil.jar into c:\sun\appserver\lib
    and I have all of the properties (serverName, portNumber, databaseName, user, password) created and set accordingly.
    Any help would be greatly appreciated.

    Here is how I got the DB2 Express-C and Sun PE 9.0 to work. ( at least base connectivity wise )
    1. ) You have to have at least the DB2 Client installed on the system that will be communicating to the DB2 instance.
    2.) The following jars will be needed ( depending on the driver type used) . db2java.zip, db2jcc.jar, and db2jcc_license_cu.jar and use them in the App Server ->JVM settings -> Path Settings -> Classpath Suffix
    3.) The next setup is dependent on the Type driver you use
    I used the Type 4 and this is the resource setup I used.
    Connection Pool:
    Name: DB2TestPool
    Datasource Classname: com.ibm.db2.jcc.DB2SimpleDataSource
    Resource Type: javax.sql.ConnectionPoolDataSource
    Properties:
    user: xxxxxx
    password: xxxxxx
    databaseName: TEST
    serverName: <hostname of machine>
    portnumber: 50000
    driverType: 4
    URL: jdbc:db2://<hostname>:<port>/<database>
    JDBC Resource:
    JNDI Name: jdbc/TEST
    Pool Name: DB2TestPool
    With this configuration I was able to ping the database as well as connect to create an entity bean from a table. This should give you a starting point.
    I have yet to deploy my application, but should be doing that sometime today to verify that a connection can be made and used from within the application.

  • Create and Apply new connection pool failure

    Hi all,
    I am trying to creat a new connection pool by the examples Console with WebServer
    6.0
    Name: testingPool
    URL: jdbc:cloudscape:demo or jdbc:dbc:cloudscape:Test (where Test is a new DB
    in cloudscape)
    Driver Name:COM.cloudscape.core.JDBCDriver
    Property:
    user=none
    password=none
    server=none
    Then create a Datasource which using the new created testingPool and the Target
    is the "exampleServer"
    However when I start the server,it keeps on complaining that the "testingPool
    is not exist".
    Any setting that I 've missed when using a new connection pool??
    I only know the workaround is using the demoPool which is already exist in the
    example.
    Any help will be very appreciate!!
    Thanks !
    Regards,
    u0p1

    HI,
    I've already set the Target Server to be the Example Server,
    is it wrong?
    "Sree Bodapati" <[email protected]> wrote:
    Check if you have set a target server for the connection pool.
    sree
    "u0p1" <[email protected]> wrote in message
    news:3bb3bc32$[email protected]..
    Hi all,
    I am trying to creat a new connection pool by the examples Consolewith
    WebServer
    6.0
    Name: testingPool
    URL: jdbc:cloudscape:demo or jdbc:dbc:cloudscape:Test (where Test isa new
    DB
    in cloudscape)
    Driver Name:COM.cloudscape.core.JDBCDriver
    Property:
    user=none
    password=none
    server=none
    Then create a Datasource which using the new created testingPool andthe
    Target
    is the "exampleServer"
    However when I start the server,it keeps on complaining that the"testingPool
    is not exist".
    Any setting that I 've missed when using a new connection pool??
    I only know the workaround is using the demoPool which is already existin
    the
    example.
    Any help will be very appreciate!!
    Thanks !
    Regards,
    u0p1

  • Oracle Connection Pool failure in COM+

    I am having some trouble trying to get a specific database to work with an application that makes use of a COM+ Application. When we point the application at the UAT database everything seems fine, but when we point it to the production database after a few successful calls it ends up failing at the COM+ application recycles. The event viewer provides the following information:
    Event Type:     Error
    Event Source:     COM+
    Event Category:     Unknown
    Event ID:     4786
    Date:          8/5/2007
    Time:          12:54:46 PM
    User:          N/A
    Computer:     APPL_SERVER
    Description:
    The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below.
    Component Prog ID: Oracle Connection Pool - tnsnames_alias
    Method Name: IDispenserDriver::CreateResource
    Server Application ID: {30A93CB3-25EB-4258-8C88-5AE103B7B86F}
    Server Application Instance ID:
    {A57C513E-519F-45BD-B46D-DC54B285F534}
    Server Application Name: COM+ Application Name
    The serious nature of this error has caused the process to terminate.
    Exception: C0000005
    Address: 0x7C8327F9
    Call Stack:
    + 0x7c8327f9
    ntdll!RtlFindActivationContextSectionGuid + 0x7d2
    ntdll!RtlInitializeSListHead + 0x175
    ntdll!RtlFindActivationContextSectionGuid + 0x1b7
    msvcrt!malloc + 0x6c
    oracommon9!sktsfMalloc + 0x14
    orageneric9!kpummapg + 0x58
    orageneric9!kghalo + 0xabb
    orageneric9!kghalf + 0x102
    orageneric9!kopo2cpc + 0x61
    orageneric9!kopeini + 0x1d
    orageneric9!kopo2cpc + 0xd2
    orageneric9!kopopgi + 0x117
    OraClient9!koudpnp + 0x712
    OraClient9!koudpnp + 0x101
    OraClient9!kpuinit0 + 0xb19
    OraClient9!kpuinit + 0x38
    OraClient9!OCIEnvInit + 0x1c
    oramts!kpntsrvr::kpntsrvr(class kpntdbid *) + 0x80
    oramts!kpntdbid::allocNewSrvr(struct SIDAND_ATTRIBUTES *) + 0x138
    oramts!kpntdbid::GetSrvr(class kpntsvrl * *,unsigned long) + 0x7df
    oramts!kpntdisp::getNet8conn(class kpntsvrl * *,unsigned long) + 0x41
    oramts!kpntsess::initOCI(void) + 0xec
    oramts!kpntsess::sessionBegin(void) + 0x17b
    oramts!kpntdisp::CreateResource(unsigned long,unsigned long *,long *) + 0xc4
    COMSVCS!DispManGetContext + 0xa3d
    COMSVCS!DispManGetContext + 0x1fee
    oramts!kpntdisp::allocateConnection(class kpntsess * *,unsigned long,class kpntrtyp *) + 0x3c4
    oramts!_kpntsvcgetex + 0x183
    oramts!_kpntsvcget + 0x25
    oramts!kpntctra::getConnectionAndHandles(class kpntrtyp *,struct OCISvcCtx * *,struct OCITrans * *,struct OCIError * *) + 0x87
    oramts!kpntctra::abortBranch(struct xid_t &,class kpntbrnch *,struct BOID *,int,struct BOID *) + 0x15a
    oramts!kpntctra::doAbort(struct BOID *,int,struct BOID *) + 0x454
    oramts!kpntajob::doJob(void) + 0x27
    oramts!kpntjobq::serviceRequest(class kpntjob *) + 0x3e
    oramts!workerThread(void *) + 0xd0
    msvcrt!_endthreadex + 0xa3
    kernel32!GetModuleFileNameA + 0xeb
    Not being an expert in Oracle, I have been able to dig up a little bit of information that might be of use ...
    a) Our tnsnames.ora indicates that the connections are to be DEDICATED and running Toad bares this out -- dllhost ends up with a single connection.
    b) most of the database initial set of parameters seem to be very similar. The only difference I noticed was that the archive log mode and db_cache_advice are ON for production.
    c) We have little control over how the connection strings are being created internally in this COM+ application, but however they are created it works for UAT and doesn't for PROD.
    d) When we go into our web application and hit a page that makes use of the COM+ component to render, it will work the first time but when I do a simple browser refresh it will usually fail on the 2nd or 3rd time. Almost like it is trying to expand the connection pool size and the oracle server is throwing up.
    If I didn't mention earlier the two database instances run on different servers but the application server is exactly the same. We only change the alias we are using for the database (both are defined in tnsnames) and the password used to make its connection.
    Does anyone have any clues on this one? I am really spinning my wheels trying to figure out what could cause this type of situation. Anything at all would be very helpful.

    It appeared to us that the problem was with the Oracle server and that it might have been failing when we were trying to expand our application connection pool size or basically obtain more connections.
    The biggest indicator of this is that we run the same application code against two different databases and one works and one does not work. Having said this, I suppose the problem could be rooted in a data error instead of an oracle server error ...
    Is there a specific trace file on the oracle server that would help me point to any error that is truly an oracle server error? Sorry I am very new to Oracle.

  • 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

  • Connection Pooling in EJBContainer if Driver already implements

    Hi,
    Can anybody explain the mechanism in an EJBContainer if the Driver for a particular database already implements the Connection pooling ie JDBC2.0X feature. Does the EJBContainer utilize the already pooled connections or the Container uses it own implementation of the pooledConnection interface.
    Thanks in advance
    neo

    the Container uses it own implementation of the pooledConnection interface.
    you have to make connection pool in the property file
    in weblogic we make connection pool in the weblogic.property file
    which server u r using

  • No connection pool with oracle thin driver

    Hi all,
    whenever I try to set up my server as target for an Oracle connection pool on OPracle
    8.1.7, I get the following exception:
    java.sql.SQLException: Illegal Arguments
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:210)
    at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:857)
    at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:189)
    at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:249)
    at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:365)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:260)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:193)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
    at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
    at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
    at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
    The Oracle driver classes12.zip is the very first in my classpath, connection pool
    settings are:
    <JDBCConnectionPool DriverName="oracle.jdbc.driver.OracleDriver"
    Name="Oracle Connection Pool"
    Properties="dll=ocijdbc8;USER=zapper;protocol=thin;PASSWORD=oracle"
    TestTableName="CABIN" URL="jdbc:oracle:thin:@192.168.0.2:1521:eins"/>
    Do I need any additional software besides the driver and weblogic??
    Thx
    Christian

    You're welcome :)
    Regards,
    Slava Imeshev
    "Christian" <[email protected]> wrote in message
    news:[email protected]...
    >
    That worked!
    Thx
    "Slava Imeshev" <[email protected]> wrote:
    Hi Christian,
    There is a couple of problems with the pool definition.
    First, the connection pool and datasource names can't
    contain spaces. Second, USER and PASSWORD
    should be in lower case, i.e. user and password accordingly.
    Regards,
    Slava Imeshev
    "Christian" <[email protected]> wrote in message
    news:[email protected]...
    Hi all,
    whenever I try to set up my server as target for an Oracle connectionpool
    on OPracle
    8.1.7, I get the following exception:
    java.sql.SQLException: Illegal Arguments
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:210)
    at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:857)
    at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:189)
    at
    oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:249)
    atoracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:365)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:260)
    atweblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connection
    EnvFactory.java:193)
    at
    weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connection
    EnvFactory.java:134)
    at
    weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
    ava:698)
    at
    weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
    at
    weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623
    The Oracle driver classes12.zip is the very first in my classpath,connection pool
    settings are:
    <JDBCConnectionPool DriverName="oracle.jdbc.driver.OracleDriver"
    Name="Oracle Connection Pool"
    Properties="dll=ocijdbc8;USER=zapper;protocol=thin;PASSWORD=oracle"
    TestTableName="CABIN" URL="jdbc:oracle:thin:@192.168.0.2:1521:eins"/>
    Do I need any additional software besides the driver and weblogic??
    Thx
    Christian

  • Intermittent mssql4 Connection Pool Failure problems

    Ocaisionally we are getting the following error:
    weblogic.jdbcbase.mssqlserver4.TdsConnection.registerOutgoingPipeline(TdsConnection.java:414)
    at weblogic.jdbcbase.mssqlserver4.TdsConnection.registerPipeline(TdsConnection.java:430)
    at weblogic.jdbcbase.mssqlserver4.TdsStatement.execute(TdsStatement.java:182)
    at weblogic.jdbcbase.mssqlserver4.TdsStatement.execute(TdsStatement.java:1521)
    at weblogic.jdbcbase.jts.Statement.execute(Statement.java:302)
    at weblogic.jdbc20.rmi.internal.PreparedStatementImpl.execute(PreparedStatementImpl.java:288)
    at weblogic.jdbc20.rmi.SerialPreparedStatement.execute(SerialPreparedStatement.java:398
    Once we get this error the whole connection pool is fried until we restart it.
    We are using the test connection on checkout property of the connection pool,
    so I don't understand why this problem isn't caught at connection checkout time.
    Normally if there is a problem with a connection, the connection is refreshed.
    However, sometimes, this happens.

    What version of our product? What is the whole serverside stacktrace?
    thanks,
    Joe
    Scott wrote:
    >
    Ocaisionally we are getting the following error:
    weblogic.jdbcbase.mssqlserver4.TdsConnection.registerOutgoingPipeline(TdsConnection.java:414)
    at weblogic.jdbcbase.mssqlserver4.TdsConnection.registerPipeline(TdsConnection.java:430)
    at weblogic.jdbcbase.mssqlserver4.TdsStatement.execute(TdsStatement.java:182)
    at weblogic.jdbcbase.mssqlserver4.TdsStatement.execute(TdsStatement.java:1521)
    at weblogic.jdbcbase.jts.Statement.execute(Statement.java:302)
    at weblogic.jdbc20.rmi.internal.PreparedStatementImpl.execute(PreparedStatementImpl.java:288)
    at weblogic.jdbc20.rmi.SerialPreparedStatement.execute(SerialPreparedStatement.java:398
    Once we get this error the whole connection pool is fried until we restart it.
    We are using the test connection on checkout property of the connection pool,
    so I don't understand why this problem isn't caught at connection checkout time.
    Normally if there is a problem with a connection, the connection is refreshed.
    However, sometimes, this happens.

  • Error creating a connection pool (No suitable driver)

    I have just installed WLS6.1 SP3
    I try to create a connection with the following parameters
    URL = jdbc:oracle:thin@myOracleServer:1521:myOracleSID
    DriverName = oracle.jdbc.driver.OracleDriver
    every thing else is left as the defaults,
    when I click create everything is OK.
    I then go to the "Targets" tab and select myserver,
    move it to the chosen column and click apply.
    I then get the error
    <Error> <JDBC> <Cannot startup connection pool "myCP" No suitable driver>
    I looked at the doc edocs.bea.com/wls/docs61/jdbc/thirdparty.html
    Under the section "Setting environment for your third party driver"
    it implys that if your using sybase jconnect or oracle thin drivers
    you do not need to do anything else.
    I looked in the weblogic.jar file and the OracleDriver.class file
    is there under oracle\jdbc\driver.
    the CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
    I would have thought that the driver class in the jar file
    would have be picked up given the path & classname match the
    driver name enter in the console.
    Any ideas on how to fix this problem?

    "Robert Towler" <[email protected]> wrote in message
    news:3dd3ea04$[email protected]..
    Thanks Slava, you were correct,
    I really appreciate it.Glad to help :)
    Regards,
    Slava Imeshev
    "Slava Imeshev" <[email protected]> wrote:
    Hi Robert,
    Looks like colon is missing after jdbc:oracle:thin. The url should be
    jdbc:oracle:thin:@myOracleServer:1521:myOracleSID
    Regards,
    Slava Imeshev
    "Robert Towler" <[email protected]> wrote in message
    news:3dd3e3c6$[email protected]..
    I have just installed WLS6.1 SP3
    I try to create a connection with the following parameters
    URL = jdbc:oracle:thin@myOracleServer:1521:myOracleSID
    DriverName = oracle.jdbc.driver.OracleDriver
    every thing else is left as the defaults,
    when I click create everything is OK.
    I then go to the "Targets" tab and select myserver,
    move it to the chosen column and click apply.
    I then get the error
    <Error> <JDBC> <Cannot startup connection pool "myCP" No suitable
    driver>
    >>>
    I looked at the doc edocs.bea.com/wls/docs61/jdbc/thirdparty.html
    Under the section "Setting environment for your third party driver"
    it implys that if your using sybase jconnect or oracle thin drivers
    you do not need to do anything else.
    I looked in the weblogic.jar file and the OracleDriver.class file
    is there under oracle\jdbc\driver.
    the CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
    I would have thought that the driver class in the jar file
    would have be picked up given the path & classname match the
    driver name enter in the console.
    Any ideas on how to fix this problem?

  • Cannot startup connection pool  no suitable driver /WLS 6.1 SP4

    hi all,
    i got a problem in creating a ConnectionPool with weblogic 6.1 sp4.
    my connection pool has following config data:
    URL:jdbc:oracle:[email protected]:1521:ESECD7
    Driver:oracle.jdbc.driver.OracleDriver
    props
    username=aaaa
    password=bbbb
    in my startWebLogic.cmd i have following classpath:
    set PATH=.\bin;%PATH%;c:\bea\wlserver6.1\config\mydomain;c:\bea\wlserver6.1\bin\oci817_8;c:\oracle\ora92\bin;%PATH%
    set CLASSPATH=C:\oracle\ora92\jdbc\lib\classes111.zip;C:\oracle\ora92\jdbc\lib\classes12.zip;.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;c:\bea\jolt.jar;c:\bea\joltwls.jar;c:\bea\joltjse.jar
    but i keep on gettign the exception Cannot startup connection pool.. no suitable
    driver
    to me it looks like everything is in classpath...
    any ideas?
    regards
    marco

    Marco wrote:
    hi all,
    i got a problem in creating a ConnectionPool with weblogic 6.1 sp4.
    my connection pool has following config data:
    URL:jdbc:oracle:[email protected]:1521:ESECD7
    Driver:oracle.jdbc.driver.OracleDriver
    props
    username=aaaa
    password=bbbb
    in my startWebLogic.cmd i have following classpath:
    set PATH=.\bin;%PATH%;c:\bea\wlserver6.1\config\mydomain;c:\bea\wlserver6.1\bin\oci817_8;c:\oracle\ora92\bin;%PATH%
    set CLASSPATH=C:\oracle\ora92\jdbc\lib\classes111.zip;C:\oracle\ora92\jdbc\lib\classes12.zip;.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;c:\bea\jolt.jar;c:\bea\joltwls.jar;c:\bea\joltjse.jar
    but i keep on gettign the exception Cannot startup connection pool.. no suitable
    driver
    to me it looks like everything is in classpath...
    any ideas?
    regards
    marcoHi. Read the weblogi startServer script, and the startWLS script it calls. These
    scripts build up a string which is added to the java commandline that starts
    the server, with an argument -classpath ....... Unless the driver shows up there,
    the server doesn't see it.
    However, we already include a version of the oracle thin driver. It may not be
    the best (it's old), so you will want to make sure you version gets in to the classpath
    argument ahead of our stuff, but the old driver would have been invoked...
    Therefore, I suspect your URL is not exactly correct. Please verify that this exact URL
    works in a simple standalone JDBC program using the driver you want, without any
    weblogic code in the picture.
    thanks,
    Joe

Maybe you are looking for

  • Airport Express not showing up

    Noticed my aexpress was blinking amber today. We use it to stream music to speakers. I tried to reset it and it still is blinking amber. It is not showing up in Airport Utility 5.6 at all. It did a few minutes ago but when I went throught the set up

  • Dual monitors with HDMI Splitter

    I am wanting to use my ATV 2 at work to run a slideshow on 2 monitors. I bought an HDMI Splitter but it just has a black screen. If I hook up 1 HDMI it works fine. Any ideas?

  • PL/SQL Version in Forms 9 or 10?

    I am looking for reasons to upgrade Forms. What version of PL/SQL does Forms 9 and 10 run? Thanks!

  • Can't delete calendar default reminder

    I am having trouble with the google calendar since upgrading to lollipop. In settings I can change the default reminder to none, but every time I put a new entry in there's always a reminder time that I can't delete. I don't need a reminder for all m

  • Archive and Install - will I lose my photos?

    Hi I need to reinstall OS X as I am having some problems with the blue screen and the fact that my iBook will not boot up. Before I go ahead and reinstall can anyone confirm that I will not lose my photos (and music). I really do not want to lose yea