March 30, 2020 - 4:16 pm UTC
Thanks for the answers.
1. I meant because this command can be executed. What does it do?
ALTER SYSTEM ENABLE DISTRIBUTED RECOVERY
2. Got it.
3. Got it.
4. Never mind. It comes with the distributed architecture. I think this is how things get done in this kind of architecture.
March 31, 2020 - 12:48 am UTC
From the docs:
" For example, you can temporarily disable RECO to force the failure of a two-phase commit and manually resolve the in-doubt transaction.
ALTER SYSTEM DISABLE DISTRIBUTED RECOVERY;"
This was a new discovery for me - I always thought that no RECO = no database instance.
But normal operation would obviously be for reco to be active.
April 08, 2020 - 2:21 am UTC
Thanks for the response.
Is there any way to automatically resolves a in-doubt transaction where the MSDTC is involved?
Thanks in advanced.
April 08, 2020 - 8:13 am UTC
I don't know what the MSDTC is, but as the docs say:No action is required by the administrator of any node that has one or more in-doubt distributed transactions due to a network or system failure. The automatic recovery features of the database transparently complete any in-doubt transaction so that the same outcome occurs on all nodes of a session tree (that is, all commit or all roll back) after the network or system failure is resolved.
But there are situations where you may want to do a manual recovery. Check the docs to see if any of these apply to you: https://docs.oracle.com/en/database/oracle/oracle-database/20/admin/managing-distributed-transactions.html#GUID-297F05FA-6F3E-40E6-8C11-C6B68CFAD9FE