WebLogic MultiPool Vs Oracle FCF

I am checking on whats the most efficient way to utilize Oracle RAC from weblogic application server perspective.
Based on the information available, it looks like weblogic multiPool has the functionalities (if not better) than what Oracle FCF offers.
Can some one from BEA/Oracle and anyone who evaluated both the approaches comment on this. (considering both XA and non XA connections).
Going forward what would the reccommended approach?
-Vijay

Definitely use MultiPools. FCF does not support XA, and FCF fails over connection-by-connection
whereas MP can know about the DBMS connectivity state from the first couple of failed
connections, and be able to fail over to the other pool immediately, and fix up/close the
remaining dead connections in the other pool asynchronously.

Similar Messages

Build Issue(package weblogic.jdbc.vendor.oracle does not exist) weblogic10

Hi All,
I am getting below build error. I am migrating weblogic 10. Which jar file contains this interface: weblogic.jdbc.vendor.oracle.OracleThinClob?
Error:
package weblogic.jdbc.vendor.oracle does not exist [javac] if (theClob instanceof weblogic.jdbc.vendor.oracle.OracleThinClob)
I already got weblogic.jar file from weblogic 10.
Thanks,
Srinivas

Srinivas U wrote:
Hi All,
I am getting below build error. I am migrating weblogic 10. Which jar file contains this interface: weblogic.jdbc.vendor.oracle.OracleThinClob?
Error:
package weblogic.jdbc.vendor.oracle does not exist [javac] if (theClob instanceof weblogic.jdbc.vendor.oracle.OracleThinClob)
I already got weblogic.jar file from weblogic 10.
Thanks,
SrinivasIt's in the datasource module/jar: modules/com.bea.core.datasource_1.0.0.0.jar

WebLogic Portal vs Oracle Portal

Anyone know the differences in term of features of WebLogic Portal and Oracle Portal?
i) WebLogic Portal supports Web 2.0 while Oracle Portal doesn't?
ii) Oracle Portal provides SSO to oracle applications while WebLogic Portal doesn't?
Any other different features?
Please advise, thanks.

There are lots of differences, but I think you should post your question in the WebCenter and Web 2.0 Technology forum with some additional detail as to why you are asking:
WebCenter Portal
For example, are you making a technology choice for a particular project? What portal requirements do you have? What are the skillsets of those who will be implementing, etc.
The long term strategy is to converge on the WebCenter product, but there are nuances that may make other portal products a better fit in the short-term.

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
 >

Weblogic setting the Oracle password

Hi,
I have a problem with an Oracle 8.1.7 database and Weblogic Server 6.0 sp2 both
running on an HPUX 11 Unix box in that everytime I start Weblogic it sets the
Oracle password to be the value of the Orarcle sid. I have configured Weblogic
to have a Connection Pool to the database.
Anyone have any clues?
Regards,
Dave.

can you post your connection pool settings?
sree
"David Fletcher" <[email protected]> wrote in message
news:3bc5f5cf$[email protected]..
>
Hi,
I have a problem with an Oracle 8.1.7 database and Weblogic Server 6.0 sp2both
running on an HPUX 11 Unix box in that everytime I start Weblogic it setsthe
Oracle password to be the value of the Orarcle sid. I have configuredWeblogic
to have a Connection Pool to the database.
Anyone have any clues?
Regards,
Dave.

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]

Any kind of integration experience with Weblogic JMS and Oracle AQ?

Hi,
In my company I work with java developers who believe in some kind of "holly" database independence I don't understand and as a result my life as a database developer is hell on earth.. Yesterday we again started to discuss, this time where to log, they believe database is slow and prefer logging to filesystem, after some hours finally I could convince them for some operational and reporting needs to use the database and will do this in an asyncronous way whiich they won't get slow. After all I believe the reason for a database is data, this is the place where data lives, and with the correct desing and implementation logging to database would perform better.
I love Oracle features, and know that we paid a lot for this software, so today I started investigating this promised solution. And quickly I found AQ and JMS topics in the documentation :)
After this introduction here is my problem; my company use BEA Weblogic as application server and the java guys want AQ to automatically (but of course with some delay) take their JMS log requests into database tables. Does any one have similar application experience, or any kind of integration experience with Weblogic JMS and Oracle AQ?
Any comments, references, documentation, sample code, url will be most welcomed :)
Thank you very much!
Tonguc
[email protected]
References I found upto now;
Oracle® Streams Advanced Queuing Java API Reference 10g Release 2 (10.2) http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14291/toc.htm
(Packages; javax.jms & oracle.jms)
Oracle® Streams Advanced Queuing User's Guide and Reference 10g Release 2 (10.2) http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14257/toc.htm
Part IV
Using Oracle JMS and Oracle Streams AQPart V describes how to use Oracle JMS and Oracle Streams Advanced Queuing (AQ).
Chapter 11, "Introducing Oracle JMS"
Chapter 12, "Oracle JMS Basic Operations"
Chapter 13, "Oracle JMS Point-to-Point"
Chapter 14, "Oracle JMS Publish/Subscribe"
Chapter 15, "Oracle JMS Shared Interfaces"
Chapter 16, "Oracle JMS Types Examples"
A Sample Code from Otn
http://www.oracle.com/technology/sample_code/tech/java/web_services/jmsws/NewsQueueEJB.java.html

I wouldn't go as far to say Oracle AQ is out-dated today. However, it is indeed a proprietary technology that did not found much main-stream adoption in the earlier years after its introduction. The advent of JMS made it somewhat more useful (or should I say intriguing, because more people are trying to tie it together with other J2EE technologies), but the Oracle's JMS wrapper classes in aqapi.jar were not feature complete for a long while, so using it outside Oracle's application server was painful, if not impossible. I do agree that the info at the dev2dev's JMS newsgroup or in this forum is highly fragmented, as neither Oracle nor BEA provides an official solution to integrate AQ with WebLogic, so people like us have to learn the technology through experimentation and in a piecemeal fashion.
3 years ago I was literally "playing around" - we had a polling mechanism set up to use triggers to write Oracle data changes into an event table, and had a Java-based daemon to scan that table and publish events as JMS messages to the WebLogic JMS server. This continues to work reliably till today, but I was looking for a solution that has few parts - I wanted to hook up my WebLogic MDB directly to AQ as a foreign JMS provider. Although I was able to get it to work (including XA), there were a few hoops I had to jump through, such as decompiling the Oracle AQjms classes to make them bind to the WebLogic JNDI tree.
One year after that Diptanshu Parui took what I did a giant step further - he extended the Oracle AQjms classes to allow them to be bound to the WebLogic JNDI tree naturally, and he figured out how to use WebLogic JMS messging bridge to re-send single-threaded AQ JMS messages to clustered JMS queues, which allow concurrent message assumption by multiple instances of MDB's. My impression is that he is using that setup in a production environment.
I am sure you are aware of it but I would like to make it clear - in order to use AQ as a foreign JMS provider to WebLogic-hosted MDB's, you don't need to update your database to Oracle 10g - Oracle 8i is good enough (although I recommend at least 9i Release 2). It is not the database engine, but rather the aqapi.jar JMS wrapper on top of AQ that matters. I do recommend that you use aqapi.jar from Oracle Application Server 10.0.3 or up for better XA support, among other things. Again, you don't have to replace WebLogic with Oracle AS - you only need a single jar file from it and put it in your WebLogic's classpath. However, I don't know what this means from a licensing point of view if you ever go to production - do you have to pay the full price of OracleAS or OC4J just to use the aqapi.jar?
In the coming days I will test the latest aqapi.jar to see how much progress Oracle has made in terms of making their J2EE products more spec-compliant :-).
Hope the above gives you a different perspective.
Eric

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

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.

Oracle.sql.ARRAY incompatible with weblogic.jdbc.vendor.oracle.OracleArray

Hi,
I am facing following issue in my one environment. but in other environment same class path is working fine. I have compared all jar and classpath for both weblogic server.
I am using weblogic 11g.
27 Mar 2013 15:21:09,507 ERROR XXXServlet:293 - oracle.sql.ARRAY incompatible with weblogic.jdbc.vendor.oracle.OracleArray
java.lang.ClassCastException: oracle.sql.ARRAY incompatible with weblogic.jdbc.vendor.oracle.OracleArray
at com.emc.nems.wsd.ui.beans.reports.mpapi.FacilityBeanType.nullSafeGet(FacilityBeanType.java:126)
at org.hibernate.type.CustomType.nullSafeGet(CustomType.java:128)
at org.hibernate.type.AbstractType.hydrate(AbstractType.java:105)
at org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:2114)
at org.hibernate.loader.Loader.loadFromResultSet(Loader.java:1404)
at org.hibernate.loader.Loader.instanceNotYetLoaded(Loader.java:1332)
at org.hibernate.loader.Loader.getRow(Loader.java:1230)
at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:603)
at org.hibernate.loader.Loader.doQuery(Loader.java:724)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259)
at org.hibernate.loader.Loader.doList(Loader.java:2232)
at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2129)
at org.hibernate.loader.Loader.list(Loader.java:2124)
at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:312)
at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1723)
at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:165)
at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:175)
at com.emc.nems.oms.dao.hibernate.util.OMSHibBaseDAO.executeNamedQueryWithoutTransaction(Unknown Source)
at com.emc.nems.wsd.dao.hibernate.reports.mpapi.MpapiReportHibDAO.findMCR020(Unknown Source)
at com.emc.nems.wsd.ui.handler.reports.ReportsHandler.getMPAPIData(Unknown Source)
at com.emc.nems.wsd.ui.servlets.reports.mpapi.MpapiServlet.executeReport(XXXServlet.java:1009)
at com.emc.nems.wsd.ui.servlets.reports.mpapi.MpapiServlet.generateAuditFile(XXXServlet.java:318)
at com.emc.nems.wsd.ui.servlets.reports.mpapi.MpapiServlet.execute(XXXServlet.java:273)
at com.emc.nems.wsd.ui.servlets.reports.mpapi.MpapiServlet.doGet(XXXServlet.java:207)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3731)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3695)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2285)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2184)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1459)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Regards,
Abhishek

Creating my Oracle connection works fine ... code as follows:
Context ctxt = getInitialContext();
DataSource dataSource = (DataSource) ctxt.lookup(poolName);
Connection conn = dataSource.getConnection();
OracleConnection oracleConn = (OracleConnection)((WLConnection)conn).getVendorConnection();
I also have reviewed documentation:
http://e-docs.bea.com/wls/docs81/jdbc/thirdparty.html. In section 'Using OracleStruct Extension Methods' it highlights that
java.sql.Struct struct =(weblogic.jdbc.vendor.oracle.OracleStruct)(rs.getObject(2));
None of the documentation actually mentions oracle.sql.STRUCT. For Weblogic to truely provide support for Oracle it needs an easy way of converting to this data type. At present I cannot interact with Oracle APIs until I can create an oracle.sql.STRUCT.

Weblogic 8.1/Oracle 9 Writing and Reading Clob

I’m trying to write and read a clob to a database table. The database table has
an Id field (int) and a Content field (clob).
My environment consists of Weblogic 8.1, and Oracle 9. Is there a way to get a
handle to a Weblogic connection to Oracle and then write and read clobs?
Any help would be greatly appreciated!
Thanks,
Mike

Problem 1. US7ASCII and Linux - Status Resolved.
The issue with the BEA 817 JDBC driver not connecting to the US7ASCII database tuned out to be that it had not deployed the connection pool correctly from the weblogic admin console... or that it was reported as being deployed when in fact it was not. After re-deploying the connection pool and restarting the server we were able to connect.
The patch was for character sets was not needed.
Problem 2. Oracle Stored Proc error.
The problem with the stored procedures tunred out to be with ref cursors. A patch in sp3, and a change to the way we called the stored proc allowed us to fix the problem.
The problem is reproduced when connecting to an Oracle 8.1.7 server.
It was introduced in the Connect JDBC driver build 3.0.0007. According
to the jdbcread.me file which comes with the 3.0.0007 build we
deprecated the refCursorSupport connection property. This could be
related to the driver not being able to execute a stored procedure
containing ref cursors.
Resolution
Driver was fixed in the Connect JDBC 3.1 Oracle driver version 3.1.0008
The trick was to use
"{call PROC(?,?)}"
instead of
"BEGIN PROC(?, ?);
END;"
Here is a very useful link on the matter:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=b860627b.0405130528.4db317a0%40posting.google.com&rnum=1&prev=/groups%3Fq%3D%255BBEA%255D%255BOracle%2BJDBC%2BDriver%255DInvalid%2Bparameter%2Bbinding%26hl%3Den%26lr%3D%26ie%3DUTF-8%26selm%3Db860 27b.0405130528.4db317a0%2540posting.google.com%26rnum%3D1
The bea type 4 is an oem from DataDirect
http://knowledgebase2.datadirect.com/kbase.nsf/26536a530e20a22b85256e550079afc2/b3be8f8fcb7c30c285256c9f006f8645?OpenDocument&Highlight=0,oracle

Where did weblogic.jdbc.vendor.oracle.OracleThinBlob go?

I just upgraded from 8.1sp4 to 10.1 and the problem I am facing is that the import
import weblogic.jdbc.vendor.oracle.OracleThinBlob;
is no longer valid. I cannot find it even to import. What am I missing??:|
-Joe

Hi
You will find the 'weblogic.jdbc.vendor.oracle.OracleThinBlob' located in the 'com.bea.core.datasource_1.0.0.0.jar'. You will find this jar in the modules directory, in the top level of your WebLogic 10 installation
e.g. for me, it is located in:
C:\wls10\modules\com.bea.core.datasource_1.0.0.0.jar
Vimala-

Comparison of Weblogic Multipools VS. Oracle OCI TAF?

My group is thinking of going with Weblogic's Multipools as opposed to
using Oracle's TAF for failover support.
Has anyone done any benchmarking on the two - or does anyone know of
the pros and cons of going with either solution?
Any first hand feedback on either solution would be extremely helpful,
as would recommendations.
Our setup is:
Linux, oracle 9i and weblogic 7.0
thanks,
- Ryan

Hi Joe,
thanks for the reply - the code change helped a little. It's returning
a bit faster than it was before. However, I'm still experiencing
problems with the Multipool functionality.
After experimenting a little, I have more information on the problem
definition.
I have 2 DB Connection Pools, both set up for one multipool (set up
for HighAvailability).
I can see both pools getting populated (max of 10) at the server
startup.
DB 'getConnection' requests are being created without any problems on
the first connection pool.
As an experiment, I decided to test the health of the connection pools
frequently (every time a connection is requested). The code grabs a
connection and releases it immediately.
This is the code I wrote to do that:
>>>>>>>>>>>>>>
     try{
     conn1 = d.connect("jdbc:weblogic:pool:RConnPool1", null);
     }catch(Exception e)
     debug("Conn1 threw exception " + e.getMessage());
     finally
     try {conn1.close(); } catch (Exception e) { debug("Conn1.Close
E " + e.getMessage());}
     try{
     conn2 = d.connect("jdbc:weblogic:pool:RConnPool2", null);
     }catch(Exception e)
     debug("Conn2 threw exception " + e.getMessage());
     finally
     try {conn2.close(); } catch (Exception e) { debug("Conn2.Close
E " + e.getMessage());}
>>>>>>>>>>>>>>
That code worked inefinitely (I sent about 20-30 requests through
without problems). The actual connection being used was requestd from
the multipool right after that section of code.
>>>>>>>>>>>>>>
     conn = d.connect("jdbc:weblogic:pool:RMultiPool", null);
     notRetrieved = false;
>>>>>>>>>>>>>>
So, when I shut down one the server for ConnPool1 (through the
console), I expected to have the first try-catch to generate an
exception and the second one to continue to function healthily. I also
expected the multipool to switch over to the second pool.
On the first few requests after the db shutdown, I do get the
exception from the first Connpool1 and a healthy message from
Connpool2. However, the multipool returns exceptions for ConnPool1,
but doesn't return connections from ConnPool2 (it just throws an
exception), and healthy message from ConnPool2 stops after 10 tries,
and then I get this message:
"Error in getConnection Pool connect failed:
weblogic.common.ResourceException:
RMultiPool(RConnPool2): no connections available"
It seems that the multipool is grabbing connections from the backup
connection pool and not releasing them. I thought it was me who was
getting the connection and not releasing it, but all connection
objects I have access to appear accounted for.
I tried to confirm this by removing the multipool 'getConnection'
request (instead retrieving the connection from the second connection
pool explicity after I do the health check). With the multipool code
removed, ConnPool2 never runs out of connections.
So finally, I've implemented this bit of code:
>>>>>>>>>>>>>>
     try{
     conn1 = d.connect("jdbc:weblogic:pool:RConnPool1", null);
     notRetrieved = false;
     conn = conn1;
     }catch(Exception e)
          debug("Conn1 threw exception - FAILING OVER" + e.getMessage());
          try{
          conn2 = d.connect("jdbc:weblogic:pool:RConnPool2", null);
          notRetrieved = false;
          conn = conn2;
          }catch(Exception eX)
          debug("Conn2 threw exception - TOTAL DB FAILURE" +
eX.getMessage());
>>>>>>>>>>>>>>
And that code seems to provide failover support.. At least at the
level we need for now.
We would really rather use MultiPools - they're probably better
implemented than what I wrote above, more flexible and more of a
standard - but we just can't figure out what is preventing the
multipool from returning a good connection right away.
No. Refresh is separate. If you have testConnsOnReserve, you don't need
refresh. Set it to 99999999 to effectively turn it off and save resources.This has been changed - thanks.
I wish. However, if you get the failover URL into the pool definition,
the first pool should benefit from the oracle driver failing over internally.
If you disable a pool, using the admin command or the console, then a
multipool will quickly pass over it to the next, so if/when you know the
primary DBMS is down, you can save a lot of time for connectors, if you
disable it's pool, and re-enable it when the DBMS is back.Could you explain the paragraph above? What do you mean by the
failover URL? Do you mean I'd have to disable the connection pool
manually if the database fails? (I'm sure I'm interpreting that
incorrectly) How else can you disable and re-enable a pool
programatically and in a timely manner? Wasn't that the purpose of the
MultiPool?
Thanks,
- Ryan

WebLogic 9.2: Oracle: Can longer connect with a Good Data Source

Hi;
I have WebLogic 9.2 set up on my computer as a development tool. Yesterday I was able to connect to the test database on our test server with the JNDI/Database resource "abc" just fine.
For some reason, it simply stopped working this morning.
I got this error message when trying to connect with the webapp I use:
*+<Jul 28, 2011 4:48:14 PM EDT> <Notice> <Stdout> <000000> <Exception in getPersonIdByEmail(String emailAddress) - statementDB14>+*
+java.sql.SQLException: Cannot obtain connection: driverURL = jdbc:weblogic:pool:nsd, props = {EmulateTwoPhaseCommit=false, connectionPoolID=abc, jdbcTxDataSourcourceName=abc}.+*
Nested Exception: java.lang.RuntimeException: Failed to Generate Wrapper Class*
at weblogic.utils.wrapper.WrapperFactory.createWrapper(WrapperFactory.java:213)
at weblogic.jdbc.wrapper.JDBCWrapperFactory.getWrapper(JDBCWrapperFactory.java:173)
at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:247)
at weblogic.jdbc.pool.Driver.connect(Driver.java:164)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:647)
at weblogic.jdbc.jts.Driver.connect(Driver.java:137)
I got this error message when using a Test JSP I have for doing a simple database connection using that Database Resource ( "abc")
*+<Jul 28, 2011 4:52:06 PM EDT> <Error> <HTTP> <BEA-101020> <[weblogic.servlet.internal.WebAppServletContext@507c6d - appName: 'mainWebApp', name: 'mainWebApp', context-path: ''] Servlet failed with Exception+*
java.lang.NullPointerException*
at jsp_servlet._test.__testjndiweblogic._jspService(__testjndiweblogic.java:145)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
Truncated. see log file for complete stacktrace
Any ideas on how I can fix whatever is wrong?
Thanks in advance
Edited by: 872921 on Jul 28, 2011 2:14 PM

Hi Joe;
I appreciate you taking time to answer my question.
By client do you mean my JRE? I one JRE set in my JAVA_HOME, and two in the weblogic install. How can I tell which is WebLogic using? So, you are basically saying make sure my Oracle JDBC drivers wherever they are in WebLogic should match what I have in my JRE?
I'll give that a shot when I get into work tomorrow.
I am puzzled because it has been working fine for weeks and I haven't changed anything.

Error while using TXDataSource with Weblogic 6.1 & Oracle 8.1.6

Hi,
I am using Weblogic 6.1 and Oracle 8.1.6.
I have configured JDBC XA Connection Pool with Oracle thin driver. These are my settings...
Connection Pool:
Name - myXAPool
URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource:
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
I get the following error when I try to lookup the datasource. I am not sure where the problem is as I have configured Connection Pool and TXDataSource as mentioned in the documentation.
java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start() failed on resource 'myXAPool' Unexpected error during start for XAResource 'myXAPool': null
It would be really great if you can help me out.
Thanks in Advance,
Sudhir.

Hi Sudhir,
If you do not know if upgrade or not, have a look here :
http://e-docs.bea.com/wls/docs61/notes/bugfixes2.html
Note that at the end of June SP3 will be released...
Sergi
"Sudhir Babu" <[email protected]> wrote:
>
Hi Sergi,
Thanks a lot for the class file, I figured out what the problem was. Actually
the
database version I was working with was 8.0.6.0. The Oracle driver doesn't
work with
this but the JDriver worked. This is the output of running CheckDriver..
DatabaseProductName : Oracle
DatabaseProductVersion : Oracle8 Enterprise Edition Release 8.0.6.0.0 -
Production
With the Partitioning and Objects options
PL/SQL Release 8.0.6.0.0 - Production
DriverName : Oracle JDBC driver
DriverVersion : 8.1.7.1.0
Then I tried on using the Oracle Driver on another instance which has the
version
8.1.7.1.0 and it worked. The JDriver and Oracle driver both work with this
database.
The output of CheckDriver for this Oracle instance is..
DatabaseProductName : Oracle
DatabaseProductVersion : Oracle8i Enterprise Edition Release 8.1.7.1.0 -
Production
With the Partitioning option
JServer Release 8.1.7.1.0 - Production
DriverName : Oracle JDBC driver
DriverVersion : 8.1.7.0.0
By the way I am working on WLS 6.1 SP1. What is the advantage of SP2 ? Should
I upgrade
Thanks once again,
Sudhir.
"Sergi Vaz" <[email protected]> wrote:
Hi Sudhir ,
JDriver works well, you can work with it.
Just for curiosity, can you run the class I attached using the "exact"classpath
of your WL instance (with Oracle drivers in front of weblogic.jar) ? What
is the
output ?
On which platform are you running your WLSP2 ?
Thanks
Sergi
"Sudhir Babu" <[email protected]> wrote:
Hi Sergi,
I just checked the things you mentioned. The connection pool starts correctly
without
any errors. I also made sure SELECT previlege was granted to DBA_PENDING_TRANSACTIONS.
I do have the JAVA_XA package installed and it has EXECUTE permission
to
PUBLIC.
I actually tried using the Weblogic JDriver (weblogic.jdbc.oci.xa.XADataSource)
and
it works perfect without any issue. The only consideration is that itis
a Type 2
Driver and needs to have the Oracle Client installed. But right now Ido
have it
installed on the same machine.
Do you know any known issues with Weblogic JDriver. Do you think it'sa
good idea
to go with it ?
Thanks,
Sudhir.
"Sergi Vaz" <[email protected]> wrote:
Hi Sudhir,
does your connection pool start correctly ?
Check the setup of your Oracle server too:
1) grant select on DBA_PENDING_TRANSACTIONS table to PUBLIC
2) package JAVA_XA installed (with grant execute to PUBLIC)
Sergi
"Sudhir Babu" <[email protected]> wrote:
Hi Sergi,
Thanks for the response. I downloaded the driver for 8.1.7 from Oraclesite
and put
it in classpath in front of weblogic.jar. I still get the same problem.
Is there
another location where we can download the Oracle driver with the bug
fixed
Regards, Sudhir.
"Sergi Vaz" <[email protected]> wrote:
Hi Sudhir,
I think you are using Oracle JDBC drivers 8.1.6.
They have a bug, they do not accept a foreign XID.
Use 8.1.7 or higher to solve this problem.
Sergi
Sudhir Babu <[email protected]> wrote:
Hi,
I am using Weblogic 6.1 and Oracle 8.1.6.
I have configured JDBC XA Connection Pool with Oracle thin driver.
These
are my settings...
Connection Pool:
Name - myXAPool
URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource:
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
I get the following error when I try to lookup the datasource. I amnot
sure where the problem is as I have configured Connection Pool and
TXDataSource
as mentioned in the documentation.
java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
occured in the transaction branch start() failed on resource 'myXAPool'
Unexpected error during start for XAResource 'myXAPool': null
It would be really great if you can help me out.
Thanks in Advance,
Sudhir.

WebLogic MultiPool Vs Oracle FCF

Similar Messages

Maybe you are looking for