Archives of the TeradataForum
Message Posted: Fri, 01 Jan 2010 @ 15:22:40 GMT
"Locking row for read" will not work because all MSR's contain statements that perform DML operations. We tried splitting the MSR into separate requests but problems only became worse. Even according to TD documentation, it is encouraged that we combine the statements and convert it into a single MSR(to avoid deadlocks) rather than sending them individually. The reason is that a MSR acquires locks(most restrictive in table id order) in advance before executing any statement in the MSR.
I guess, the locking logger options are the ones that come by default(Although i shall double check the same. Thanks for the tip). One thing that i definitely know is that the mode is 'snapshot' and not 'continuous'.
Thank you for your response. Looking forward for further suggestions.
|Copyright 2016 - All Rights Reserved
|Last Modified: 15 Jun 2023