Many Thanks Mihajlo. This is what I wanted to know. I read about the TRANSACTION_CONSISTENCY parameter being deprecated on one of my online search result but I was unable to find the page again. Thanks a lot. On Tue, Nov 9, 2010 at 2:50 PM, Mihajlo Tekic <mihajlo.tekic@xxxxxxxxx>wrote: > Sundar, > > Starting from 10.2 TRANSACTION_CONSISTENCY parameter has been replaced with > PRESERVE_COMMIT_ORDER. > > > http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_lsbydb.htm#BABCJHGH > ~Mihajlo > > On Tue, Nov 9, 2010 at 8:53 AM, sundar mahadevan < > sundarmahadevan82@xxxxxxxxx> wrote: > >> Hi Group, >> This email was not replied by anyone in the group. I would like to bump it >> up to give it a try. Appreciate if someone could enlighten me on this. >> Thanks. >> >> >> On Fri, Nov 5, 2010 at 12:26 PM, sundar mahadevan < >> sundarmahadevan82@xxxxxxxxx> wrote: >> >>> Hi All, >>> Greetings. Background: 1 primary (10.3) with 1 logical standby (10.3) on >>> solaris sparc 64 bit. >>> >>> 1) I would like to know the difference between TRANSACTION_CONSISTENCY >>> parameter and PRESERVE_COMMIT_ORDER parameter in DBMS_LOGSTDBY.APPLY_SET. I >>> searched for these parameters online and tried to understand but I cannot >>> completely point out the differences. My Google search results on >>> TRANSACTION_CONSISTENCY refer to 9.2 version while PRESERVE_COMMIT_ORDER >>> refer to 10.1+ version. >>> 2) Has TRANSACTION_CONSISTENCY been replaced by PRESERVE_COMMIT_ORDER? or >>> is TRANSACTION_CONSISTENCY still valid? >>> >>> Please help. Thanks in advance. >>> >> >> >