hello...I am trying to simulate distrubuted transactions . we have 3 databases in a single machine.
commit point strength for database A is 100.
commit point strength for database B is 1
commit point strength for database C is 1.
i am doing a distributed transaction and i am shutting down the database B . then i commit . It then rolling back the transaction and keeping an entry in dba_2pc_pending . once i startup the database B it is removing the entry from dba_2pc_pending .
but i want to simulate the environment such that it should not rollback the transaction and once the database B is up then the transaction should be finished successfully either by oracle ( reco process) or mannually by using commit force .
please advice me
Thanks in advance.
what i want to do is to use commit force .
Is is a big topic, but in short, 2PC shall be used for any synchronous transactions but if u want that the transactions for remote database should remain in the queue(u decide the time) and be applied later use either Asynchronous Replication or Advanced Queue (Messaging System).