distributed database
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: distributed database

  1. #1
    Join Date
    Nov 2000
    Posts
    35
    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 .

  2. #2
    Join Date
    Feb 2001
    Posts
    389
    Use Asynchronous Replication or Advanced Queue.

  3. #3
    Join Date
    Nov 2000
    Posts
    35

    distibuted database

    hello..mr singh thanks for your reply
    can you please elaborate it . this is the first time i am doing distributed database...
    thanks

  4. #4
    Join Date
    Feb 2001
    Posts
    389
    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).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width