Monday, January 15, 2007

Is Your Java Application FailoverProof (i.e., RAC Aware)?

Developing and Deploying FailoverProof Java/JDBC Applications in RAC environment using Fast Connection Failover, TAF and Runtime Connection Load Balancing.

Why in the world should a Java developer care about failover and what does it mean to be failoverproof?
Well, failure is inevitable however, in mission critical (i.e., web) deployments, all applications including the Java ones must sustain resource manager (i.e., RDBMS) failure, or connection failure, or transaction failure without disrupting the service.

How exactly?
For the sake of simplicity, let's take a JDBC program. Best practices mandate that Java/JDBC programs capture exceptions and deal with these; here is a skeleton of a failoverproof program using Oracle JDBC in RAC environment:
...
try
{
conn = getConnection();
// do some work
} catch (SQLException e) {
handleSQLException(e); }
...
handleSQLException (SQLException e)
{
if (OracleConnectionCacheManager.isFatalConnectionError(e))
ConnRetry = true; // Fatal Connection error detected
}

Capturing SQL exceptons and re-trying to get a connection are all good JDBC programming so the burden is not really at the Java application level (it has to be somewhat portable), rather at the driver or framework level. Up to these (the driver, the OR Mapping framework, servlet engine, Java EE container) to furnish, under the covers, a failoverproof environment.

Do all drivers and Java frameworks are failoverproof?
You wish! The reality is that very few JDBC drivers or Java frameworks furnish true/reliable connection or transaction failover mechanisms.

From database access point of view, what does it take for a JDBC Driver or a Java framework to be failoverproof?
First of all, a JDBC driver or a Java EE ccontainer by itself cannot furnish a complete failoverproof environment, it more importantly requires the resource manager, in this case the RDBMS to be failoverproof as well. In the Oracle RDBMS case, instance/node failover as well as scalability is furnished by the RAC framework.

What is RAC?
An Oracle database is managed by a database instance which is made of a shared memory (a.k.a. SGA)and a set of database server processes. A database is usually accessed and managed by a single instance. However, an Oracle database can also be concurrently accessed and managed by multiple instances up to 64 nodes and beyond; this technology is known as Real Application Clusters (RAC).

How Does RAC Furnish Failover?
Starting with release 10g, RAC generates events that indicate the health or status of each RAC components including SERVICE, SERVICE_MEMBER,DATABASE, INSTANCE, NODE, ASM, and SRV_PRECONNECT.
The possible status are: UP, DOWN, NOT_RESTARTING, PRECONN_UP, PRECON_DOWN, and UNKNOWN.

Example of events can be: "Instance1 UP", "Node2 Down".

RAC furnishes failover by design in the sense that when a service/instance/node fails, a well written application can be redirected to the surviving node/instance provided these furnish the same service and proceed against the same database.

How Does JDBC Leverages RAC Failover?

The Oracle JDBC 10g drivers, more specifically it's connection cache (a.k.a. Implicit Connection Cache) leverages RAC by subscribing to the following events and status (as described in RAC documentation and in chapter 7 of my book):

  • Service Up: The connection pool starts establishing connections in small batches to the newly added service.
  • Instance (of Service) Up: The connection pool gradually releases idle connections associated with existing instances and reallocates these onto the new instance.
  • Instance (of Service) Down: The connections associated with theinstance are aborted and cleaned up, leaving the connection pool with sound and valid connections.
  • Node Down: The connections associated with the instance are aborted and cleaned up, leaving the connection pool with good connections.

But to be reliable, these events must be propagated to interested parties as fast as possible because the timeout mechanisms(tcp_keepalive, tcp_ip_interval, and so on) are unreliable and may take a long (tens of minutes) to indefinite time to be kick-in.
Orale furnishes ONS (Orale Notification Services) and Advanced Queue as publish/subscribe and predictable notification mechanisms which detects and propagates quasi-instantaneously (sub-seconds) those events to components that have subscribed to these mechanisms.

Setting up JDBC for Failover

  1. Set up a multinstance Oracle Database 10g RAC database (see RAC documentation).
  2. Virtualize the database host through a service name (see JDBC URL in chapter 7 of my book).
  3. Configure ONS on each RAC server node (see the RAC Administrator Guide or chapter 7 in my book).
  4. Configure ONS on each client node (10g Release 1) or use simpler remote subscription (10g Release 2). Ensure ons.jar file is in the CLASSPATH then programmatically set the ONS configuration string for remote ONS subscription at the data source level (unfortunately this cannot yet be set through system property): ods.setONSConfiguration("nodes=node1:4200,node2:4200"); The Java virtual machine (JVM) in which the JDBC driver is running must have oracle.ons.oraclehome set to point to ORACLE_HOME -Doracle.ons.oraclehome=
  5. Enable the Connection Cache and Fast Connection Failover through system property: -Doracle.jdbc.FastConnectionFailover = true Alternatively, the Connection Cache and Fast Connection Failover can be enabled programmatically using OracleDataSource properties: ods.setConnectionCachingEnabled(true); ods.setFastConnectionFailoverEnabled(true);

Oracle JDBC: Handling of DOWN events (Under the covers) Upon the notification of Service Down event, a worker thread (one per pool instance) processes the event in two passes:First pass: Connections are marked as down first, to efficiently disable bad connectionsSecond pass: Aborts and removes connections that are marked as downNote: active connections that may be in the middle of a transaction receive a SQLException instantly

Oracle JDBC: Hanlding of UP Events (under the covers)
A Service UP event initiates connections to be load balanced to all active RAC instances Connection creation depends on Listener’s placement of connections. Starting with 10g release 2,load balancing advisory events enabled Runtime Connection Load Balancing (covered in chapter 7 of my book).

Object-relational Mapping frameworks as well as any Java EE containers may either leverage Oracle JDBC (bypassing their own connection pool) or subscribe diretly to RAC events using the ONS APIs and processing these (i.e., handle connection retry). To my knowledge, only Oracle's Java EE containers (OC4J) has integrated Fast Connection Failover and ONS at datasource level.

How does Oracle JDBC Fast Connection Failover (FCF) compares with TAF?
Fast Connection Fail-over and TAF differ from each other in the followingways:

  1. Driver-type dependency: TAF is in fact a OCI failover mechanism exposed to Java through JDBC-OCI. FCF is driver-type independent (i.e., works for both JDBC-Thin and JDBC-OCI).
  2. Application-Level Connection Retries: FCF supports application-level connection retries (i.e., the application may retry the connection or rethrow the exception). TAF on the other hand retries connection transparently at the OCI/Net out of the control ofthe application or Java framework.
  3. Integration with the Connection Cache: FCF is integrated with the Implicit Connection Cache and invalidates failed connections automatically in the cache. TAF on the other hand works on a per-connection basis at the network level; it does not notify the connection cache of failures.
  4. Load Balancing: unlike TAF, FCF and runtime connection load balancing (RCLB) support UP event load-balancing of connections and runtime distribution of work across active RAC instances.
  5. Transaction Management: FCF automatically rolls back in-flight transations; TAF, on the other hand, requires the application to roll back the transaction and send an acknowledgment to TAF to proceed with the failover.
  6. TAF does not protect or fail-over codes that have server-side states such as Java or PL/SQL stored procedures; however, the application can register a callback function that will be called upon failure to reestablish the session states.

// register TAF callback function “cbk”

((OracleConnection) conn).registerTAFCallback(cbk,msg);

Voila, you now have a Java plateform with connection pool failover, on top of which you can code and deploy JDBC applications or Java EE components.

For more details, see chapter 7 of my book: http://db360.blogspot.com/2006/08/oracle-database-programming-using-java_01.html

81 comments:

Anonymous said...

Is it safe to say, that when using the BC4J/ADF Framework? my application must be FailoverProof/RAC Awar?

Kuassi Mensah said...

Hi,

Fast Connection Failover is based on RAC events. ADFBC provides a failover mode, but it does not depend on RAC.

Kuassi

Anonymous said...

Kuassi,

The question I have is what does the application code have to do to use TAF vs FCF? We have in our requirements to our client identified to use TAF, however I am questioning whether TAF is the right way to go or FCF would be a better option. We are in a J2EE environment with an Oracle 10.2.0.2 application server cluster and 10.2.0.2 RAC database behind it. From our management perspective since we are well into development what impact would using FCF have, i.e. additional code to our application or just enabling ONS and setting some system configuration properties within the application servers and or database servers? Any assistance you could provide or direction would be greatly appreciated.

Thanks,
Brad

Kuassi Mensah said...

Hi Brad,

Simply put:

- with TAF, connection failover is transparent (in case of node failure) however, you have to programmatically rollback ongoing transactions (TAF requires an ACK from the application, in order to proceed)

- with FCF, you need to retry getConnection() programmatically in case of node faiure (you might not need to do anything if your JDBC code has already done the right thing - i.e., catch SQL exception and retry), ongoing transactions are automatically rolled back.

From JDBC perspective, we recommend FCF and it's future incarnation as these are driver independent (as you know, TAF is an OCI feature which only works for JDBC-OCI).

Hope this helps, Kuassi

Anonymous said...

Does anyone know if the Spring framework handles this? There is a spring thread at http://forum.springframework.org/showthread.php?t=16931

Cheers
Neil

Anonymous said...

Kuassi,

Our application is not using RAC but using DataGuard as per client requirements. In this case how do we manage the failover when standby databse becomes master? We are using hibernate and c3p0. Please advice.
Thanks
Sri.

Anonymous said...

Kuassi,

I am an oracle DBA implementing 10gR2 RAC. I have implemented TAF in the past but never had a chance to implement FCF so far. But now our requirement is to implement FCF using ONS. I see that our app team will need to use Oracle JDBC drivers in their code so that we can achieve this. What does the app team need to use/do to ensure that our FCF will work? Thanks much in advance.

Don

Kuassi Mensah said...

Don,

Assuming RAC, ONS, and the services have been confugured and working (see Setting up JDBC for Failover in the blog) , the application team needs to do 2 things.
1) enable FCF either programmatically or using system property
(-Doracle.jdbc.FastConnectionFailover = true)
2) catch SQLException and if this is indeed a FataConnectionError then retry getConnection. See the pseudo-code above in the blog.

That's it, Kuassi

Anonymous said...

Hi Kuassi,

We are currently using our own connection pooling mechanism, and would like to continue using this pool. We are also moving to a RAC environment, and need to support RAC in our application.

Is it possible to use the RAC type db connection properties with our existing connection pool. (No FCF, and no Implicit Connection Cache)

If so, what is the behavior of the JDBC driver when getConnection is called and one of the nodes in the RAC are down? Does it return a connection failure?

Kuassi Mensah said...

Hi,

Right now, the subscription to RAC events ( using ONS) is handled by our connection pool, not by the JDBC itself. There is no public API that you can use to subscribe to RAC events and manage these in your custom connection pool but we are looking into furnishing a JDBC API which will allow you to do that, in a near future.

KUassi

Anonymous said...

Kuassi,
First of all it is not clear to me if retrying is mandatory in order to change servers and allow for fail over. If it *is* mandatory, then
I don't see why Oracle's Data Source driver does not automatically retries the connection (i.e. via configuration parameters); given the fact that there is a RAC configured retrying in case of error would seem the most logical thing to do.
Additionally, I am not aware if commonly used frameworks (like Spring) actually retry a connection on failure (do you happen to know this is the case?).
Thanks a lot,
Regards
AB

Kuassi Mensah said...

Hi,

Yes, when a RAC node fails, it is mandatory to get a new connection belonging to surviving nodes; and the only programmatic way is to rety getConnection(). Having said that, if you were using a container that can intersperse the retry then your own code does not have to do it.
A plain data source cannot intersperse the retry. I know that TAF does that at the network layer but TAF has lot of shortages (not counting that is depends on OCI) that makes it not fully general purpose.
We have had interacion with the Spring folks but i don't know if they have achieved the integration with RAC or not.

Regards, Kuassi

Anonymous said...

---------------------------------------------------------------------------------------------------------------------------------

Anonymous said...

I am having a trouble to implement FCF using Oracle OracleDataSource JDBC class in my plain Java application.
But I don't have this problem in my Java web application deployed to WebLogic app server since WebLogic takes of this. The one big difference between my Java and Web app is providing database connection information. In my Java application, to connect a database, I use Oracle OracleDataSource methods such as setServerName(), setUser(), setFastConnectionFailoverEnabled(), etc. However, in my Web application, I use standard DataSource JDBC class and provide the following connection information to WebLogic configuration file:

url tag jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=

(ADDRESS = (PROTOCOL = TCP)(HOST = 192.199.1.144)(PORT = 1521))

(ADDRESS = (PROTOCOL = TCP)(HOST = 192.199.1.145)(PORT = 1521))

(FAILOVER=on)(LOAD_BALANCE=yes))

(CONNECT_DATA=(SERVER=DEDICATED)

(SERVICE_NAME = my.ractest.com)

(FAILOVER_MODE =(TYPE = SELECT)(METHOD = BASIC)(RETRIES = 180)(DELAY = 5))

)

)
As I said before, my Web App works with Oracle RAC but not my plain Java app.

My questions are below:
1. For my java app, do I have to provide the above url to OracleDataSource class to connect database as I did to WebLogic?

2. If yes, how do I pass these information?
I mean which OracleDataSource methods I have to use. I can't find a method that takes the entire url string a single call.

3. Can you take a look at my code snippet and tell what is wrong with my code?
Note: This code works fine in NOT RAC environment.


OracleDataSource conPds = new OracleDataSource();

conPds.setUser( user );
conPds.setPassword( password );
conPds.setDriverType( THIN );
conPds.setPortNumber( port );
conPds.setDatabaseName( databaseName );
conPds.setServerName( serverName );
if ( serviceName != null && serviceName.length() != 0 )
{
conPds.setServiceName( serviceName );
}

Properties cacheProp = new Properties();
cacheProp.setProperty( INITIAL_LIMIT, initConLimit );
ms_initConLimit = initConLimit; // for debugging info
cacheProp.setProperty( MAX_LIMIT_STATEMENTS_LIMIT, "30" );

conPds.setConnectionCachingEnabled( true );
conPds.setFastConnectionFailoverEnabled( true );
conPds.setConnectionCacheProperties( cacheProp );
conPds.setONSConfiguration( "nodes=192.168.1.155:6200,192.168.1.156:6200" ); // hard-coded now
conPds.setConnectionCacheName( CONNECTION_CACHE_NAME );

OracleConnectionCacheManager conCacheMgr = OracleConnectionCacheManager.getConnectionCacheManagerInstance();

conCacheMgr.createCache( CONNECTION_CACHE_NAME, conPds, cacheProp );

I appreciate your help in advance.

Sun

Kuassi Mensah said...

Hi,

The Weblogic data source does on your behalf what your JDBC code needs to do.
Yes, you need to provide the same URL either directly in your Java code or in tnsnames.ora as a service and use the service name in your JDBC URL.

HOpe this helps

Anonymous said...

(法新社倫敦四日電) 英國情色大亨芮孟的成人公司昨天說色情,芮孟a片下載日前部落格去世,享壽八十二歲;成人網站這位身價上億的房地產開情色電影發商,曾經a片在倫敦推出av女優色情一場脫色情衣舞情色表演。


芮孟的財產估計達六億五千萬英色情影片鎊(台幣將近四百億),由日本av於他名a片下事業大多分布部落格在倫敦夜av生活區蘇活區成人電影,因此擁有「蘇活之王」的稱號。sex


他的公司「保羅芮a片孟集團」旗下發行多種情色雜誌情色視訊,包括「Razzle成人影片」、「男性世界」以及「Mayfair」。av女優


成人光碟芮孟a片下載本名av女優a片福瑞成人影片av安東尼.奎恩,父成人影片親為搬運承包商。芮孟十五歲離開學校,矢言要在表演事業留成人網站AV片,起先表成人網站演讀心成人術,後來成為巡迴歌舞avdvd雜耍表演的製作人。
情色電影

許多評論家認為,他把情色表演帶進主流社會,一九五九年主部落格持破天荒的av脫衣舞表演,後來更靠情色著在蘇活區與倫敦西區開發房地成人電影產賺得大筆財富。av


有人形容芮孟是英國的海夫納色情a片,地位等同美國的「花花公子」創辦人海夫納。

Unknown said...

Does two-phase commit (XA) work with Fast Connection Failover?

Kuassi Mensah said...

Yes but you have to use the new connection pool (UCP) it comes with 11.1.0.7.

vuong said...

先物 比較
先物 比較
先物 比較
先物 比較
先物 比較
先物 比較
先物 比較
事業再生
経営計画書
経営改革
経営改善
会社分割
経営コンサルティング
お見合いパーティー 福岡
お見合いパーティー 福岡
お見合いパーティー 福岡
お見合いパーティー 福岡
お見合いパーティー 福岡
お見合いパーティー 福岡
お見合いパーティー 福岡
お見合いパーティー 福岡
お見合いパーティー 福岡
お見合いパーティー 福岡
浮気調査 松戸
浮気調査 船橋
備考調査 追跡調査 東京
不倫調査 離婚調査 東京
浮気調査 素行調査 東京 
ストーカー相談 ストーカー対策 東京
結婚調査 結婚詐欺 東京
信用調査 企業調査 東京
調査料金 東京
身上調査 身元調査 身辺調査 東京
所在調査 東京
夫 妻 浮気 東京

vuong said...

リノベーション
リノベーション
リノベーション
リノベーション
リノベーション
リノベーション
リノベーション
リノベーション
リノベーション
リノベーション
ビジネス英会話
英文 書き方
英語塾
社会人入試
英語 転職
医療脱毛

会社設立 格安
派遣会社
東横 賃貸
田園都市 賃貸
デザイナーズ 賃貸
恵比寿 賃貸
学芸大学 賃貸
目黒 賃貸
中目黒 賃貸
新築 賃貸
ペット可 賃貸
三軒茶屋 賃貸
パチンコ求人
販売管理
債務整理 新宿
過払い 渋谷
液晶 テレビ 32
先物 比較
先物 比較
先物 比較

Hussain said...

Hi Kuassi,

While using FCF, we are continously getting below exception on console. Daemon thread that gravitates connection from one instance to another keeps on getting this exception
(http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq.html)

Exception in thread "Thread-1457" java.lang.NullPointerException
at oracle.jdbc.pool.OracleImplicitConnectionCache.gravitateCache(OracleImplicitConnectionCache.java:3186)
at oracle.jdbc.pool.OracleGravitateConnectionCacheThread.run(OracleGravitateConnectionCacheThread.java:33)
Exception in thread "Thread-2098" java.lang.NullPointerException
at oracle.jdbc.pool.OracleImplicitConnectionCache.gravitateCache(OracleImplicitConnectionCache.java:3186)
at oracle.jdbc.pool.OracleGravitateConnectionCacheThread.run(OracleGravitateConnectionCacheThread.java:33)
Exception in thread "Thread-2965" Exception in thread "Thread-2966" java.lang.NullPointerException
at oracle.jdbc.pool.OracleImplicitConnectionCache.gravitateCache(OracleImplicitConnectionCache.java:3186)
at oracle.jdbc.pool.OracleGravitateConnectionCacheThread.run(OracleGravitateConnectionCacheThread.java:33)
java.lang.NullPointerException
at oracle.jdbc.pool.OracleImplicitConnectionCache.gravitateCache(OracleImplicitConnectionCache.java:3186)
at oracle.jdbc.pool.OracleGravitateConnectionCacheThread.run(OracleGravitateConnectionCacheThread.java:33)


Please can you tell us the reason why this exception keeps on coming.

Thanks,
Hussain

Anonymous said...

I am presently managing a 10.2.0.4 RAC. Since migrating this single instance database to RAC ON Linux, there have been issues on the application side. Part of the error reads:
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'a
lertsManagerImpl' defined in class path resource [application-context-service-core.xml]: Cannot reso
lve reference to bean 'alertsCommonUser' while setting bean property 'commonUser'; nested exception
is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'alertsCom
monUser' defined in class path resource [application-context-service-core.xml]: Invocation of init m
ethod failed; nested exception is org.govgrnds.dao.DAOException: ; nested exception is org.springfra
mework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is jav
a.sql.SQLException: Io exception: Got minus one from a read call

The application used thin client jdbc drivers. We are thinking of setting up ONS for FCF. How is this set up on the database?

Kuassi Mensah said...

I don't know how well the Sping framework works with RAC, Oracle JDBC, and FAN/ONS. I suggest to check their web site.
regardign ONS configuration, this is documented in our JDBC doc @http://www.oracle.com/pls/db112/to_pdf?pathname=java.112/e10589.pdf.

r4 card said...

I am an oracle DBA implementing 10gR2 RAC. I have implemented TAF in the past but never had a chance to implement FCF so far. But now our requirement is to implement FCF using ONS.

vas said...

Hi Kuassi,

I had been trying to use UCP for our up-gradation of in-house connectionPool to make it RAC aware. I'm facing quite a tough time in managing the threads it creates.

We have quite a number of instances and so had to have some 5 pools (Old has 37) of maxPoolSize to 100 (some may have 200).

This is creating insane amount of threads and for every getConnection() it is creating a new thread.

As I could not find any other post related, am posting this question here. Sorry!

Could you just point us to where we are messing up with UCP?

Vas

wedding reception las vegas said...

I am an oracle DBA implementing 10gR2 RAC. I have implemented TAF in the past but never had a chance to implement FCF so far. But now our requirement is to implement FCF using ONS.

lakeside said...

I don't see why Oracle's Data Source driver does not automatically retries the connection (i.e. via configuration parameters); given the fact that there is a RAC configured retrying in case of error would seem the most logical thing to do.Las Vegas Receptions

Civil Engineering said...

They anticipated an upswing in local blogging, and the influx of social media contributors, that would come with a global event.

Construction Safety Coordination said...

In the Oracle RDBMS case, instance/node failover as well as scalability is furnished by the RAC framework.

Construction Safety Coordination said...

Any assistance you could provide or direction would be greatly appreciated.

Inspection of Work said...

A database is usually accessed and managed by a single instance. However, an Oracle database can also be concurrently accessed and managed by multiple instances up to 64 nodes and beyond; this technology is known as Real Application Clusters (RAC).

Inspection of Work said...

Well, failure is inevitable however, in mission critical (i.e., web) deployments, all applications including the Java ones must sustain resource manager (i.e., RDBMS) failure, or connection failure, or transaction failure without disrupting the service.

Inspection of Work said...

Fast Connection Failover is based on RAC events. ADFBC provides a failover mode, but it does not depend on RAC.

Construction Safety Coordination said...

In the Oracle RDBMS case, instance/node failover as well as scalability is furnished by the RAC framework.

las vegas wedding chapels said...

I see that our app team will need to use Oracle JDBC drivers in their code so that we can achieve this. What does the app team need to use/do to ensure that our FCF will work? Thanks much in advance.

sex shop said...

good post

vegas weddings and receptions said...

The connection pool gradually releases idle connections associated with existing instances and reallocates these onto the new instance.

vegas weddings and receptions said...

The reality is that very few JDBC drivers or Java frameworks furnish true/reliable connection or transaction failover mechanisms.

vegas weddings and receptions said...

In this case how do we manage the failover when standby databse becomes master? We are using hibernate and c3p0.

vegas weddings and receptions said...

An Oracle database is managed by a database instance which is made of a shared memory (a.k.a. SGA)and a set of database server processes.

vegas weddings and receptions said...

I don't see why Oracle's Data Source driver does not automatically retries the connection (i.e. via configuration parameters); given the fact that there is a RAC configured retrying in case of error would seem the most logical thing to do.

vegas wedding chapels said...

The reality is that very few JDBC drivers or Java frameworks furnish true/reliable connection or transaction failover mechanisms.

vegas weddings and receptions said...

Failure is inevitable however, in mission critical (i.e., web) deployments, all applications including the Java ones must sustain resource manager (i.e., RDBMS) failure, or connection failure, or transaction failure without disrupting the service.

vegas weddings and receptions said...

From JDBC perspective, we recommend FCF and it's future incarnation as these are driver independent (as you know, TAF is an OCI feature which only works for JDBC-OCI).

vegas weddings and receptions said...

However, an Oracle database can also be concurrently accessed and managed by multiple instances up to 64 nodes and beyond; this technology is known as Real Application Clusters (RAC).

wedding flowers las vegas said...

From JDBC perspective, we recommend FCF and it's future incarnation as these are driver independent (as you know, TAF is an OCI feature which only works for JDBC-OCI).

wedding flowers las vegas said...

Fast Connection Failover is based on RAC events. ADFBC provides a failover mode, but it does not depend on RAC.

Pneumatic Cylinder said...

The connection pool gradually releases idle connections associated with existing instances and reallocates these onto the new instance.

Pneumatic Solenoid Valves said...

However, an Oracle database can also be concurrently accessed and managed by multiple instances up to 64 nodes and beyond; this technology is known as Real Application Clusters

vegas weddings and receptions said...

Starting with 10g release 2,load balancing advisory events enabled Runtime Connection Load Balancing

Pneumatic Filters said...

an Oracle database can also be concurrently accessed and managed by multiple instances up to 64 nodes and beyond; this technology is known as Real Application Clusters (RAC).

las vegas wedding chapels said...

RAC furnishes failover by design in the sense that when a service/instance/node fails, a well written application can be redirected to the surviving node/instance provided these furnish the same service and proceed against the same database.

soil stabilization plant said...

I see that our app team will need to use Oracle JDBC drivers in their code so that we can achieve this. What does the app team need to use/do to ensure that our FCF will work? Thanks much in advance.

bitumen sprayer truck said...

Right now, the subscription to RAC events ( using ONS) is handled by our connection pool, not by the JDBC itself.

mixing concrete said...

A plain data source cannot intersperse the retry. I know that TAF does that at the network layer but TAF has lot of shortages (not counting that is depends on OCI) that makes it not fully general purpose.

Concrete batch mix plant said...

In this case how do we manage the fail over when standby database becomes master? We are using hibernate and c3p0. Please advice.

Mobile Concrete Batching Plant said...

There is no public API that you can use to subscribe to RAC events and manage these in your custom connection pool but we are looking into furnishing a JDBC API which will allow you to do that, in a near future.

Wet mix macadam plant said...

The one big difference between my Java and Web app is providing database connection information. In my Java application, to connect a database, I use Oracle OracleDataSource methods such as setServerName(), setUser(), setFastConnectionFailoverEnabled(), etc.

Air Filter Regulator Lubricator said...

In this case how do we manage the fail over when standby database becomes master? We are using hibernate and c3p0. Please advice.

Compact Cylinder said...

I see that our app team will need to use Oracle JDBC drivers in their code so that we can achieve this. What does the app team need to use/do to ensure that our FCF will work? Thanks much in advance.

Data Entry India said...

I see that our app team will need to use Oracle JDBC drivers in their code so that we can achieve this.

Data Entry Outsourcing said...

what is the behavior of the JDBC driver when getConnection is called and one of the nodes in the RAC are down? Does it return a connection failure?

Outsourcing Transcription Services said...

I have implemented TAF in the past but never had a chance to implement FCF so far. But now our requirement is to implement FCF using ONS.

bitumen sprayer said...

What does the app team need to use/do to ensure that our FCF will work? Thanks much in advance.

concrete batch plant said...

This is creating insane amount of threads and for every getConnection() it is creating a new thread.

portable batch plant said...

Yes, you need to provide the same URL either directly in your Java code or in tnsnames.ora as a service and use the service name in your JDBC URL.

vegas weddings and receptions said...

From JDBC perspective, we recommend FCF and it's future incarnation as these are driver independent (as you know, TAF is an OCI feature which only works for JDBC-OCI).

vegas wedding chapels said...


From JDBC perspective, we recommend FCF and it's future incarnation as these are driver independent (as you know, TAF is an OCI feature which only works for JDBC-OCI

vegas weddings and receptions said...

A database is usually accessed and managed by a single instance. However, an Oracle database can also be concurrently accessed and managed by multiple instances up to 64 nodes and beyond; this technology is known as Real Application Clusters (RAC).

vegas weddings and receptions said...

TAF does not protect or fail-over codes that have server-side states such as Java or PL/SQL stored procedures; however, the application can register a callback function that will be called upon failure to reestablish the session states.

data entry india said...

TAF does not protect or fail-over codes that have server-side states such as Java or PL/SQL stored procedures; however, the application can register a callback function that will be called upon failure to reestablish the session states.

bitumen sprayer said...

I have implemented TAF in the past but never had a chance to implement FCF so far. But now our requirement is to implement FCF using ONS.

concrete batch plant said...

They anticipated an upswing in local blogging, and the influx of social media contributors, that would come with a global event.

portable batch plant said...

What does the app team need to use/do to ensure that our FCF will work? Thanks much in advance.

outsourcing web research said...

A database is usually accessed and managed by a single instance.

concrete batch plant said...

However, an Oracle database can also be concurrently accessed and managed by multiple instances up to 64 nodes and beyond; this technology is known as Real Application Clusters (RAC).

Data Entry Outsourcing said...

However, an Oracle database can also be concurrently accessed and managed by multiple instances up to 64 nodes and beyond; this technology is known as Real Application Clusters (RAC).

Data Entry Outsourcing said...

RAC furnishes failover by design in the sense that when a service/instance/node fails, a well written application can be redirected to the surviving node/instance provided these furnish the same service and proceed against the same database.

Data Entry Outsourcing said...

The reality is that very few JDBC drivers or Java frameworks furnish true/reliable connection or transaction failover mechanisms.

Unknown said...

Thanks for all your information, Website is very nice and informative content.
Signature:
The place to play all unblocked games 77 online. Here you can find every blocked games such as: unblockedgames , unblocked games happy , unblocked games 77 , Garry's Mod Free

Unknown said...

Jual obat herbal de nature asli untuk berbagai penyakit kelamin dan sebagainya
Obat Wasir Herbal
Obat Wasir Herbal Mujarab
Obat Wasir Herbal Ampuh
Obat Wasir Herbal Pada Pria
Obat Wasir Herbal Di Apotik
Cara Mengobati Wasir Stadium 4
Cara Mengobati Wasir Stadium 4 Tanpa Operasi
Cara Mengatasi Wasir Stadium 4
Cara Penyembuhan Wasir Stadium 4
Cara Mengobati Ambeien Stadium 4 Secara Alami
Cara Pengobatan Wasir Stadium 4
Cara Pengobatan Ambeien Stadium 4
Cara Mengobati Wasir Stadium 3 Dan 4
Cara Mengobati Wasir Stadium 3
Cara Mengobati Wasir Stadium 3 Secara Alami
Obat Wasir Herbal Apotik
Obat Wasir Herbal Untuk Ibu Hamil
Obat Wasir Herbal Terdaftar Bpom
Obat Wasir Herbal Untuk Ibu Menyusui
Obat Wasir Herbal Bandung
Cara Mengobati Wasir Stadium 3 Dan 4
Cara Mengatasi Wasir Stadium 3
Cara Mengobati Ambeien Stadium 3 Tanpa Operasi
Cara Menyembuhkan Wasir Stadium 3
Cara Mengatasi Ambeien Stadium 3
Cara Alami Mengobati Wasir Stadium 3
Cara Mengobati Ambeien Stadium 3 Secara Alami
Obat Wasir Herbal Manjur
Obat Wasir Herbal Semarang
Obat Wasir Herbalife
Obat Wasir Herbal Jogja
Obat Herbal Wasir Berdarah
Obat Herbal Wasir Dalam
Obat Herbal Wasir Akut
Obat Herbal Wasir Stadium 4
Obat Herbal Wasir Terpercaya
Obat Herbal Wasir Stadium 3
Obat Herbal Wasir Internal
Obat Wasir Herbal Alami