Weblogic jDriver for Oracle 9.0.1.4

Hi,
We are using the Weblogic jDriver for Oracle oci901_8 to access the Oracle 9.0.1.
We are planning to upgrade the oracle to 9.0.1.4. Will there be any issues with
the Weblogic jDriver that is being currently used by us(oci901_8 ).
Is there Weblogic jDriver available for oracle 9.0.1.4?
Thanks in Advance,
Vidhyaa Shankar.S

The driver you have is ok to be used with oracle 9.0.1.4. Actually, you are getting
patch set for 901 database server. So, you dont need additional driver. The driver you
have is ok to work with it.
Mitesh
"Vidhyaa Shankar.S" wrote:
Hi,
We are using the Weblogic jDriver for Oracle oci901_8 to access the Oracle 9.0.1.
We are planning to upgrade the oracle to 9.0.1.4. Will there be any issues with
the Weblogic jDriver that is being currently used by us(oci901_8 ).
Is there Weblogic jDriver available for oracle 9.0.1.4?
Thanks in Advance,
Vidhyaa Shankar.S

Similar Messages

  • Does Weblogic JDriver for Oracle support Oracle REFCURSOR?

     

    "R. W. Stavros" wrote:
    >
    BUT BE FORWARNED ... IF YOUR CONNECTION IS FROM A CONNECTION POOL ...
    YOU GET A WONDERFUL weblogic.jdbc.pool.ResultSet not a
    java.sql.ResultSet .... BEA wants you to believe its a featureI'm still interested in your position that a weblogic.jdbc.pool.ResultSet
    is not a java.sql.ResultSet. I get the impression you're very frustrated
    and I know that can cause one to make mistakes one normally wouldn't...
    Joe
    >
    Shiva Paranandi <[email protected]> wrote in message news:<[email protected]>...
    Yes, you have to specify it as java.sql.Types.OTHER and use the
    getObject() method to obtain it.
    Shiva.
    Chuan Li wrote:
    Does Weblogic JDriver for Oracle support Oracle REFCURSOR?
    Thanks.
    -Chuan
    PS: Folks: BEA WebLogic is expanding rapidly, with both entry and advanced positions
    for people who want to work with Java, XML, SOAP and E-Commerce infrastructure products.
    We have jobs at Nashua NH, Liberty Corner NJ, San Francisco and San Jose CA.
    Send resumes to [email protected]

  • Weblogic jDriver for oracle/xa thin driver configuration

              Hi,
              I try to configure an XA thin connection pool to oracle.
              Using the configuration from page 16-11 of adminguide.pdf,
              the start is with the error "No suitable driver".
              The driver is configured like that:
              DriverClassname=oracle.jdbc.xa.client.OracleXADataSource
              Also, with the classes12.zip for oracle 8.1.7 for jdk1.2 taken from oracle site,
              before weblogic.jar in classpath, same error:(.
              The error:
              <Jan 14, 2001 2:22:01 PM EET> <Error> <JDBC> <Cannot startup connection pool "OracleJDBCTxConnectionPool"
              weblogic.common.ResourceException: java.sql.SQLException: No suitable driver
                   at java.sql.DriverManager.getConnection(DriverManager.java:537)
                   at java.sql.DriverManager.getConnection(DriverManager.java:177)
                   at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:111)
                   at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:88)
                   at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:68)
                   at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:194)
                   at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:54)
                   at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:707)
                   at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:306)
                   at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:679)
                   at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:109)
                   at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
                   at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
                   at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
                   at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
                   at java.lang.reflect.Method.invoke(Native Method)
                   at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
                   at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
                   at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
                   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:437)
                   at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
                   at $Proxy41.updateDeployments(Unknown Source)
                   at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2571)
                   at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:333)
                   at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:149)
                   at java.lang.reflect.Method.invoke(Native Method)
                   at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
                   at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
                   at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
                   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:437)
                   at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
                   at $Proxy34.start(Unknown Source)
                   at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
                   at weblogic.management.Admin.startApplicationManager(Admin.java:1098)
                   at weblogic.management.Admin.finish(Admin.java:520)
                   at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:473)
                   at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
                   at weblogic.Server.main(Server.java:35)
                   at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:203)
                   at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:54)
                   at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:707)
                   at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:306)
                   at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:679)
                   at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:109)
                   at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
                   at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
                   at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
                   at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
                   at java.lang.reflect.Method.invoke(Native Method)
                   at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
                   at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
                   at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
                   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:437)
                   at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
                   at $Proxy41.updateDeployments(Unknown Source)
                   at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2571)
                   at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:333)
                   at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:149)
                   at java.lang.reflect.Method.invoke(Native Method)
                   at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
                   at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
                   at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
                   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:437)
                   at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
                   at $Proxy34.start(Unknown Source)
                   at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
                   at weblogic.management.Admin.startApplicationManager(Admin.java:1098)
                   at weblogic.management.Admin.finish(Admin.java:520)
                   at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:473)
                   at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
                   at weblogic.Server.main(Server.java:35)
              >
              Thank you in advance.
              kind regards, adrian
              

              Hi,
              it works :) !
              Thank you,
              Adrian
              "John Harby" <[email protected]> wrote:
              >
              >Mine seems to work ok but I have classes12.zip after weblogic.jar.
              >
              >set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;.C:\oracle\ora81\jdbc\l
              >ib\classes12.zip;.\config\examples\serverclasses
              >
              >
              >"adrian balaban" <[email protected]> wrote:
              >>
              >>Hi,
              >>
              >>I try to configure an XA thin connection pool to oracle.
              >>
              >>Using the configuration from page 16-11 of adminguide.pdf,
              >>the start is with the error "No suitable driver".
              >>
              >>The driver is configured like that:
              >>DriverClassname=oracle.jdbc.xa.client.OracleXADataSource
              >>
              >>Also, with the classes12.zip for oracle 8.1.7 for jdk1.2 taken from
              >oracle
              >>site,
              >>before weblogic.jar in classpath, same error:(.
              >>
              >>The error:
              >>
              >><Jan 14, 2001 2:22:01 PM EET> <Error> <JDBC> <Cannot startup connection
              >>pool "OracleJDBCTxConnectionPool"
              >>weblogic.common.ResourceException: java.sql.SQLException: No suitable
              >>driver
              >>     at java.sql.DriverManager.getConnection(DriverManager.java:537)
              >>     at java.sql.DriverManager.getConnection(DriverManager.java:177)
              >>     at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:111)
              >>     at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:88)
              >>     at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:68)
              >>     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:194)
              >>     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:54)
              >>     at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:707)
              >>     at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:306)
              >>     at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:679)
              >>     at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:109)
              >>     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
              >>     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
              >>     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
              >>     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
              >>     at java.lang.reflect.Method.invoke(Native Method)
              >>     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
              >>     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
              >>     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
              >>     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:437)
              >>     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
              >>     at $Proxy41.updateDeployments(Unknown Source)
              >>     at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2571)
              >>     at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:333)
              >>     at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:149)
              >>     at java.lang.reflect.Method.invoke(Native Method)
              >>     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
              >>     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
              >>     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
              >>     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:437)
              >>     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
              >>     at $Proxy34.start(Unknown Source)
              >>     at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
              >>     at weblogic.management.Admin.startApplicationManager(Admin.java:1098)
              >>     at weblogic.management.Admin.finish(Admin.java:520)
              >>     at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:473)
              >>     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
              >>     at weblogic.Server.main(Server.java:35)
              >>
              >>     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:203)
              >>     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:54)
              >>     at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:707)
              >>     at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:306)
              >>     at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:679)
              >>     at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:109)
              >>     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
              >>     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
              >>     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
              >>     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
              >>     at java.lang.reflect.Method.invoke(Native Method)
              >>     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
              >>     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
              >>     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
              >>     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:437)
              >>     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
              >>     at $Proxy41.updateDeployments(Unknown Source)
              >>     at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2571)
              >>     at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:333)
              >>     at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:149)
              >>     at java.lang.reflect.Method.invoke(Native Method)
              >>     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
              >>     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
              >>     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
              >>     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:437)
              >>     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
              >>     at $Proxy34.start(Unknown Source)
              >>     at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
              >>     at weblogic.management.Admin.startApplicationManager(Admin.java:1098)
              >>     at weblogic.management.Admin.finish(Admin.java:520)
              >>     at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:473)
              >>     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
              >>     at weblogic.Server.main(Server.java:35)
              >>>
              >>
              >>Thank you in advance.
              >>
              >>kind regards, adrian
              >
              

  • Problem installing weblogic jdriver for oracle

    Hi ,
    I have installed WLS510 and Oracle8i Personal Edition on windows98. I have
    put the c:\weblogic\bin\oci815_8 directory in the system path and
    c:\oracle\ora81\jdbc\lib\classes102.zip in the CLASSPATH
    Now when I try to test the connection using the following command:
    $ java utils.t3dbping URL user password DB driver_class driver_URL
    I get error :
    Connecting to WebLogic with the WebLogic JDBC Driver
    Can't connect with the WebLogic JDBC driver:
    System.loadLibrary threw java.lang.UnsatisfiedLinkError
    with the message 'no weblogicoci36 in java.library.path'.
    Server StackTrace:
    <not available>]
    Could anyone please tell me what java.library.path is and where should I
    find
    weblogicoci36.
    Thanks
    Vishwajeet Lohakarey

    java.library.path is Java System variable for seting directories where will java look out for native library modules (DLLs on NT). It is normally unset because DLLs are serached by standard NT algorithm (PATH variable, System dir) too.
    weblogicoci36 is native module name of WL JDBC driver for Oracle that Java&NT couldn't find. Coresponding DLL file is in your c:\weblogic\bin\oci815_8 directory.
    Problem could be in that if WL is started as NT Service,
    a) PATH variable must be set for System not for User and
    b) this setting don't take effect until NT restart.
    VZ
    "Vishwajeet Lohakarey" <[email protected]> wrote:
    Hi ,
    I have installed WLS510 and Oracle8i Personal Edition on windows98. I have
    put the c:\weblogic\bin\oci815_8 directory in the system path and
    c:\oracle\ora81\jdbc\lib\classes102.zip in the CLASSPATH
    Now when I try to test the connection using the following command:
    $ java utils.t3dbping URL user password DB driver_class driver_URL
    I get error :
    Connecting to WebLogic with the WebLogic JDBC Driver
    Can't connect with the WebLogic JDBC driver:
    System.loadLibrary threw java.lang.UnsatisfiedLinkError
    with the message 'no weblogicoci36 in java.library.path'.
    Server StackTrace:
    <not available>]
    Could anyone please tell me what java.library.path is and where should I
    find
    weblogicoci36.
    Thanks
    Vishwajeet Lohakarey

  • Configuring Weblogic's jDriver for Oracle to use in distributed transactions

              Here is some errata to the instructions at "Configuring XA JDBC drivers" section of the online beta documentation:
              http://www.weblogic.com/docs60/adminguide/managetx.html#1041268
              The sample JDBC connection pool using Weblogic jDriver for Oracle should be:
              <JDBCConnectionPool
              Name="fundsXferAppPool"
              Targets="myserver"
              URL="jdbc:weblogic:oracle:localdb"
              DriverName="weblogic.jdbc.oci.xa.XADataSource"
              InitialCapacity="0"
              MaxCapacity="5"
              CapacityIncrement="1"
              Properties="user=scott;password=tiger;server=localdb;rmid=0"
              />
              <JDBCTxDataSource
              Name="fundsXferDataSource"
              Targets="myserver,server1"
              JNDIName="myapp.fundsXfer"
              PoolName="fundsXferAppPool"
              />
              Here is an example of an additional XA connection pool for a second database instance:
              <JDBCConnectionPool
              Name="fundsXferAppPool2"
              Targets="myserver"
              URL="jdbc:weblogic:oracle:localdb2"
              DriverName="weblogic.jdbc.oci.xa.XADataSource"
              InitialCapacity="0"
              MaxCapacity="5"
              CapacityIncrement="1"
              Properties="user=scott;password=tiger;server=localdb2;rmid=1"
              />
              <JDBCTxDataSource
              Name="fundsXferDataSource2"
              Targets="myserver,server1"
              JNDIName="myapp.fundsXfer2"
              PoolName="fundsXferAppPool2"
              />
              Please note the different "rmid" values for the 2 different database instances. Note also that the above sample only applies for Beta 1. Instructions may change in the future for Beta 2.
              Also, all the names of the data source properties shown in "Table 8-2 Data Source Properties for WebLogic jDriver for Oracle" should start with lower case.
              The Beta 1 online documentation will soon be updated to reflect the above. Our apologies for any inconvenience caused.
              -- Priscilla Fung, BEA Systems, Inc.
              

              Thanks
              Mark
              "Sree Bodapati" <[email protected]> wrote:
              >Hi Mark,
              >
              >Yes you need 8.1.6 DB Server or higher for WebLogic's jDriver for Oracle/XA
              >as well.
              >
              >/
              >sree
              >
              >
              >"Mark Cordobal" <[email protected]> wrote in message
              >news:[email protected]..
              >>
              >> I read that XA features require version Oracle8i release 8.1.6 or later
              >of
              >the Oracle
              >> server.
              >> Does this apply only to Oracle JDBC drivers (which implement 2pc on top
              >of
              >JAVA_XA
              >> package) or also to Weblogic's jDriver for Oracle/XA ?
              >> I mean, if I have two Oracle 8.06 (or however < 8.1.6) jdbc Resource
              >Manager, can
              >> I implement (wlserver 6.1sp2) a distributed xa transaction using
              >Weblogic's jDriver
              >> for Oracle/XA ?
              >> Or is it (jdriver) built also on top of JAVA_XA package, and so the db
              >server XA
              >> compliancy is a must ?
              >>
              >> Thanks in advance
              >>
              >> Mark
              >
              >
              

  • Cannot configure JDriver for Oracle

    Following the instructions indicated in Setting JDriver for Oracle, I still get
    the following errors :
    1. Error dialog box : The procedure entry point OCILobLocatorAssign could not
    be located in the dynamic link library OCI.dll.
    Anyone can help to fix the problem.
    Thanks.
    Elton.

    Sashikiran Inuganti wrote:
    We recently applied a client and server patches to our db and workstations to move to Oracle9i Enterprise Edition Release 9.2.0.6.0. We are using the OCI driver thru the weblogic Jdriver for oracle. when we print the meta data after the client upgrade the version of the driver is still showing as old. If we put the oracle classes12.jar in the weblogic classpath the driver version is printed correctly from the meta data. Can some oone answer why this happens.
    Here is the out put with out the oracle classes12.jar in the class path:
    <b>============= Database Product Name is ... Oracle
    Database Product Version is Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.6.0 - Production
    ============= JDBC Driver Name is ........ Oracle JDBC driver
    JDBC Driver Version is ..... 9.2.0.3.0
    JDBC Driver Major Version is 9
    JDBC Driver Minor Version is 2</b>
    Driver version should show as 9.2.0.6.0 it is instead showing 9.2.0.3.0.
    Thanks For your Help.We ship a version of the oracle driver, which you will find in the server\lib directory, and
    unless you put a different version of the driver ahead of weblogic.jar, that's the version of
    the driver WLS will use. You can definitely install a later version of the oracle driver in that
    directory.
    Joe

  • Setting isolation level with JDriver for Oracle/XA

    edocs (http://e-docs.bea.com/wls/docs70/oracle/trxjdbcx.html#1080746) states that,
    if using jDriver for Oracle/XA you can not set the transaction isolation level
    for a transaction and that 'Transactions use the transaction isolation level set
    on the connection or the default transaction isolation level for the database'.
    Does this mean that you shouldn't try to set it programatically (fair enough)
    or that you can't set it in the weblogic deployment descriptor either? Also anybody
    got any idea what the default is likely to be if you are using an Oracle 9iR2
    database? Is this determined by some database setting?

    IJ wrote:
    edocs (http://e-docs.bea.com/wls/docs70/oracle/trxjdbcx.html#1080746) states that,
    if using jDriver for Oracle/XA you can not set the transaction isolation level
    for a transaction and that 'Transactions use the transaction isolation level set
    on the connection or the default transaction isolation level for the database'.
    Does this mean that you shouldn't try to set it programatically (fair enough)
    or that you can't set it in the weblogic deployment descriptor either? Also anybody
    got any idea what the default is likely to be if you are using an Oracle 9iR2
    database? Is this determined by some database setting?The system should honor the setting defined in the deployment descriptor,
    however, for oracle it may not be helpful to change it. Oracle provides two
    isolation levels. The default is always READ_COMMITTED. The other
    setting is SERIALIZABLE, but this hurts performance, and is also problematic
    in the way oracle implements it. For instance, even if you set SERIALIZABLE,
    oracle will not lock read data. It will allow other transactions to read and/or
    alter data trhat another ongoing SERIALIZABLE transaction has read. The
    only way to really lock read data in oracle is to issue oracle-specific SQL in
    your select: "SELECT ..... FOR UPDATE".
    All in all, you should collect a strong case for why you can't proceed with
    READ_COMMITTED first. Then you should research oracle's recommendations
    (and their problem record) with SERIALIZABLE.
    Joe Weinstein at BEA

  • XA  jDriver for Oracle problem : Getting native code exception

    Hi,
    I'm getting a native code exception which causes the Weblogic server to crash when
    using XA drivers for transaction with two oracle databases. My application uses RMI
    and threads.
    I'm using BEA's jDriver for Oracle running under Weblogic server 6.1 sp1 talking
    to Oracle 8.1.6. The OS is Solaris 2.8.
    In middle of the program execution it's giving this problem. I'm using jdk131 in
    solaris platform.
    Any idea what's going on here ?
    Thanks,
    Nagoor Haja
    Exception in the Log file:
    ===========================
    An unexpected exception has been detected in native code outside the VM.
    Unexpected Signal : 11 occurred at PC=0xff2414d8
    Function name=madvise
    Library=/usr/lib/libc.so.1
    Current Java thread:
    at weblogic.jdbc.oci.xa.XA.native_commit(Native Method)
    at weblogic.jdbc.oci.xa.XA.commit(XA.java:136)
    at weblogic.jdbc.oci.xa.XADataSource.commit(XADataSource.java:696)
    at weblogic.jdbc.jta.DataSource.commit(DataSource.java:784)
    at weblogic.transaction.internal.ServerResourceInfo.commit(ServerResourceInfo.java:1180)
    at weblogic.transaction.internal.ServerResourceInfo.commit(ServerResourceInfo.java:419)
    at weblogic.transaction.internal.ServerSCInfo.startCommit(ServerSCInfo.java:233)
    at weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransactionImpl.java:1397)
    at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:1940)
    at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:1886)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:221)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
    at weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68)
    at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Dynamic libraries:
    0x10000 /opt/jdk131/jre/bin/../bin/sparc/native_threads/java
    0xff350000 /usr/lib/libthread.so.1
    0xff390000 /usr/lib/libdl.so.1
    0xff200000 /usr/lib/libc.so.1
    0xff330000 /usr/platform/SUNW,Ultra-60/lib/libc_psr.so.1
    0xfe480000 /opt/jdk131/jre/lib/sparc/hotspot/libjvm.so
    0xff2e0000 /usr/lib/libCrun.so.1
    0xff1e0000 /usr/lib/libsocket.so.1
    0xff100000 /usr/lib/libnsl.so.1
    0xff0d0000 /usr/lib/libm.so.1
    0xff100000 /usr/lib/libnsl.so.1
    0xff0d0000 /usr/lib/libm.so.1
    0xff310000 /usr/lib/libw.so.1
    0xff0b0000 /usr/lib/libmp.so.2
    0xff080000 /opt/jdk131/jre/lib/sparc/native_threads/libhpi.so
    0xff050000 /opt/jdk131/jre/lib/sparc/libverify.so
    0xfe440000 /opt/jdk131/jre/lib/sparc/libjava.so
    0xff020000 /opt/jdk131/jre/lib/sparc/libzip.so
    0xfafb0000 /opt/jdk131/jre/lib/sparc/libnet.so
    0xfadd0000 /usr/lib/nss_files.so.1
    0xe1d00000 /opt/wlserver6.1/lib/solaris/oci816_8/libweblogicoci37.so
    0xe1400000 /opt/oracle/lib/libclntsh.so.8.0
    0xfac90000 /usr/lib/libC.so.5
    0xfadb0000 /opt/oracle/lib/libwtc8.so
    0xfad90000 /usr/lib/libgen.so.1
    0xfac70000 /usr/lib/libsched.so.1
    0xfac40000 /usr/lib/libaio.so.1
    0xfac20000 /opt/wlserver6.1/lib/solaris/oci816_8/libweblogicoxa37.so
    0xe8ad0000 /redis/tibco/rv6.6/lib/libtibrvj.so
    0xe8ab0000 /redis/tibco/rv6.6/lib/libtibrvcmq.so
    0xe89c0000 /redis/tibco/rv6.6/lib/libtibrvcm.so
    0xe8990000 /redis/tibco/rv6.6/lib/libtibrvft.so
    0xe8890000 /redis/tibco/rv6.6/lib/libtibrv.so
    0xe8870000 /usr/lib/libpthread.so.1
    0xe6fe0000 /opt/wlserver6.1/lib/solaris/libmuxer.so
    0xe6fc0000 /opt/wlserver6.1/lib/solaris/libweblogicunix1.so
    java Exception in the program due to the above reason:
    ======================================================
    java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException - with nested
    exception:
    [weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException]
         at weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
         at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
         at com.cme.clearing.jta.JThread.process(JThread.java:100)
         at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException - with nested
    exception:
    [weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException]
         at weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
         at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
         at com.cme.clearing.jta.JThread.process(JThread.java:100)
         at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException - with nested
    exception:
    [weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException]
         at weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
         at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
         at com.cme.clearing.jta.JThread.process(JThread.java:100)
         at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.rmi.RemoteException: Message was not sent because transaction is not active.
    Xid=0:a1ccd55d7f28edb9(795840),Status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 29 seconds
    Xid=0:a1ccd55d7f28edb9(795840),Status=Active,numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
    since begin=29,seconds left=30,activeThread=Thread[Thread-1,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
    since begin=68,seconds left=1,activeThread=Thread[Thread-1,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)
         at weblogic.transaction.internal.TransactionManagerImpl.sendRequest(TransactionManagerImpl.java:1155)
         at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:101)
         at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
         at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
         at $Proxy1.process(Unknown Source)
         at com.cme.clearing.jta.JThread.process(JThread.java:101)
         at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.rmi.RemoteException: Message was not sent because transaction is not active.
    Xid=1:a1ccd55d7f28edb9(6051803),Status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 29 seconds
    Xid=1:a1ccd55d7f28edb9(6051803),Status=Active,numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
    since begin=29,seconds left=30,activeThread=Thread[Thread-2,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
    since begin=69,seconds left=0,activeThread=Thread[Thread-2,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)
         at weblogic.transaction.internal.TransactionManagerImpl.sendRequest(TransactionManagerImpl.java:1155)
         at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:101)
         at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
         at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
         at $Proxy1.process(Unknown Source)
         at com.cme.clearing.jta.JThread.process(JThread.java:101)
         at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.rmi.RemoteException: Message was not sent because transaction is not active.
    Xid=2:a1ccd55d7f28edb9(4244097),Status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 33 seconds
    Xid=2:a1ccd55d7f28edb9(4244097),Status=Active,numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
    since begin=33,seconds left=30,activeThread=Thread[Thread-3,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
    since begin=68,seconds left=5,activeThread=Thread[Thread-3,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)
         at weblogic.transaction.internal.TransactionManagerImpl.sendRequest(TransactionManagerImpl.java:1155)
         at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:101)
         at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
         at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
         at $Proxy1.process(Unknown Source)
         at com.cme.clearing.jta.JThread.process(JThread.java:101)
         at com.cme.clearing.jta.JThread.run(JThread.java:85)
    javax.naming.CommunicationException. Root exception is java.rmi.ConnectException:
    Unable to get direct or routed connection to: '-736127454917455663S:10.1.32.81:[8001,8001,8002,8002,8001,8002,-1]:mydomain:myserver'
         at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:255)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:222)
         at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
         at $Proxy0.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
         at javax.naming.InitialContext.lookup(InitialContext.java:350)
         at com.cme.clearing.jta.JContext.getTransaction(JContext.java:29)
         at com.cme.clearing.jta.JThread.startTransaction(JThread.java:67)
         at com.cme.clearing.jta.JThread.run(JThread.java:81)
    Exception null
    javax.naming.CommunicationException. Root exception is java.rmi.ConnectException:
    Unable to get direct or routed connection to: '-736127454917455663S:10.1.32.81:[8001,8001,8002,8002,8001,8002,-1]:mydomain:myserver'
         at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:255)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:222)
         at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
         at $Proxy0.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
         at javax.naming.InitialContext.lookup(InitialContext.java:350) Exception null
         at com.cme.clearing.jta.JContext.getTransaction(JContext.java:29)
         at com.cme.clearing.jta.JThread.startTransaction(JThread.java:67)
         at com.cme.clearing.jta.JThread.run(JThread.java:81)

    I see. Do you mean this code runs outside of the server? :
    at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
    at com.cme.clearing.jta.JThread.process(JThread.java:100)
    at com.cme.clearing.jta.JThread.run(JThread.java:85)
    Regards,
    Slava Imeshev
    "Tim" <[email protected]> wrote in message
    news:[email protected]...
    >
    Slava,
    In my case, I'm not spawning any threads.
    Regards,
    Tim
    "Slava Imeshev" <[email protected]> wrote:
    That could be a trace of some threading issue. Note that EJB spec
    prohibits
    using threads within a container.
    Regards,
    Slava Imeshev
    "Tim" <[email protected]> wrote in message
    news:[email protected]...
    Nagoor,
    Did anybody respond? I'm getting the same exception with the sameenvironment configuration
    but using WLS 6.1 SP2.
    Tim
    "Nagoor Haja" <[email protected]> wrote:
    Hi,
    I'm getting a native code exception which causes the Weblogic server
    to
    crash when
    using XA drivers for transaction with two oracle databases. Myapplication
    uses RMI
    and threads.
    I'm using BEA's jDriver for Oracle running under Weblogic server 6.1sp1
    talking
    to Oracle 8.1.6. The OS is Solaris 2.8.
    In middle of the program execution it's giving this problem. I'm
    using
    jdk131 in
    solaris platform.
    Any idea what's going on here ?
    Thanks,
    Nagoor Haja
    Exception in the Log file:
    ===========================
    An unexpected exception has been detected in native code outside theVM.
    Unexpected Signal : 11 occurred at PC=0xff2414d8
    Function name=madvise
    Library=/usr/lib/libc.so.1
    Current Java thread:
    at weblogic.jdbc.oci.xa.XA.native_commit(Native Method)
    at weblogic.jdbc.oci.xa.XA.commit(XA.java:136)
    atweblogic.jdbc.oci.xa.XADataSource.commit(XADataSource.java:696)
    at weblogic.jdbc.jta.DataSource.commit(DataSource.java:784)
    at
    weblogic.transaction.internal.ServerResourceInfo.commit(ServerResourceInfo.j
    ava:1180)
    at
    weblogic.transaction.internal.ServerResourceInfo.commit(ServerResourceInfo.j
    ava:419)
    at
    weblogic.transaction.internal.ServerSCInfo.startCommit(ServerSCInfo.java:233
    at
    weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransa
    ctionImpl.java:1397)
    at
    weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(Server
    TransactionImpl.java:1940)
    at
    weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTrans
    actionImpl.java:1886)
    at
    weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
    nsactionImpl.java:221)
    at
    weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
    Impl.java:190)
    at
    weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
    atweblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown
    Source)
    atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Dynamic libraries:
    0x10000 /opt/jdk131/jre/bin/../bin/sparc/native_threads/java
    0xff350000 /usr/lib/libthread.so.1
    0xff390000 /usr/lib/libdl.so.1
    0xff200000 /usr/lib/libc.so.1
    0xff330000 /usr/platform/SUNW,Ultra-60/lib/libc_psr.so.1
    0xfe480000 /opt/jdk131/jre/lib/sparc/hotspot/libjvm.so
    0xff2e0000 /usr/lib/libCrun.so.1
    0xff1e0000 /usr/lib/libsocket.so.1
    0xff100000 /usr/lib/libnsl.so.1
    0xff0d0000 /usr/lib/libm.so.1
    0xff100000 /usr/lib/libnsl.so.1
    0xff0d0000 /usr/lib/libm.so.1
    0xff310000 /usr/lib/libw.so.1
    0xff0b0000 /usr/lib/libmp.so.2
    0xff080000 /opt/jdk131/jre/lib/sparc/native_threads/libhpi.so
    0xff050000 /opt/jdk131/jre/lib/sparc/libverify.so
    0xfe440000 /opt/jdk131/jre/lib/sparc/libjava.so
    0xff020000 /opt/jdk131/jre/lib/sparc/libzip.so
    0xfafb0000 /opt/jdk131/jre/lib/sparc/libnet.so
    0xfadd0000 /usr/lib/nss_files.so.1
    0xe1d00000/opt/wlserver6.1/lib/solaris/oci816_8/libweblogicoci37.so
    0xe1400000 /opt/oracle/lib/libclntsh.so.8.0
    0xfac90000 /usr/lib/libC.so.5
    0xfadb0000 /opt/oracle/lib/libwtc8.so
    0xfad90000 /usr/lib/libgen.so.1
    0xfac70000 /usr/lib/libsched.so.1
    0xfac40000 /usr/lib/libaio.so.1
    0xfac20000/opt/wlserver6.1/lib/solaris/oci816_8/libweblogicoxa37.so
    0xe8ad0000 /redis/tibco/rv6.6/lib/libtibrvj.so
    0xe8ab0000 /redis/tibco/rv6.6/lib/libtibrvcmq.so
    0xe89c0000 /redis/tibco/rv6.6/lib/libtibrvcm.so
    0xe8990000 /redis/tibco/rv6.6/lib/libtibrvft.so
    0xe8890000 /redis/tibco/rv6.6/lib/libtibrv.so
    0xe8870000 /usr/lib/libpthread.so.1
    0xe6fe0000 /opt/wlserver6.1/lib/solaris/libmuxer.so
    0xe6fc0000 /opt/wlserver6.1/lib/solaris/libweblogicunix1.so
    java Exception in the program due to the above reason:
    ======================================================
    java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException-
    with nested
    exception:
    [weblogic.rjvm.PeerGoneException: ; nested exception is:
    java.io.EOFException]
    at
    weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
    >>>>
    at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
    at com.cme.clearing.jta.JThread.process(JThread.java:100)
    at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException-
    with nested
    exception:
    [weblogic.rjvm.PeerGoneException: ; nested exception is:
    java.io.EOFException]
    at
    weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
    >>>>
    at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
    at com.cme.clearing.jta.JThread.process(JThread.java:100)
    at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException-
    with nested
    exception:
    [weblogic.rjvm.PeerGoneException: ; nested exception is:
    java.io.EOFException]
    at
    weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
    >>>>
    at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
    at com.cme.clearing.jta.JThread.process(JThread.java:100)
    at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.rmi.RemoteException: Message was not sent because transaction isnot
    active.
    Xid=0:a1ccd55d7f28edb9(795840),Status=Rolled back.[Reason=weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 29 seconds
    Xid=0:a1ccd55d7f28edb9(795840),Status=Active,numRepliesOwedMe=1,numReplies
    O
    wedOthers=0,seconds
    since begin=29,seconds
    left=30,activeThread=Thread[Thread-1,5,main],spatidbxa,SCInfo[mydomain+myser
    >
    ver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordin
    >
    atorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOw
    edOthers=0,seconds
    since begin=68,seconds
    left=1,activeThread=Thread[Thread-1,5,main],spatidbxa,SCInfo[mydomain+myserv
    >
    er]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordina
    torURL=myserver+10.1.32.81:8001+mydomain+)
    at
    weblogic.transaction.internal.TransactionManagerImpl.sendRequest(Transaction
    ManagerImpl.java:1155)
    at
    weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:
    101)
    at
    weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
    >>>>
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy1.process(Unknown Source)
    at com.cme.clearing.jta.JThread.process(JThread.java:101)
    at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.rmi.RemoteException: Message was not sent because transaction isnot
    active.
    Xid=1:a1ccd55d7f28edb9(6051803),Status=Rolled back.[Reason=weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 29 seconds
    Xid=1:a1ccd55d7f28edb9(6051803),Status=Active,numRepliesOwedMe=1,numReplie
    s
    OwedOthers=0,seconds
    since begin=29,seconds
    left=30,activeThread=Thread[Thread-2,5,main],spatidbxa,SCInfo[mydomain+myser
    >
    ver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordin
    >
    atorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOw
    edOthers=0,seconds
    since begin=69,seconds
    left=0,activeThread=Thread[Thread-2,5,main],spatidbxa,SCInfo[mydomain+myserv
    >
    er]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordina
    torURL=myserver+10.1.32.81:8001+mydomain+)
    at
    weblogic.transaction.internal.TransactionManagerImpl.sendRequest(Transaction
    ManagerImpl.java:1155)
    at
    weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:
    101)
    at
    weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
    >>>>
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy1.process(Unknown Source)
    at com.cme.clearing.jta.JThread.process(JThread.java:101)
    at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.rmi.RemoteException: Message was not sent because transaction isnot
    active.
    Xid=2:a1ccd55d7f28edb9(4244097),Status=Rolled back.[Reason=weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 33 seconds
    Xid=2:a1ccd55d7f28edb9(4244097),Status=Active,numRepliesOwedMe=1,numReplie
    s
    OwedOthers=0,seconds
    since begin=33,seconds
    left=30,activeThread=Thread[Thread-3,5,main],spatidbxa,SCInfo[mydomain+myser
    >
    ver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordin
    >
    atorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOw
    edOthers=0,seconds
    since begin=68,seconds
    left=5,activeThread=Thread[Thread-3,5,main],spatidbxa,SCInfo[mydomain+myserv
    >
    er]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordina
    torURL=myserver+10.1.32.81:8001+mydomain+)
    at
    weblogic.transaction.internal.TransactionManagerImpl.sendRequest(Transaction
    ManagerImpl.java:1155)
    at
    weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:
    101)
    at
    weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
    >>>>
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy1.process(Unknown Source)
    at com.cme.clearing.jta.JThread.process(JThread.java:101)
    at com.cme.clearing.jta.JThread.run(JThread.java:85)
    javax.naming.CommunicationException. Root exception isjava.rmi.ConnectException:
    Unable to get direct or routed connection to:
    '-736127454917455663S:10.1.32.81:[8001,8001,8002,8002,8001,8002,-1]:mydomain
    :myserver'
    at
    weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
    java:85)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :255)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :222)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy0.lookup(Unknown Source)
    at
    weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
    >>>>
    at javax.naming.InitialContext.lookup(InitialContext.java:350)
    at com.cme.clearing.jta.JContext.getTransaction(JContext.java:29)
    at com.cme.clearing.jta.JThread.startTransaction(JThread.java:67)
    at com.cme.clearing.jta.JThread.run(JThread.java:81)
    Exception null
    javax.naming.CommunicationException. Root exception isjava.rmi.ConnectException:
    Unable to get direct or routed connection to:
    '-736127454917455663S:10.1.32.81:[8001,8001,8002,8002,8001,8002,-1]:mydomain
    :myserver'
    at
    weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
    java:85)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :255)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :222)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy0.lookup(Unknown Source)
    at
    weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
    >>>>
    at javax.naming.InitialContext.lookup(InitialContext.java:350)Exception
    null
    at com.cme.clearing.jta.JContext.getTransaction(JContext.java:29)
    at com.cme.clearing.jta.JThread.startTransaction(JThread.java:67)
    at com.cme.clearing.jta.JThread.run(JThread.java:81)

  • BEA WebLogic jDriver for Microsoft SQL Server

    Will BEA continue to support current and future installations of WebLogic jDriver for Microsoft SQL Server 2000 even though BEA recommends to use the JDBC driver available from Microsoft? A written response is necessary in order to determine our future product development direction.
    Thank you for your attention regarding this matter.

    Actually, this driver is already documented as deprecated. We intended to remove it from a future
    release (most likely, the release after WLS 8.1).
    The plan is to ship another driver out-of-the-box. We have been evaluating various drivers
    for features, quality, and performance. We are pushing very hard to have this replacement
    driver available in 8.1SP01, which will also ship with the WLI/Portal/WLW GA (announced to
    ship in July). The most likely candidate is already in testing both at the WLS level and
    with the layered products. It also did quite well in an internal performance comparison.
    "Joseph Weinstein" <[email protected]_this> wrote in message news:[email protected]_this...
    >
    >
    Peter Foskaris wrote:
    Will BEA continue to support current and future installations of WebLogic jDriver for Microsoft SQL Server 2000 even though
    BEA recommends to use the JDBC driver available from Microsoft? A written response is necessary in order to determine our future
    product development direction.
    >>
    Thank you for your attention regarding this matter.Hi. We intend to deprecate it. We may or may not fix bugs that are found in it in future, and will likely
    not do any more development on it, such as implementing any JDBC 2.0 methods. It will be in
    our next major release (8), but may not be in future ones.
    Joe Weinstein at BEA

  • JDK1.3 for "jDriver for Oracle"

    Hi,
    I'm developing for RMI/IIOP by using WLS5.1,JDK1.3 and Oracle8.
    Is it possible to use JDK1.3 for "jDriver for Oracle"? And also, when it
    will be added to Support Platform??

    I dunno about Oracle 8... ask Oracle... 1.3 is supported now.
    Teru Yoshikoshi wrote:
    Hi,
    I'm developing for RMI/IIOP by using WLS5.1,JDK1.3 and Oracle8.
    Is it possible to use JDK1.3 for "jDriver for Oracle"? And also, when it
    will be added to Support Platform??

  • Weblogic license for Oracle IRM

    There are 3 versions of weblogic available now according to e14860 Oracle® Fusion Middleware Licensing Information.pdf
    1)Standard
    2)Enterprise
    3)Weblogic Suite
    Definitely we need enterprise as it has clustering capability. What I don’t know for sure is that whether we need weblogic suite for Oracle IRM?
    Can anyone shed some light on this.
    thanks
    k

    No, the WebLogic Server you choose depends on your individual business needs. Therefore this is something that should be part of the installation scoping process.
    Regards,
    Frank.

  • JDriver for Oracle 9.2

    I am running Weblogic 5.x and want to connect to an Oracle 9.2 database. The jDriver
    dll files that shipped with my version of Weblogic only go up to 8.1.5.
    Is there any way I can download the appropriate jDriver dll files without attempting
    to download a more recent version of Weblogic? I haven't had any success searching
    for only the jDriver files.
    Any help would be greatly appreciated.
    Thanks
    Robert

    Thanks Mitesh. The version I am currently running has the folder oci815_8, which
    I assume is for Oracle 8.1.5.8. Will that one work? If not, where can I go to
    get the 817 jDriver?
    Mitesh Patel <[email protected]> wrote:
    With latest 5.1x weblogic release, we ship 817 jDriver which you can
    use. Also, you can
    not use drivers from different weblogic releases on 5.1x.
    Thanks,
    Mitesh
    Robert Eovine wrote:
    I am running Weblogic 5.x and want to connect to an Oracle 9.2 database.The jDriver
    dll files that shipped with my version of Weblogic only go up to 8.1.5.
    Is there any way I can download the appropriate jDriver dll files withoutattempting
    to download a more recent version of Weblogic? I haven't had any successsearching
    for only the jDriver files.
    Any help would be greatly appreciated.
    Thanks
    Robert

  • JDriver for Oracle crashes JVm on solaris

    Hi,
    I'm using the weblogic jDriver/XA for oracle with oracle 8.1.7 on solaris 2.8.
    The weblogic version is 6.1 SP2.
    The JVM randomly crashes with this error:
    Is the jDriver/XA that comes with weblogic stable ?
    Has the jDriver that comes with wlserver 6.1 SP3 fixed this problem ?
    Unexpected Signal : 11 occurred at PC=0xfe557f64
    Function name=JVM_InternString
    Library=/bea/jdk131/jre/lib/sparc/hotspot/libjvm.so
    Current Java thread:
         at weblogic.jdbc.oci.xa.XA.native_start(Native Method)
         at weblogic.jdbc.oci.xa.XA.start(XA.java:70)
         at weblogic.jdbc.oci.xa.XADataSource.start(XADataSource.java:640)
         at weblogic.jdbc.jta.DataSource.detectedUnavailable(DataSource.java:445)
         at weblogic.transaction.internal.ResourceDescriptor$2.execute(ResourceDescriptor.java:991)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Dynamic libraries:
    0x10000      /bea/jdk131/jre/bin/../bin/sparc/native_threads/java
    0xff350000      /usr/lib/libthread.so.1
    0xff390000      /usr/lib/libdl.so.1
    0xff200000      /usr/lib/libc.so.1
    0xff330000      /usr/platform/SUNW,Ultra-60/lib/libc_psr.so.1
    0xfe400000      /bea/jdk131/jre/lib/sparc/hotspot/libjvm.so
    0xff2e0000      /usr/lib/libCrun.so.1
    0xff1e0000      /usr/lib/libsocket.so.1
    0xff100000      /usr/lib/libnsl.so.1
    0xff0d0000      /usr/lib/libm.so.1
    0xff310000      /usr/lib/libw.so.1
    0xff0b0000      /usr/lib/libmp.so.2
    0xff080000      /bea/jdk131/jre/lib/sparc/native_threads/libhpi.so
    0xff050000      /bea/jdk131/jre/lib/sparc/libverify.so
    0xfe7c0000      /bea/jdk131/jre/lib/sparc/libjava.so
    0xff020000      /bea/jdk131/jre/lib/sparc/libzip.so
    0xfe3b0000      /usr/lib/locale/en_US.ISO8859-1/en_US.ISO8859-1.so.2
    0xfe390000      /bea/jdk131/jre/lib/sparc/libnet.so
    0xfaed0000      /usr/lib/nss_files.so.1
    0xd9200000      /bea/wlserver6.1/lib/solaris/oci817_8/libweblogicoci37.so
    0xd8400000      /u01/app/oracle/product/8.1.7/lib/libclntsh.so.8.0
    0xfad90000      /usr/lib/libC.so.5
    0xfaea0000      /u01/app/oracle/product/8.1.7/lib/libwtc8.so
    0xface0000      /usr/lib/libgen.so.1
    0xfacc0000      /usr/lib/libsched.so.1
    0xfaca0000      /usr/lib/libaio.so.1
    0xfac80000      /bea/wlserver6.1/lib/solaris/oci817_8/libweblogicoxa37.so
    0xfac10000      /bea/jdk131/jre/lib/sparc/libioser12.so
    0xdeae0000      /bea/jdk131/jre/lib/sparc/libawt.so
    0xd7480000      /bea/jdk131/jre/lib/sparc/motif21/libmawt.so
    0xdc8b0000      /bea/jdk131/jre/bin/../lib/sparc/libmlib_image.so
    0xd7200000      /usr/dt/lib/libXm.so.4
    0xd7190000      /usr/openwin/lib/libXt.so.4
    0xdc7d0000      /usr/openwin/lib/libXext.so.0
    0xdce60000      /usr/openwin/lib/libXtst.so.1
    0xd7080000      /usr/openwin/lib/libX11.so.4
    0xdc7b0000      /usr/openwin/lib/libSM.so.6
    0xdc6d0000      /usr/openwin/lib/libICE.so.6
    0xdc6a0000      /usr/openwin/lib/libdga.so.1
    0xd6f80000      /bea/jdk131/jre/lib/sparc/libfontmanager.so
    0xdc5a0000      /usr/openwin/lib/libdps.so.5
    0xdc4c0000      /bea/jdk131/jre/lib/sparc/libdcpr.so
    0xdc3b0000      /bea/jdk131/jre/lib/sparc/libcmm.so
    0xdc2c0000      /bea/jdk131/jre/lib/sparc/libjpeg.so
    0xdc890000      /bea/wlserver6.1/lib/solaris/libmuxer.so
    0xdc4a0000      /usr/ucblib/libucb.so.1
    0xdc790000      /usr/lib/libresolv.so.1
    0xdc1c0000      /usr/lib/libelf.so.1
    Local Time = Sun Aug 25 19:12:47 2002
    Elapsed Time = 21231
    # HotSpot Virtual Machine Error : 11
    # Error ID : 4F530E43505002BD 01
    # Please report this error at
    # http://java.sun.com/cgi-bin/bugreport.cgi
    # Java VM: Java HotSpot(TM) Client VM (1.3.1_04-b02 mixed mode)
    # An error report file has been saved as hs_err_pid342.log.
    # Please refer to the file for further information.

    We have observed some problems for XA in oracle 817 client. You should use 901 client and 901 jDriver
    to talk to 817 database as a solution.
    Mitesh
    prajod wrote:
    Hi,
    I'm using the weblogic jDriver/XA for oracle with oracle 8.1.7 on solaris 2.8.
    The weblogic version is 6.1 SP2.
    The JVM randomly crashes with this error:
    Is the jDriver/XA that comes with weblogic stable ?
    Has the jDriver that comes with wlserver 6.1 SP3 fixed this problem ?
    Unexpected Signal : 11 occurred at PC=0xfe557f64
    Function name=JVM_InternString
    Library=/bea/jdk131/jre/lib/sparc/hotspot/libjvm.so
    Current Java thread:
    at weblogic.jdbc.oci.xa.XA.native_start(Native Method)
    at weblogic.jdbc.oci.xa.XA.start(XA.java:70)
    at weblogic.jdbc.oci.xa.XADataSource.start(XADataSource.java:640)
    at weblogic.jdbc.jta.DataSource.detectedUnavailable(DataSource.java:445)
    at weblogic.transaction.internal.ResourceDescriptor$2.execute(ResourceDescriptor.java:991)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Dynamic libraries:
    0x10000 /bea/jdk131/jre/bin/../bin/sparc/native_threads/java
    0xff350000 /usr/lib/libthread.so.1
    0xff390000 /usr/lib/libdl.so.1
    0xff200000 /usr/lib/libc.so.1
    0xff330000 /usr/platform/SUNW,Ultra-60/lib/libc_psr.so.1
    0xfe400000 /bea/jdk131/jre/lib/sparc/hotspot/libjvm.so
    0xff2e0000 /usr/lib/libCrun.so.1
    0xff1e0000 /usr/lib/libsocket.so.1
    0xff100000 /usr/lib/libnsl.so.1
    0xff0d0000 /usr/lib/libm.so.1
    0xff310000 /usr/lib/libw.so.1
    0xff0b0000 /usr/lib/libmp.so.2
    0xff080000 /bea/jdk131/jre/lib/sparc/native_threads/libhpi.so
    0xff050000 /bea/jdk131/jre/lib/sparc/libverify.so
    0xfe7c0000 /bea/jdk131/jre/lib/sparc/libjava.so
    0xff020000 /bea/jdk131/jre/lib/sparc/libzip.so
    0xfe3b0000 /usr/lib/locale/en_US.ISO8859-1/en_US.ISO8859-1.so.2
    0xfe390000 /bea/jdk131/jre/lib/sparc/libnet.so
    0xfaed0000 /usr/lib/nss_files.so.1
    0xd9200000 /bea/wlserver6.1/lib/solaris/oci817_8/libweblogicoci37.so
    0xd8400000 /u01/app/oracle/product/8.1.7/lib/libclntsh.so.8.0
    0xfad90000 /usr/lib/libC.so.5
    0xfaea0000 /u01/app/oracle/product/8.1.7/lib/libwtc8.so
    0xface0000 /usr/lib/libgen.so.1
    0xfacc0000 /usr/lib/libsched.so.1
    0xfaca0000 /usr/lib/libaio.so.1
    0xfac80000 /bea/wlserver6.1/lib/solaris/oci817_8/libweblogicoxa37.so
    0xfac10000 /bea/jdk131/jre/lib/sparc/libioser12.so
    0xdeae0000 /bea/jdk131/jre/lib/sparc/libawt.so
    0xd7480000 /bea/jdk131/jre/lib/sparc/motif21/libmawt.so
    0xdc8b0000 /bea/jdk131/jre/bin/../lib/sparc/libmlib_image.so
    0xd7200000 /usr/dt/lib/libXm.so.4
    0xd7190000 /usr/openwin/lib/libXt.so.4
    0xdc7d0000 /usr/openwin/lib/libXext.so.0
    0xdce60000 /usr/openwin/lib/libXtst.so.1
    0xd7080000 /usr/openwin/lib/libX11.so.4
    0xdc7b0000 /usr/openwin/lib/libSM.so.6
    0xdc6d0000 /usr/openwin/lib/libICE.so.6
    0xdc6a0000 /usr/openwin/lib/libdga.so.1
    0xd6f80000 /bea/jdk131/jre/lib/sparc/libfontmanager.so
    0xdc5a0000 /usr/openwin/lib/libdps.so.5
    0xdc4c0000 /bea/jdk131/jre/lib/sparc/libdcpr.so
    0xdc3b0000 /bea/jdk131/jre/lib/sparc/libcmm.so
    0xdc2c0000 /bea/jdk131/jre/lib/sparc/libjpeg.so
    0xdc890000 /bea/wlserver6.1/lib/solaris/libmuxer.so
    0xdc4a0000 /usr/ucblib/libucb.so.1
    0xdc790000 /usr/lib/libresolv.so.1
    0xdc1c0000 /usr/lib/libelf.so.1
    Local Time = Sun Aug 25 19:12:47 2002
    Elapsed Time = 21231
    # HotSpot Virtual Machine Error : 11
    # Error ID : 4F530E43505002BD 01
    # Please report this error at
    # http://java.sun.com/cgi-bin/bugreport.cgi
    # Java VM: Java HotSpot(TM) Client VM (1.3.1_04-b02 mixed mode)
    # An error report file has been saved as hs_err_pid342.log.
    # Please refer to the file for further information.

  • How to turn of debug output from the jdriver for Oracle

    We are running our builds with Ant and doing unit-tests with junit/cactus.
    The Weblogic jDriver produces what appears to be debug info on standard out which
    in turn is captured by junit in xml files reporting errors etc. The problem is that
    the WebLogic driver ( WL6.1 SP2) sometimes produces binary 0's ( see below) ending
    up in the result xml files, and that Ant's result xml parser cannot handle - (nor
    should it ).
    This is probably a bug in the c-code for the jdriver , the oci dll ?
    Would much appreciate how to turn off the debug(?) logging that the jDriver does:
    looks like this (look for the string "[6 binary 0's]"):
    Parsing: select length(SYSDATE) from dual
    Executing: select length(SYSDATE) from dual
    Parsing: select VALUE from V$NLS_PARAMETERS where PARAMETER='NLS_NUMERIC_CHARACTERS'
    Executing: select VALUE from V$NLS_PARAMETERS where PARAMETER='NLS_NUMERIC_CHARACTERS'
    Done logging in at: 60
    Connection: using OCI API: OCI8[6 binary 0's]
    Connection successfully established via plain JDBC
    DriverManager.getDriver("jdbc:weblogic:oracle:LSS_DBSVC_DEV_autobuild")
    trying driver[className=weblogic.jdbc.oci.Driver,weblogic.jdbc.oci.Driver@3383e9]
    getDriver returning driver[className=weblogic.jdbc.oci.Driver,weblogic.jdbc.oci.Driver@3383e9]

    Hi Gunnar,
    I'd check your code for appearances of "DriverManager.setLogWriter" that set
    log writer to System.out. This is the way to get driver's debug output
    to standard out.
    Regards,
    Slava Imeshev
    "Gunnar Skogen" <[email protected]> wrote in message
    news:3d2972bb$[email protected]..
    >
    We are running our builds with Ant and doing unit-tests with junit/cactus.
    The Weblogic jDriver produces what appears to be debug info on standardout which
    in turn is captured by junit in xml files reporting errors etc. Theproblem is that
    the WebLogic driver ( WL6.1 SP2) sometimes produces binary 0's ( seebelow) ending
    up in the result xml files, and that Ant's result xml parser cannothandle - (nor
    should it ).
    This is probably a bug in the c-code for the jdriver , the oci dll ?
    Would much appreciate how to turn off the debug(?) logging that thejDriver does:
    looks like this (look for the string "[6 binary 0's]"):
    Parsing: select length(SYSDATE) from dual
    Executing: select length(SYSDATE) from dual
    Parsing: select VALUE from V$NLS_PARAMETERS wherePARAMETER='NLS_NUMERIC_CHARACTERS'
    Executing: select VALUE from V$NLS_PARAMETERS wherePARAMETER='NLS_NUMERIC_CHARACTERS'
    Done logging in at: 60
    Connection: using OCI API: OCI8[6 binary 0's]
    Connection successfully established via plain JDBC
    DriverManager.getDriver("jdbc:weblogic:oracle:LSS_DBSVC_DEV_autobuild")
    tryingdriver[className=weblogic.jdbc.oci.Driver,weblogic.jdbc.oci.Driver@3383e9]
    getDriver returningdriver[className=weblogic.jdbc.oci.Driver,weblogic.jdbc.oci.Driver@3383e9]
    >
    >

  • Weblogic's jDriver for Oracle

    Hi!
    I get the following exception when I run utils.dbping.
    (I have added %WL_HOME%\bin\oci817_8 and %ORACLE_HOME%\bin to the path. I have
    an evaluation copy of weblogic and I use the driver that comes along with the
    server download.)
    C:\javapgms\java\sql>java utils.dbping oracle scott tiger demo Missing license
    file for: WebLogic Server 6.1
    Error encountered:
    java.sql.SQLException: Fail to load jDriver/Oracle due to license checking faile
    d!
    at weblogic.jdbc.oci.Driver.loadLibraryIfNeeded(Driver.java:182)
    at weblogic.jdbc.oci.Driver.connect(Driver.java:76)
    at java.sql.DriverManager.getConnection(DriverManager.java:517)
    at java.sql.DriverManager.getConnection(DriverManager.java:146)
    at utils.dbping.main(dbping.java:167)
    Can someone tell me what the problem could be?
    Thanks

    Hi,
    I think the error is pretty clear: Make sure that you have a valid
    license file in your bea directory, it should be named "license.bea".
    You need a license for using the jDriver.
    Nils
    Raj wrote:
    >
    Hi!
    I get the following exception when I run utils.dbping.
    (I have added %WL_HOME%\bin\oci817_8 and %ORACLE_HOME%\bin to the path. I have
    an evaluation copy of weblogic and I use the driver that comes along with the
    server download.)
    C:\javapgms\java\sql>java utils.dbping oracle scott tiger demo Missing license
    file for: WebLogic Server 6.1
    Error encountered:
    java.sql.SQLException: Fail to load jDriver/Oracle due to license checking faile
    d!
    at weblogic.jdbc.oci.Driver.loadLibraryIfNeeded(Driver.java:182)
    at weblogic.jdbc.oci.Driver.connect(Driver.java:76)
    at java.sql.DriverManager.getConnection(DriverManager.java:517)
    at java.sql.DriverManager.getConnection(DriverManager.java:146)
    at utils.dbping.main(dbping.java:167)
    Can someone tell me what the problem could be?
    Thanks--
    ============================
    [email protected]

Maybe you are looking for

  • AUR Pkgbuild and Node.js

    If my package needs some nodejs packages to build/run, it's preferred to install them through AUR (when provided) or just add a line npm install -g name_of_the_package into build() function? Keep in mind that if the package has been already installed

  • Entry restriction in maintenance view

    i have created a maintenance view in which user input and save..its working fine.now my requirement is that user should not be able to enter freely in the fields..means only values from database. like if field is customer then only value came from f4

  • How to set about:newtab as permanent tab page adress

    I changed browser.newtab.url to about:newtab, but everytime I reboot my computer it gets back to about:blank. How can I set the about:newtab to my perm tab page adress when I open a new tabpage?

  • Maintenance Order Components Error IW32

    Hi all, Please guide me on below error log: while going into components from IW32 screen against maintenance order number (It is against functional location only) - it is giving an error :: Business transaction could not be carried out Reference obje

  • Sales document type is not defined for(sales org/division/distribution chan

    Hi Friends, I am getting the error that sales document type is not defined for x/y/z(sales organisation/division/distribution channel). while creating sales order. Any pointers will be rewarded. Regards