Distributed Transactions HA and DR

We have a few SQL Server environments besides Biztalk and its speciall HA and DR configuration(SQL Server failover cluster and Biztalk Log Shipping) that use distributed transactions. Is there a HA or DR solution that supports distributed transactions
other than failover clustering? I am aware that database mirroring is not supported for distributed transactions. How about log shipping or replication? Is there any official documentation on this?
Thank you in advance

Hello,
As Shanky post, there is limitation of distributed transactions when using database mirroring or log shipping. When using Microsoft Distributed Transaction Coordinator (MSDTC) transactions, the local transaction coordinator has a resource ID that identifies
the server on which it is running. When a mirroring or log shipping failover occurs, the principal database becomes hosted on a different server (the mirroring partner or secondary server), and so the resource ID of the transaction coordinator is different.
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

Similar Messages

Distributed transactions, EJB and Sun Java App Server

Hello,
I'm trying to implement a CMT Stateless EJB that inserts data into a Oracle 9.2 table. All this running into a Sun Java System App Server 8.2 and using a XA Database Connection Pool.
Before starting bothering you, a simple question: has anybody successfully retrieved a connection from a XA connection pool? I've read somewhere that Oracle thin client is very limited and I wonder if one of its limitations would be "no support to XA transactions".
My pool information:
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="oracle.jdbc.xa.client.OracleXADataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" max-pool-size="32" max-wait-time-in-millis="60000" name="MyXAPool" pool-resize-quantity="2" res-type="javax.sql.XADataSource" steady-pool-size="8" transaction-isolation-level="read-committed">
<property name="DataSourceName" value="OracleXADataSource"/>
<property name="ImplicitCachingEnabled" value="false"/>
<property name="NetworkProtocol" value="tcp"/>
<property name="LoginTimeout" value="0"/>
<property name="Password" value="arbor123"/>
<property name="URL" value="jdbc:oracle:thin:@HostName:1521:Alias"/>
<property name="NativeXA" value="false"/>
<property name="User" value="arbor"/>
<property name="ExplicitCachingEnabled" value="false"/>
</jdbc-connection-pool>
I created a jdbc resource called jdbc/__myxa so I can access the database pool using JNDI.
The code:
InitialContext jndiContext = new InitialContext();
DataSource ds = (DataSource) jndiContext.lookup("jdbc/__myxa");
Connection con = ds.getConnection();
PreparedStatement ps = con.prepareStatement( "INSERT INTO TESTE_CLAUDIO( MSG, MSG_DT) VALUES ('" + aMessage + "', SYSDATE)" );
ps.execute();
con.close();
When attempting to get the connection, I got an exception saying that:
"This Managed Connection is not valid as the phyiscal connection is not usable"
Thanks for any information

Hi Claudio,
J2EE applications should retrieve all their resources through their component environment (java:comp/env) -- not by doing a global JNDI lookup. You should declare a resource-ref in ejb-jar.xml for the bean and then map that resource-ref to your physical data source (jdbc/__myxa) in sun-ejb-jar.xml. E.g, if the res-ref-name is "foo", your code would look it up under context.lookup("java:comp/env/foo");
--ken

Can not commit distributed transaction

Hi
We get error "can not commit distributed transaction" during
commit the transaction in which we have create NEW entities.
Update-transactions on existing enitites work correct.
Our problem is probably due to seauences for object IDs: we are using oracle native sequences:
<sequence name="SeqErrRecObj" strategy="nontransactional" factory-class="native(Sequence=BUYING.SEQ_ERRRECOBJ)"/>
As soon we use strategy="nontransactional" in managed environment,
we get "can not commit distributed transaction" error by creating new instance.
Switching to strategy="transactional" seems to eleminate this problem.
I did not found any hint in about this in documentation.
Can some one confirm our assumption that using nontransactional oracle sequences in manageg (WebLogic 9.2) environment
is responsible for "can not commit distributed transaction" error and "strategy=transactional" is the right solution.
Probably we are completely wrong and tehre is some other explanation for this error ?
kind regards
Andre Teshler

Hi Andre,
It sounds like you have not configured a non-transactional datasource. See section "4.2.1. Managed and XA DataSources" in the <kodo>/docs/jdo/pdf/manual.pdf. Connection is for the managed datasource and Connection2 for the non-transactional.
David Ezzio

ORA-01591: lock held by in-doubt distributed transaction

I am using oracle wcf adapter to connect to oracle to insert.
I am getting the ORA-01591: lock held by in-doubt distributed transaction.
Any ideas as to what could be the resolution. I have followed the below mentioned steps. but that's not a permanent solution.
Please advice.
The resolution described below is not acceptable and never should have been used. Although it does avoid the error, it's not okay to turn off AmbientTransaction when performing inserts
and/or updates. A different solution needs to be found.<o:p></o:p>
http://msdn.microsoft.com/en-US/library/dd788352(v=BTS.10).aspx <o:p></o:p>
"Not performing operations in a transactional context is advisable only for operations that do not make changes to the database. For operations that update data in the database, we recommend
setting the binding property to true otherwise you might either experience message loss or duplicate messages depending on whether you are performing inbound or outbound operations."<o:p></o:p>
********************************************<o:p></o:p>
This can be resolved by adjusting the configuration settings on the Oracle adapter, accessible via the Send Port properties. The properties and the values that should be used are shown below:<o:p></o:p>
** Binding tab:
incrPoolSize: 1
maxPoolSize: 10
useAmbientTransaction: False<o:p></o:p>
** Messages tab:
Isolation Level: ReadCommitted<o:p></o:p>
Also, you'll need to get a DBA to rollback the hanging "in-doubt" transactions, which will be viewable via the sql below. Otherwise, if you try processing the same data again, you'll
still get the same error.<o:p></o:p>
SELECT LOCAL_TRAN_ID, GLOBAL_TRAN_ID, STATE, MIXED, HOST, COMMIT# FROM DBA_2PC_PENDING;<o:p></o:p>
The transactions can be rolled back with sql, using this syntax:<o:p></o:p>
ROLLBACK FORCE '<LOCAL_TRAN_ID>';
<o:p></o:p>
Thank you and have great day! Vivek Kulkarni MCAD.net

Hi Vivek,
This error is encountered by many DBA's and cause problem by locking the distributed transaction process, and not letting the query go through, because the Two - Phase Commit Mechanism got an error somewhere.
he DBA should query the pending_trans$ and related tables, and attempt to repair network connection(s) to coordinator and commit point.
Here are some codes to help you through the process:
This one brings in-doubt transactions:
select * from DBA_2PC_PENDING where state='prepared'
This one prepares the rollback script for the transactions:
select 'rollback force '''||local_tran_id||''';' from DBA_2PC_PENDING where state='prepared'
All this is well described in below link
ORA-01591: lock held by in-doubt distributed transaction
ORA-01591: lock held by in-doubt distributed transaction string tips
On BizTalk Side you need to make ambient transaction to false as Oracle does not go ahead with DTC Transaction with Biz Talk
Thanks
Abhishek

Distributed transactions with container-managed MDBs

          I have built a framework that employs a high rate of code reuse while abstracting
          the complexities of inter-application communication. This allows application
          developers to focus on solving their business needs and not worry about "the plumbing"
          between the applications.
          At this point, the framework is using container-managed MDBs for Topic destinations.
          MDBs were chosen because of their concurrent nature for processing JMS messages.
          Now that I have this framework up and running, I am trying to add distributed
          transaction support and am having trouble understanding what I need to do. Here
          is how the framework works:
          The MDB will recieve a message, unmarshall it into a business object, and then
          route that object to the appropriate business class where it is then processed
          accordingly. In most cases, the processing of this message object will require
          database interaction. If any error should occur while processing the message,
          all XAResources within the transaction should rollback and ultimately, the JMS
          message will be redelivered later.
          Here is what I'm trying to find out:
          1. When control is passed to an application and it gets a DB connection, will
          that DB resource be dynamically enlisted with the transaction?
          2. Must the DB connection come from the WLS DB pool to be enlisted with the transaction?
          I ask this because the current standard at this company is to use a home-grown
          DB connection pool for getting DB connections. This is due to the fact that not
          all applications here run in a WLS environment and they wanted a standard way
          of retrieving a DB connection across applications. They also sited problems with
          WLS 4.5.1 connection pool.
          3. The documentation states that only one database may be involved in a transaction.
          If a connection to another database is required, but not needed in the current
          transaction, will WLS ignore enlisting the 2nd DB resource, or throw an exception?
          4. Where can I find <B>detailed</B> information about this subject? Everything
          that I have read so far has barely scratched the surface for this specific topic.
          Thanks,
          Bob.


          Hi Bob,
          If you are using WLS's XA connection pool, then the XAResource associated with
          the XA connections are enlisted with the transaction transparently for you. Enlistments
          actually occur not at getConnection, but on demand when the JDBC objects are actually
          used.
          If you are not using WLS connection pools, then you would need to enlist the XAResource
          associated with the XA connections yourself. You can obtain the transaction associated
          with the current thread by calling weblogic.transaction.TxHelper.getTransaction(),
          and then call enlistResource on the transaction.
          Weblogic has provisions that allow one (and only one) non-XA connection pool to
          participate in a distributed transaction. In this case, you will get a SQLException
          when you try to obtain a connection from a second connection pool in the same
          distributed transaction. However, if you are using real XA connection pools,
          there is no limitation and any number of XA connection pools can participate in
          the same distributed transaction.
          We will try to incorporate more info in our online docs in the future.
          -- Priscilla Fung, BEA Systems, Inc.
          "Bob Peroutka" <[email protected]> wrote:
          >
          >I have built a framework that employs a high rate of code reuse while
          >abstracting
          >the complexities of inter-application communication. This allows application
          >developers to focus on solving their business needs and not worry about
          >"the plumbing"
          >between the applications.
          >
          >At this point, the framework is using container-managed MDBs for Topic
          >destinations.
          > MDBs were chosen because of their concurrent nature for processing JMS
          >messages.
          >
          >Now that I have this framework up and running, I am trying to add distributed
          >transaction support and am having trouble understanding what I need to
          >do. Here
          >is how the framework works:
          >
          >The MDB will recieve a message, unmarshall it into a business object,
          >and then
          >route that object to the appropriate business class where it is then
          >processed
          >accordingly. In most cases, the processing of this message object will
          >require
          >database interaction. If any error should occur while processing the
          >message,
          >all XAResources within the transaction should rollback and ultimately,
          >the JMS
          >message will be redelivered later.
          >
          >Here is what I'm trying to find out:
          >
          >1. When control is passed to an application and it gets a DB connection,
          >will
          >that DB resource be dynamically enlisted with the transaction?
          >
          >2. Must the DB connection come from the WLS DB pool to be enlisted with
          >the transaction?
          >
          >I ask this because the current standard at this company is to use a home-grown
          >DB connection pool for getting DB connections. This is due to the fact
          >that not
          >all applications here run in a WLS environment and they wanted a standard
          >way
          >of retrieving a DB connection across applications. They also sited problems
          >with
          >WLS 4.5.1 connection pool.
          >
          >3. The documentation states that only one database may be involved in
          >a transaction.
          > If a connection to another database is required, but not needed in the
          >current
          >transaction, will WLS ignore enlisting the 2nd DB resource, or throw
          >an exception?
          >
          >4. Where can I find <B>detailed</B> information about this subject?
          > Everything
          >that I have read so far has barely scratched the surface for this specific
          >topic.
          >
          >Thanks,
          >
          >Bob.

Windows could not start the distributed transaction coordinator service on local computer

Dear All,
I'm having an issue starting the DTC service in windows 7 OS. I always got the error message below when im trying to start it.
"Windows could not start the distributed transaction coordinator service on local computer"
Thanks,
Melvin

Hi Melvin,
Please try the following methods to solve this issue:
Method 1: Re-create the MS DTC log, and then restart the service.
Click
Start, type cmd in the search box, and then press
Enter.
Type the command
msdtc -resetlog at the command prompt, and then press
Enter.
Warning: The msdtc -resetlog command can cause data corruption if it is used incorrectly. Make sure that you do not have any pending transactions when you run this
command.
Type the command net start msdtc, and then press
Enter.
Method 2: Set the logon account permissions for the MS DTC service
If Method 1 does not resolve the problem, set the logon account for the MS DTC service to have read and write permissions for the Msdtc.log file. Please follow the steps below:
Click
Start, type cmd in the search box, and then press
Enter.
Type the command
control admintools at the command prompt, and then press
Enter.
Double-click
Services.
In the Services pane, locate
Distributed Transaction Coordinator.
In the
Log On As column, note the account name. Note: The default logon account for the MS DTC service is the NETWORK SERVICE account.
Start Windows Explorer, and
then open the %windir%\System32\Msdtc folder.
Right-click the
Msdtc.log file, and then click Properties.
Click the
Security tab.
Click the logon account name that you noted
in step 5. For example, click the NETWORK SERVICE account name.
In the
Permissions pane, click to select the Allow check box for the following permissions: ◦Read & Execute
◦Read    ◦Write
Click
OK.
Click
Yes to accept the security warning.
In the
Services pane, right-click Distributed Transaction Coordinator, and then click
Start.
Method 3: Assign permissions to the NETWORK service to traverse the directory tree
Determine whether the NETWORK service has permissions to traverse through the folder. To do this, follow these steps.
Note: By default, the "Everyone" group has these permissions. For more information, go to the following Microsoft TechNet website:
Bypass traverse checking
Click
Start, type secpol.msc in the search box, and then press
Enter.
Browse through the following computer configuration:
        \Windows Settings\Security Settings\Local Policies\User Rights Assignment
Check for "Bypass traverse checking," and then add the "Everyone" group.
Update the Group Policy settings on the computer. To do this, click
Start, type gpupdate in the search box, and then press
Enter.
In the
Services pane, right-click Distributed Transaction Coordinator, and then click
Start.
Regards,
Lany Zhang

EJB 3.0 and JTA (Distributed transactions)

hi, first of all sorry for my english.
then :)
i'm working with JBoss Aplication Server an Oracle DataBase using EJB 3.0
i have no problem before ... but now i want work with multiple database and i wand to manage transactions ... how i understand JTA (Java Transaction Api) is a technology for it.
i think that i need two datasource file for example oracle-xa-ds.xml and postgres-ds.xml
<datasources>
<xa-datasource>
    <jndi-name>XAOracleDS</jndi-name>
    <track-connection-by-tx/>
    <isSameRM-override-value>false</isSameRM-override-value>    <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
    <xa-datasource-property name="URL">jdbc:oracle:thin:@192.9.200.177:1521:devnbtwo</xa-datasource-property>
    <xa-datasource-property name="User">paata</xa-datasource-property>
    <xa-datasource-property name="Password">1982226</xa-datasource-property>   <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
    <no-tx-separate-pools/>
      <metadata>
         <type-mapping>Oracle9i</type-mapping>
      </metadata>
</xa-datasource>
<mbean code="org.jboss.resource.adapter.jdbc.vendor.OracleXAExceptionFormatter"
         name="jboss.jca:service=OracleXAExceptionFormatter">
    <depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager</depends>
</mbean>
</datasources>
<datasources>
<local-tx-datasource>
    <jndi-name>PostgresDS</jndi-name>
   <connection-url>jdbc:postgresql://localhost:5432/Test</connection-url>
    <driver-class>org.postgresql.Driver</driver-class>
    <user-name>postgres</user-name>
    <password>1982226</password>
        <new-connection-sql>select 1</new-connection-sql>
      <metadata>
         <type-mapping>PostgreSQL 7.2</type-mapping>
      </metadata>
</local-tx-datasource>
</datasources>and i dont know what should i do in my persistance.xml file ..... when i was working with single database my persistance.xml file was working
<?xml version="1.0" encoding="UTF-8" ?>
<persistence xmlns="http://java.sun.com/xml/ns/persistence"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
     version="1.0">
     <persistence-unit name="Oracle" transaction-type="JTA">
          <jta-data-source>java:/XAOracleDS</jta-data-source>
          <class>com.magti.businesslayer.ejb3entity.Group</class>
          <class>com.magti.businesslayer.ejb3entity.Student</class>
          <properties>
               <property name="hibernate.dialect" value="org.hibernate.dialect.OracleDialect"/>
               <property name="hibernate.connection.driver_class" value="oracle.jdbc.driver.OracleDriver"/>
               <property name="hibernate.connection.url" value="jdbc:oracle:thin:@192.9.200.177:1521:devnbtwo"/>
               <property name="hibernate.connection.username" value="paata"/>
               <property name="hibernate.connection.password" value="1982226"/>
               <property name="hibernate.default_schema" value="PAATA"/>
          </properties>
     </persistence-unit>
</persistence>but then i added anothe unit for second database and i get error
     <persistence-unit name="PostgreSql" transaction-type="JTA">
          <jta-data-source>java:/PostgresDS</jta-data-source>
          <class>com.magti.businesslayer.ejb3entity.Group</class>
          <class>com.magti.businesslayer.ejb3entity.Student</class>
          <properties>
               <property name="hibernate.dialect" value="org.hibernate.dialect.PostgreSQLDialect"/>
               <property name="hibernate.connection.driver_class" value="org.postgresql.Driver"/>
               <property name="hibernate.connection.url" value="jdbc:postgresql://localhost:5432/Test"/>
               <property name="hibernate.connection.username" value="postgres"/>
               <property name="hibernate.connection.password" value="1982226"/>
               <property name="hibernate.default_schema" value="postgres"/>
          </properties>
     </persistence-unit>     i don't know how i resolve it .
i can't find any simple exaplme about distributed transactions on net ...
can anybody help me ....
thanks.

Check this one:
http://www.webagesolutions.com/knowledgebase/javakb/jkb005/index.html

ORA-00164 Autonomous and Distributed Transactions in Oracle 8i - Forms6i

Hi, in Forms6i I'm using Autonomous transactions (insert and update), and I want to use also a database link to make a query in a remote database (Distributed transaction). Even when this request are done in different PL/SQL within Forms6i, I get the error message ORA-00164 Distributed transactions disallowed within autonomous transactions. Is there a way to avoid this error message?
Thanx

Hello,
I had a similar Problem, when I tried to log errormessages while selecting by db-link.
I use pipes now to send the errormessages. The pipe is read at regular intervals and then I can Insert without using autonomous transactions.
I hope, this will help you
Marcus

Is Distributed Transaction Coordinator services of the application role are required by SQL Server 2012 for clustering and support of SharePoint 2013.

All I want to know is if Distributed Transaction Coordinator services of the application role are required by SQL Server 2012 for clustering and support of SharePoint 2013.
I have been planning and deploying my companies first Windows Server 2012/SQL Server 2012 Always On cluster and Always On Availability Groups Multi-Subnet cluster and instances for SharePoint 2013, and I will be brutally honest, the documentation on either
the MSDN and TechNet leave alot to be desired. Continually finding links in the documentation will take me from a Windows 2012 reference to a page talking about Windows Server 2008 or R2, The differences of which there are so many when it comes to configurations,
settings, roles, services when working with SQL Server 2012. I have been confused, frustrated, screaming mad, with all the misdirection in this documentation. The documentation takes me windows 2008 R2 which is different than 2012!
Tired and trying to pick myself up off the floor!
Greg
Gman

In general, DTC is not required for SQL 2012. But, since you are asking specifically about SharePoint, it would be better to ask in a SharePoint forum. They would be more likely to know those situations where FTC might be needed by SharePoint.
.:|:.:|:. tim

Distributed transactions and 2-phase commit in a SAP Netweaver environment

Hello,
I am a Java architect., I don't know very much the SAP technologies. I tried to found on forums or technical papers if SAP does support distributed transactions and two-phase commit, it's not clear. I found something on SAP WAS but my project is using a SAP PI 7.0 and I cannot find anything on the subject.
My goal is to include a SAP server (via PI 7.0) in a distributed transaction handled by a J2EE ESB (Oracle, ex-BEA Aqualogic) based on XA capabilities.
Does anyone have experience or feedback on this topic ?
Thanks.

Hi,
Do you know this white paper ?
[Distributed Transaction and 2 phase commit|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/3732d690-0201-0010-a993-b92aab79701f]
Regards,
Olivier

Using Distributed Transaction with oracle 9i and VB

How to I get distributed transaction to work between a COM + object in VB and oracle using MSDAORA.1 driver? I keep getting the following error:
error number:
-2147168229
error description:
Cannot connect to the transaction manager or the transaction manager is unavailable.

Oracle 9i works great with VB.NET. I would recommend you to use Oracle Data Provider .NET (ODP.NET) as a database driver
http://otn.oracle.com/tech/windows/odpnet/content.html
for better performance and get full advantage of Oracle 9i features.
Regards
Jagriti
OTN Team @IDC

Weblogic 5.1, Distributed Transaction and Oracle Database Link

We are planning to add a new functionality to run in Weblogic server and it
needs to update tables in two different Oracle databases. Since we are using
Weblogic 5.1 and it is unrealistic to upgrade to 6.1 in short term, we have
to deal with the fact that distributed transaction is not supported by JTS
on 5.1.
One workaround we can think of is to utilize Oracle database link. Instead
of having two connection pools, the application talks to only one database
and access the tables on the other ones through Oracle database link.
Therefore, when a session bean tries to update two tables on database 1 in
one transaction, one of the tables is just a link to the other database. We
hope that even though distributed transaction is not supported by JTS in
Weblogic 5.1, but since it is supported by Orable, it would work.
Do you think the above workaround would work? Does anyone have experience on
something like that?
Thanks in advance,
David Chen
[email protected]

Hi. You should be able to use any JDBC driver with WebLogic 5.1.
It may be the JVM that complains, if you use too old a JVM...
Joe Weinstein at BEA Systems

Distributed Transactions and Linked Servers

I'm somewhat of a novice with SQL Server but I'm learning rapidly from an application I'm developing that uses SQL Server very heavily. In conjunction with the development of this application, I have 3-4 systems set up running SQL Server and I am using those
systems to develop the database that will ultimately support the application. I decided to try to use linked servers because I am moving data back-and-forth among the different servers frequently and I ran into some consequences that I wasn't expecting.
I was doing a simple delete query on one of the servers (Delete from TableName Where ...) and I was expecting, of course, that it would only impact the server I was running it on; however, when the query finished after running for a long time, it was apparent
that SQL Server had automatically escalated that simple delete query into a distributed transaction and applied it to all four of the linked servers I had defined. I was totally surprised by that and it took some time to recover the data that was inadvertently
lost on the other servers.
I want to ensure that this doesn't happen again without me expecting it - I think the right way to prevent this from happening is to run the following stored procedure:
EXEC sp_serveroption 'servername', 'remote proc transaction promotion', 'false';
Can someone please verify that this assumption is correct and will prevent SQL Server from automatically creating distributed transactions impacting multiple servers?
Thanks,
Chuck

Hello,
Based on your description, it seems that when you connect to a SQL Server database and execute a DELETE statement to delete a recode on a table, and then the same recode were delete in the linked server which has the same table.
As pre my understand, the statement executed on one server will not apply to the linked servers unless you specify the logic yourself in the application. For example, you use dynamic query and exec the query synchronously on linked servers.
What's more, did you specify replication between this linked server?
If I have any misunderstanding, please let me know.
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

Using ATMI and tuxedo to institue distributed transactions across multiple DBs

I am creating the framework for a given application that needs to ensure that data
integrity is maintained spanning multiple databases not necessarily within an
instance of weblogic. In other words, I need to basically have 2 phase commit
"internet transactions" between a given coordinator and n participants without
having any real knowlegde of their internal system.
Originally I was thinking of using Weblogic but it appears that I may need to
have all my particular data stores registered with my weblogic instance. This
cannot be the case as I will not have access to that information for the other
participating sytems.
I next thought I would write my own TP...ouch. Everytime I get through another
iteration I kept hitting the same issue of falling into an infinite loop trying
to ensure that my coordinator and the set of participants were each able to perform
the directed action.
My next attempt has led me to the world of ATMI. Would ATMI be able to help me
here. Granted I am using JAVA so I am assuming that I would have to use CORBA
to make the calls but will ATMI enable me to truly manage and create distributed
transactions across multiple databases. Please, any advice at all would be greatly
appreciated.
Thanks
Chris

Andy
I will not have multiple instances of weblogic as I cannot enfore that
the other participants involved in the transaction have weblogic as
their application server. That being said, I may not have the choice
but to use WTC.
Does this make more sense?
Andy Piper <[email protected]> wrote in message news:<[email protected]>...
"Chris" <[email protected]> writes:
I am creating the framework for a given application that needs to ensure that data
integrity is maintained spanning multiple databases not necessarily within an
instance of weblogic. In other words, I need to basically have 2 phase commit
"internet transactions" between a given coordinator and n participants without
having any real knowlegde of their internal system.
Originally I was thinking of using Weblogic but it appears that I may need to
have all my particular data stores registered with my weblogic instance. This
cannot be the case as I will not have access to that information for the other
participating sytems.I don't really understand this. From 6.0 onwards you can do 2PC
between weblogic instances, so as long as the things you are calling
are transaction (EJBs for instance) it should all work out fine.
I next thought I would write my own TP...ouch. Everytime I get through another
iteration I kept hitting the same issue of falling into an infinite loop trying
to ensure that my coordinator and the set of participants were each able to perform
the directed action.
My next attempt has led me to the world of ATMI. Would ATMI be able to help me
here. Granted I am using JAVA so I am assuming that I would have to use CORBA
to make the calls but will ATMI enable me to truly manage and create distributed
transactions across multiple databases. Please, any advice at all would be greatly
appreciated.I don't see that ATMI would give you anything different. Transaction
management Tux is fairly similar to WebLogic (it was written by the
same people). If you are trying to do interposed transactions
(i.e. multiple co-ordinators) then WTC would give you this but it is
only a beta feature in WLS 6.1. Using Tux domain gateways would also
give you interposed behaviour but would require you write your servers
in C or C++ ....
andy

Distributed transactions and connection pooling

Hi,
We have a problem with the enlistment of connections in distributed transactions.
The following very simple C# program does not work correctly (a simple form with one button and a class hosted in COM+). If you put a breakpoint on "cnOraTx.Close();" you will see that the inserted record is already visible in the database although the transaction has not commited yet.
If you comment out the lines between //START and //END everything works as expected.
Also, if we use "Pooling=false" in the connection string, everything works fine again, but since we are writing a web application, we really need the connection pooling.
We are using ODP.NET 9.2.0.2.102 (I also tried with the ODP.NET 9.2.0.4.0 BETA) and an oracle 8.1.7 database.
Best Regards,
Piet
private void button1_Click(object sender, System.EventArgs e)
//When commenting the following lines the connection is enlisted in the distributed transaction
//START
OracleConnection cnOraTx;
cnOraTx = new Oracle.DataAccess.Client.OracleConnection("Data Source=ECOMP532;User ID=USER;Password=PWD");
cnOraTx.Open();
cnOraTx.Close();
cnOraTx.Dispose();
//END
OpenOraTransConn obj = new OpenOraTransConn();
obj.Connect();
//This class is going to be hosted within COM+
[Transaction(TransactionOption.Required)]
public class OpenOraTransConn: ServicedComponent
private OracleConnection cnOraTx;
private OracleCommand cmd;
internal void Connect()
cnOraTx = new OracleConnection("Data Source=ECOMP532;User ID=USER;Password=PWD");
cnOraTx.Open();
cmd = new OracleCommand();
cmd.Connection = cnOraTx;
cmd.CommandText = "INSERT INTO SYSADM.PERSON (PE_KEY) VALUES(130000)";
cmd.ExecuteNonQuery();
cnOraTx.Close();
cnOraTx.Dispose();
ContextUtil.SetComplete();

Hello:
We are experiencing the exact same problem. INSERT, UPDATE or DELETE statements that should roll back because an exception is being thrown from inside our ServicedComponent-derived class (which is set to TransactionOption.Required and uses AutoComplete) are not -- and instead are being committed to the database.
Were you able to figure out why this is happening, and what can be done to get around it? We too were able to avoid the problem by setting Pooling=False to our connect string, but for a variety of reasons we want to use connection pooling ...!

Distributed Transactions HA and DR

Similar Messages

Maybe you are looking for