Connection failover and transaction failover

Connection failover and transaction failover
I need to know more about a behavior in a RAC cluster. When a node goes down that is executing one of my transaction through JDBC , does the connection and transaction failover to a new node without me needing to restart tran or reconnect ?
Please provide some insight
Thanks

Transactions are NOT automatically rolled back. The application must do this otherwise the session will get disconnected.
If you code TAF, all sessions will failover to the backup connection. You can specify that select statements are automatically re-executed after the failover. Insert/update/delete transactions must be explicitly rolled back and resubmitted by the application.
IF you are using an ORacle Connection pool, the connection pool will automatically cleanup connections to the failed instance, abort inflight transactions. The application will either retry or it will propagate the error to the end user.
See the whitepaper on the OTN RAC page (otn.oracle.com/rac) Workload Management with Oracle RAC for more information.

Similar Messages

PO for LAN failover and stateful failover link?

Hi.. We have 2 x ASA 5520s running ver 9.0. We plan to aggregate the 2 interfaces used for LAN failover and stateful failover into a lacp PO. So both the ASAs are connected to each other directly using these 2 interfaces and then we logically make it a one PO. We then assign the PO intface an ip. Is this supported?

You can use any unused interface (physical, redundant, or EtherChannel) as the failover link. (Source)
That said, It would be an uncommon implementation. I almost always see them on separate physical interfaces.

Using oracle's connection pools and transactional context

Hi!
I have an implementations of existing interfaces ( let's call this layer as
data access layer) which abstracts the connection and transactional session
from the calling application. This implementaion makes use of Oracles JVM
inside the oracle database (8.1.7) to create and maintain the connection
pools and the transactional session (transactional context). I would like
to create differenent implementation, if the calling application is a
session bean running inside the weblogic application server. is there way I
can still use the connection pools and transactinal context that I got from
the oralce if the calling application is a session bean running inside the
weblogic app.. server?
do I have to change any configuration settings in weblogic?. there might
be two scenarios..
the data access layer (the classes which deal with the connection pools and
transactions) might be running inside the oracle's JVM..
the data access layer might be running inside weblogic application server...
thanks...
Srinivas

Certainly this from SPAM. Now from anothe user :). Note sure whether I should mark you as you as SPAM as you're posting questions which are available in stackoverflow
http://stackoverflow.com/questions/26531161/biztalk-and-odp-net-connection-pools-and-connection-strings
Details provided in the other forum should provide you the answer.
I don’t want to duplicate this thread just for the sake of giving reply.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Problem with transacted JMS connection factory and transaction timeouts

          We encountered an interesting problem using transacted JMS connection factories.
          An EJB starts a container managed transaction and tries to validate a credit card
          before creating some information to a database for the user, in case of success
          an SMS is sent to the user via the transacted JMS queue. If the credit card authentications
          duration is about the same as the transactions timeout (in this case the default
          30 seconds) sometimes the database inserts is committed but the JMS insert is
          rollbacked. How can this be?
          If the authorization duration is much longer than 30 seconds everything works
          fine (both database and JMS inserts rollbacked), the same is true if a rollback
          is insured by calling EJBContext.setRollbackOnly(). The problem thus occurs only
          if the duration is approximately the same as the transaction timeout, it appears
          that the database insert is not timeouted but the JMS insert is. How can this
          be if they are both participating in the same transaction.
          The JMSConnectionFactory used is a Connection factory with XA-enabled. The result
          is the same also with the default "javax.jms.QueueConnectionFactory" and if we
          configure our own factory with user transactions enabled.
          Any help appreciated!


Tomas Granö wrote:
          > We encountered an interesting problem using transacted JMS connection factories.
          > An EJB starts a container managed transaction and tries to validate a credit card
          > before creating some information to a database for the user, in case of success
          > an SMS is sent to the user via the transacted JMS queue. If the credit card authentications
          > duration is about the same as the transactions timeout (in this case the default
          > 30 seconds) sometimes the database inserts is committed but the JMS insert is
          > rollbacked. How can this be?
          It should not be.
          >
          > If the authorization duration is much longer than 30 seconds everything works
          > fine (both database and JMS inserts rollbacked), the same is true if a rollback
          > is insured by calling EJBContext.setRollbackOnly(). The problem thus occurs only
          > if the duration is approximately the same as the transaction timeout, it appears
          > that the database insert is not timeouted but the JMS insert is. How can this
          > be if they are both participating in the same transaction.
          >
          > The JMSConnectionFactory used is a Connection factory with XA-enabled. The result
          > is the same also with the default "javax.jms.QueueConnectionFactory" and if we
          > configure our own factory with user transactions enabled.
          >
          > Any help appreciated!
          Make sure that your session is not "transacted". In other words,
          the first parameter to createSession() must be false. There is an
          unfortunate name re-use here. If a session is "transacted", it
          maintains an independent "inner transaction" independent of the
          outer transaction. From the above description, it seems unlikely
          that your application has this wrong, as you say that
          "setRollbackOnly" works - but please check anyway.
          Make sure that you are using a true XA capable driver and database
          (XA "emulation" may not suffice)
          Beyond the above, I do not see what can be going wrong. You
          may want to try posting to the transactions and jdbc newsgroups. Note
          that JMS is appears to be exhibiting the correct behavior, but the
          JDBC operation is not. The JDBC operation appears to have
          its timeout independent of the transaction monitor's timeout.
          Tom

Connection Pool and Database Sessions

Hi,
Is there any way to use the connection pool or Datasource while connecting to database?If I am using a stateless sesssion bean and using a Data Access layer which just creates a database session to write the persistence toplink objects how I can make use of application server connection pool?
Thanks,
Vinod

Hi,
Is there any way to use the connection pool or Datasource while connecting to database?If I am using a stateless sesssion bean and using a Data Access layer which just creates a database session to write the persistence toplink objects how I can make use of application server connection pool?Hi Vinod,
Yes, TopLink allows you to use the app server's connection pooling and transaction services. Chapter 2 of the Oracle9iAS TopLink Foundation Library Guide provides details as do the TopLink examples. The easiest way to set this up is by using the sessions.xml file. The sample XML below is from the file <toplink903>\examples\ias\examples\ejb\sessionbean\sessions.xml. Here we are adding the datasource defined in OC4J and specifying that we are using the OC4J transaction controller also.
<login>
<user-name>sa</user-name>
<password></password>
<datasource>java:comp/env/jdbc/ejbJTSDataSource</datasource>
<uses-external-transaction-controller>true</uses-external-transaction-controller>
<uses-external-connection-pool>true</uses-external-connection-pool>
</login>
<external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
When using this approach you need to change your TopLink code slightly in the EJB methods:
a. Acquire the ACTIVE unit of work from the server
session (again, see the EmployeeSessionEJB code
example) with something like:
UnitOfWork uow = clientSession.getActiveUnitOfWork();
b. Calls to uow.commit() can be ommitted or commented out
because the EJB will handle this. Note that of course
the methods you create in the EJB that are using this
approach must have TX Required (default).
Hope this helps.
Pete

Listener EA2: database connection pool and connection revalidation

Hi all,
As one can expect from early adopter release there could be some bugs but I can't find any references in forum to my situation:
* My 11g XE database and listener are starting as windows services when server boots operating system (Windows Server 2003 R2).
* I configured my web server (unsupported Jetty 9.0.0.M1) to start as windows service when operating system starts.
* Apex Listener 2.0.0.268.17.05 configured to connect with XE using JDBC thin driver with default settings (initial pool size 3, max statements 10, min connections 1, max connections 10, inactivity timeout 1800, abandoned connection timeout 900)
* Because web server starts a bit faster than Oracle database when apex connects first time it gets "ORA-12528, TNS:listener: all appropriate instances are blocking new connections" (could be that database still starting but already registered service with listener)
* From listener.log file I can see that all further connections made from Apex listener succeeds
* When I try to open any apex page with browser I am getting 404 error and apex listener logs error (*time is 2 days after system startup*):
2012-11-30 3:56:02 PM oracle.dbtools.common.config.db.DatabaseConfig badConfiguration
SEVERE: The pool named: apex is not correctly configured, error: Listener refused the connection with the following error:
ORA-12528, TNS:listener: all appropriate instances are blocking new connections
ConnectionPoolException [error=BAD_CONFIGURATION]
     at oracle.dbtools.common.jdbc.ConnectionPoolException.badConfiguration(ConnectionPoolException.java:62)
     at oracle.dbtools.common.config.db.DatabaseConfig.badConfiguration(DatabaseConfig.java:146)
     at oracle.dbtools.common.config.db.DatabaseConfig.createPool(DatabaseConfig.java:168)
     at oracle.dbtools.common.config.db.DatabaseConfig.getConnection(DatabaseConfig.java:68)
     at oracle.dbtools.common.jdbc.ora.OraPrincipal.connection(OraPrincipal.java:25)
     at oracle.dbtools.apex.ModApexContext.getConnection(ModApexContext.java:320)
     at oracle.dbtools.apex.Procedure.getProcedure(Procedure.java:166)
     at oracle.dbtools.apex.OWA.validateProcedure(OWA.java:384)
     at oracle.dbtools.apex.security.Security.isValidRequest(Security.java:171)
     at oracle.dbtools.apex.ModApex.validateRequest(ModApex.java:233)
     at oracle.dbtools.apex.ModApex.doGet(ModApex.java:79)
     at oracle.dbtools.apex.ModApex.service(ModApex.java:263)
     at oracle.dbtools.rt.web.HttpEndpointBase.modApex(HttpEndpointBase.java:288)
     at oracle.dbtools.rt.web.HttpEndpointBase.service(HttpEndpointBase.java:127)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
     at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:665)
     <... Jetty web server stack ...>
     at java.lang.Thread.run(Unknown Source)
2012-11-30 3:56:02 PM oracle.dbtools.rt.web.HttpEndpointBase modApex
* Oracle listener log for same time (no errors here):
30-NOV-2012 15:56:01 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=SYSTEM))(SERVICE_NAME=xe)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=SYSTEM))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1078)) * establish * xe * 0
30-NOV-2012 15:56:01 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=SYSTEM))(SERVICE_NAME=xe)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=SYSTEM))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1079)) * establish * xe * 0
30-NOV-2012 15:56:01 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=SYSTEM))(SERVICE_NAME=xe)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=SYSTEM))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1080)) * establish * xe * 0
30-NOV-2012 15:56:01 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=SYSTEM))(SERVICE_NAME=xe)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=SYSTEM))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1081)) * establish * xe * 0
* For some reason apex listener keeps first connection status and won't try to establish new connection if first attempt finished with ORA-12528
* The same scenario is valid when at time of web server start oracle database/listener is not available - even if database and listener starts and apex successfully establishes further connections all apex pages gets 404 error
* If I restart web server windows service (while oracle db and listener still running) browser opens apex pages without errors and apex listener does not log any errors
* I know that I can avoid this error delaying start of web server windows service but it would be nice to have production release 2.x without such bugs

Hi,
Is there any way to use the connection pool or Datasource while connecting to database?If I am using a stateless sesssion bean and using a Data Access layer which just creates a database session to write the persistence toplink objects how I can make use of application server connection pool?Hi Vinod,
Yes, TopLink allows you to use the app server's connection pooling and transaction services. Chapter 2 of the Oracle9iAS TopLink Foundation Library Guide provides details as do the TopLink examples. The easiest way to set this up is by using the sessions.xml file. The sample XML below is from the file <toplink903>\examples\ias\examples\ejb\sessionbean\sessions.xml. Here we are adding the datasource defined in OC4J and specifying that we are using the OC4J transaction controller also.
<login>
<user-name>sa</user-name>
<password></password>
<datasource>java:comp/env/jdbc/ejbJTSDataSource</datasource>
<uses-external-transaction-controller>true</uses-external-transaction-controller>
<uses-external-connection-pool>true</uses-external-connection-pool>
</login>
<external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
When using this approach you need to change your TopLink code slightly in the EJB methods:
a. Acquire the ACTIVE unit of work from the server
session (again, see the EmployeeSessionEJB code
example) with something like:
UnitOfWork uow = clientSession.getActiveUnitOfWork();
b. Calls to uow.commit() can be ommitted or commented out
because the EJB will handle this. Note that of course
the methods you create in the EJB that are using this
approach must have TX Required (default).
Hope this helps.
Pete

Oracle Application server connection pool and database links

I am using Oracle application server 10g with connection pools, the db used by the application connects to another oracle db using a database link. My question is when the application starts it creates 10 connections, does it also create x amount of database links as well?

Hi,
Is there any way to use the connection pool or Datasource while connecting to database?If I am using a stateless sesssion bean and using a Data Access layer which just creates a database session to write the persistence toplink objects how I can make use of application server connection pool?Hi Vinod,
Yes, TopLink allows you to use the app server's connection pooling and transaction services. Chapter 2 of the Oracle9iAS TopLink Foundation Library Guide provides details as do the TopLink examples. The easiest way to set this up is by using the sessions.xml file. The sample XML below is from the file <toplink903>\examples\ias\examples\ejb\sessionbean\sessions.xml. Here we are adding the datasource defined in OC4J and specifying that we are using the OC4J transaction controller also.
<login>
<user-name>sa</user-name>
<password></password>
<datasource>java:comp/env/jdbc/ejbJTSDataSource</datasource>
<uses-external-transaction-controller>true</uses-external-transaction-controller>
<uses-external-connection-pool>true</uses-external-connection-pool>
</login>
<external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
When using this approach you need to change your TopLink code slightly in the EJB methods:
a. Acquire the ACTIVE unit of work from the server
session (again, see the EmployeeSessionEJB code
example) with something like:
UnitOfWork uow = clientSession.getActiveUnitOfWork();
b. Calls to uow.commit() can be ommitted or commented out
because the EJB will handle this. Note that of course
the methods you create in the EJB that are using this
approach must have TX Required (default).
Hope this helps.
Pete

Questions on Client Failver and Fast Failover

've few questions regarding Client Failover and Fast Faiolver of Oracle Database HA. Before I ask those questions I would like to explain my environment. Below are the details.
- We have two physical locations called 'ABC' and 'PQR'
- ABC is the primary site.
- PQR is the standby site.
- In ABC, we have Oracle RAC database (11.2.0.2) with two nodes.
- In PQR, we have a single server standalone database (11.2.0.2) with ASM. This is not a RAC.
- Data Guard has been configured between ABC and PQR and it is working as expected.
- Please note that we have a licence for Active Data Guard.
- We have Oracle Identity Management products at both ABC and PQR and they are going to use RAC database as a primary database which is in ABC.
- We did not configure Data Guard broker yet.
We want to achieve below goals:
Goal 1:
Whenever RAC primary goes down completely, standby database should become primary database AUTOMATICALLY and it should allow read/write operation.
I guess this is called 'Fast Failover'. Please let me know if I am wrong.
Questions :
- To make this happen, Do I need to configure Data Guard Broker so that standy database becomes primary when RAC goes down completely with planned or unplanned outage.
- Let's say RAC goes down completely, how long does Data Guard broker take to make standby db as Primary.
- What about the client/application who already connected to RAC.
- Let's standby DB has become as primary and after sometime if RAC comes back , Does data guard automatically changes the role of RAC to primary ?
Goal 2:
As I explained above, all Oracle IDM products and applications speak to RAC database they only know about RAC database which is primary.They are not aware of standby database.
- Whenever a client session is in progress with RAC primary database, if RAC goes down completely , we would like to expect client session should get transferred standby datbase without loosing session information . However before this happens, standby database should become primary becuase client session may perform write operations.
- Whenever a client is trying to connect to RAC prmary and assume RAC is completely down, we would like to expect client connections should get transferred to standby database.
However before this happens, standby database should become primary becuase client session may perform write operations.
As per my knowledge, above scenarios are called 'client failver'. Please let me know if I am wrong.
Questions:
1. Please throw some light to achieve above features.
2. As per my understanding, before client failover happens, fast failover should have already occured and standby should get switch to primary role. I guess all this happens through TIMEOUT parameters. What are those.
Could you please help ?
Thanks

859875 wrote:
Goal 1:
Whenever RAC primary goes down completely, standby database should become primary database AUTOMATICALLY and it should allow read/write operation.
I guess this is called 'Fast Failover'. Please let me know if I am wrong.You are correct.
>
Questions :
- To make this happen, Do I need to configure Data Guard Broker so that standy database becomes primary when RAC goes down completely with planned or unplanned outage.Yes (you can also use Grid Control that will use Data Guard Broker).
>
Goal 2:
As I explained above, all Oracle IDM products and applications speak to RAC database they only know about RAC database which is primary.They are not aware of standby database.
- Whenever a client session is in progress with RAC primary database, if RAC goes down completely , we would like to expect client session should get transferred standby datbase without loosing session information:This is not possible: it is possible only for SELECT statement and only in a single RAC database.
You can find some interesting documents on MAA home page (best pratices, case studies...):
http://www.oracle.com/technetwork/database/features/availability/maa-090890.html

Load balancing, failover and fallback in Non-Clustered WebLogic environment

hi,
Has anyone implemented WebLogic 10.3.3 (or 10.3.4) in a Non-Clustered environment, but also got load balancing, failover and fallback work?
We were successful in getting failover working using t3://server1:7001,server2:7002 provider URL, but not load balancing or fallback.
The fallback is working when it was connecting to server2 and if we kill server2, then it switches to server1, but not when server2 is still running while server1 comes back.
All we need to find a way to enforce fallback to primary site, even if secondary which the client connected is still up and running and primary site comes back.
Any help appreciated.
Thanks.
Best regards,
Bala

hi,
Has anyone implemented WebLogic 10.3.3 (or 10.3.4) in a Non-Clustered environment, but also got load balancing, failover and fallback work?
We were successful in getting failover working using t3://server1:7001,server2:7002 provider URL, but not load balancing or fallback.
The fallback is working when it was connecting to server2 and if we kill server2, then it switches to server1, but not when server2 is still running while server1 comes back.
All we need to find a way to enforce fallback to primary site, even if secondary which the client connected is still up and running and primary site comes back.
Any help appreciated.
Thanks.
Best regards,
Bala

LRT224 Load Balancing and Link Failover

Hi, I am new to this forum. I have recently set up the LRT224 with two different ISP's. I am having problems configuring the Load Balance and Link Failover.
When I have Load Balance selected only one ISP (WAN 1) is active, the other (WAN2, ISP modem) remains inactive. Why is Load Balance only engaging one ISP?
When I have Link Failover selected, even with attempts and seconds configured to one second, and WAN1 has packets lost, it doesn't switch over to WAN2.
I am not tech savey but any help will be greatly appreciated so that I can get both ISP's active with Load Balance or at least have Link Failover work almost instantly. Thanks.

Hi @BSue2015,
If both WAN1 and WAN2 are already getting IP Addresses from your ISPs then we can say that Load Balance is working. To check it further, do a speed test by going to http://www.speedtest.net. Dual WAN connections are doubling the amount of available full speed connections due to the load balancing. The speed should have its maximum throughput even if you have several users on the network.

Always On - async mode - Failover and failback check list

Hi All,
Our production is configured with Always On in Async mode with DR.
We are planning to do a failover and failback on the Availability Groups in weekend.
Apart from the time consuming to do a failover and failback, does anyone having complete checklist on what all has to be checked at the time of failover and failback?
Thanks in advance!

Hi MvKalyan,
In AlwaysOn Avaliability Groups, when availability replicas are configured for asynchronous-commit mode, it supports only the manual failover mode. For more details, please review this article:
Failover and Failover Modes (AlwaysOn Availability Groups).
Before performing a failover of SQL Server AlwaysOn Avaliability Group, there are several things should be considering, such as data loss, connectivity problems and so on. For more information, you can review this online blog:
Before You Fail Over a SQL Server AlwaysOn Availability Group.
Thanks,
Lydia Zhang

PIX Failover and HW.

Hi all,
I have some more question about HW and PIX failover.
What happens when I connect two PIXs..
one UR license and one FO license and my
FO PIX takes activity over and my PIX with UR license will be corrupted so that I will need to disconnect it completely to repair it? I know that when someone wants to use FO PIX standalone than PIX reboots per 24 hours cycle. How PIX determines that it is not used standalone? I think that when I switch off first PIX in pair so second PIX in pair with FO license will function standalone.
Could you give me some explanation?
BR
jl

I guess you won't take magic as an answer? ;-)
I am assuming you are using Serial Failover, no?
So, when the PIX pair powers up, both units detect each other. If you then later remove the UR PIX from the mix, the FO will remain up and actively passing traffic indefinately. (Or almost so. At least until the next power outage). The licensing restriction only kicks in if the FO unit does not detect a UR unit at boot.
If this answers your question (I believe it does) please check the box so we can see one of those nice red checks :-)
Sincerely,
David.

Difference between closing the connection before and after committing user transaction?

          I was wondering what's the difference between closing the connection before committing
          the transaction versus closing the connection after committing the transaction?...
          for e.g....
          Scenario 1.........
          UserTransaction useretran;
          usertran.begin();
          Connection con = datasource.getCOnnection();
          // do bunch of stuff...
          conn.close();
          usertran.commit()
          Scenario 2...
          UserTransaction useretran;
          usertran.begin();
          Connection con = datasource.getCOnnection();
          // do bunch of stuff...
          usertran.commit()
          conn.close();
          thanks....
          Srini


Hi. As long as you're sure there's a transaction going on, and the connection
is a transaction-aware object (from a TxDataSource), either will be fine.
In the first scenario the actual semantics of the close() call are less than
normal, because we really don't close the connection or return it to the
pool until the actual transaction commits, and in the second case, we have
already taken the connection out of your service as of the commit().
The second scenario is the usual coding style. If there's ever a chance your
code will get non-transaction-aware connections, it is crucial to close
connections, and I always recommend putting the close() in a finally block
so it's guaranteed to happen.
Joe
srinivas wrote:
I was wondering what's the difference between closing the connection before committing
the transaction versus closing the connection after committing the transaction?...
for e.g....
Scenario 1......... UserTransaction useretran; usertran.begin(); Connection con =
datasource.getCOnnection(); // do bunch of stuff... conn.close(); usertran.commit()
Scenario 2... UserTransaction useretran; usertran.begin(); Connection con = datasource.getCOnnection();
// do bunch of stuff... usertran.commit() conn.close();
thanks....
Srini

Master Data and Transaction Data For DB Connect extracted Data...

Dear Experts,
I have been working on SAP NetWeaver BW 7.3 and for the first time I have extracted data from Oracle DBMS by using DB Connect. I have successfully extracted data of a View namely Sales_View into BW by creating a DataSource. This View has about 100 fields and I have been told that this view consists of Master Data and Transaction Data too. For my further reporting needs say building a Dashboard or InfoSpace I have to design a DSO and InfoCube for this DataSource. I'm bit confused about the Master Data and Transaction Data of this DataSource.
1. Should I create all custom InfoObject against all fields of DataSource for DSO and InfoCube design?
2. Do I need to create and load the Master Data for all InfoObjects or I need to create or load the Master Data for only those InfoOjects which will be
used for drill down or reporting in Dashboard or InfoSpace?
3. Do I need to load the Master Data manually by creating Flat Files and using these files for Master Data loading for required objects?
4. How should I approach the designing of DSO and InfoCube?
I will appreciate your inputs in this matter.
Many thanks!
Tariq Ashraf

Thanks!

New Note 790189.1 - Oracle Clusterware and Application Failover Management

Hi all,
please, note the newly created Metalink Note 790189.1 - Oracle Clusterware and Application Failover Management if you want to use Oracle Clusterware as a general purpose cluster solution. The note intends to clarify and to explain the current situation in regards to the supportability of applications managed by Oracle Clusterware.
In environments not including Oracle RAC, Oracle Clusterware still provides the level of high availability that is commonly known to be achievable for applications and databases managed in (failover) cluster environments. These environments can include Oracle Single Instance Databases, Oracle Application Servers, Oracle Enterprise Manager components, third party databases, or any other kind of application. (For more information on Oracle Clusterware 11g in general, please, refer to [Oracle Clusterware homepage|http://otn.oracle.com/clusterware].)
Metalink Note 790189.1 - Oracle Clusterware and Application Failover Management is tightly integrated with the information on application failover management available on the [Oracle Clusterware homepage|http://otn.oracle.com/clusterware] and discusses typical questions like
* Terminology
* Script supportability and preconfigured agents
* How to prove that action scripts work outside of Oracle Clusterware
* Supportability of the Oracle Database Single Instance example scripts
* How do I know whether a certain script is supported as a preconfigured agent?
Metalink Note 790189.1, however, does not change the level of support that has been introduced for these kind of configurations as of Oracle Database 10g Release 2: "Generally, Oracle does not support action scripts in the strict terms of supporting individual code fragments. Oracle fully supports the integration of individual action scripts proven to run outside of Oracle Clusterware into the Oracle Clusterware management stack. Supported operations therefore typically involve crs_* commands such as crs_profile, crs_register, crs_setperm, crs_getperm, crs_start, crs_stop, and crs_relocate invoked on custom resources. If actions scripts are used as part of a preconfigured agent, Oracle or the application provider who provides the agent will support the integration of this agent, while only the application provider will provide support for the individual action scripts."
Just for your information. Thanks,
Markus

not meant to be a question - rather an announcement.

Connection failover and transaction failover

Similar Messages

Maybe you are looking for