Progress - 10.0B05
OS - 5.3 (32 bit)
It was recommended that I use 2phase commit by our vendor for a few databases that have transactions that update multiple databases. I am curious about the setup though.
While reading about the setup, I see that you can't use variable extents for the transaction log area. My question is, does the TL storage area work similar to the BI, truncating data following each completed transaction? Are there processes that manage this similar to probiw?
Also, there is a confusing note:
If you enable after-imaging for the coordinator database, the coordinator database automatically uses the AI file to log the status of each distributed transaction. If you disable after-imaging, the coordinator once again uses TL files.
--- If this is the case, with AI enabled all both databases, do I need to create the new areas? Why?
Lastly, should I plan for growth within the AI extents as well?
Thanks,
Matthew Couper
OS - 5.3 (32 bit)
It was recommended that I use 2phase commit by our vendor for a few databases that have transactions that update multiple databases. I am curious about the setup though.
While reading about the setup, I see that you can't use variable extents for the transaction log area. My question is, does the TL storage area work similar to the BI, truncating data following each completed transaction? Are there processes that manage this similar to probiw?
Also, there is a confusing note:
If you enable after-imaging for the coordinator database, the coordinator database automatically uses the AI file to log the status of each distributed transaction. If you disable after-imaging, the coordinator once again uses TL files.
--- If this is the case, with AI enabled all both databases, do I need to create the new areas? Why?
Lastly, should I plan for growth within the AI extents as well?
Thanks,
Matthew Couper
