none
"in doubt" transaction in MS DTC set FCI DB on another instance to suspect mode

    Question

  • We currently have a SQL Server 2012 environment with FCI based on shared storages, our primary site consists of a two node cluster with one active and one passive, we also have MS DTC installed and running as a clustered resource.

    Our current issue is that when we create an "in doubt" transaction on the active node, then shutdown it, the other DB is changed to suspect mode and prevents any client connections. From the MS DTC, we can see one "in doubt" transaction there. Either we abort it or commit it, the instance can start well.

    However, we suppose the passive DB can take over the "in doubt" transaction silently and wait for the high level applications to decide whether to commit or rollback it.  Is it possible?

    Thanks,

    Holly



    • Edited by holly_yb Friday, February 21, 2014 10:51 AM
    Friday, February 21, 2014 10:24 AM

All replies

  • However, we suppose the passive DB can take over the "in doubt" transaction silently and wait for the high level applications to decide whether to commit or rollback it.  Is it possible?

    Thanks,

    Holly


    Hello.

    Its is not always possible depends on SQL Server if it is able to .But below link will guide to how to make changes so that either it is committed or aborted

    http://technet.microsoft.com/en-us/library/ms179586.aspx


    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

    Friday, February 21, 2014 10:38 AM
  • Thanks for your prompt help! in-doubt xact resolution option is just an option for all same operations.

    So there is no way for sql server FCI to work normally unless it recovers all 'in-doubt' transactions.

    Monday, February 24, 2014 7:54 AM