ER's cdr stop & cdr suspend
Frank saw ER keep capturing data after cdr stop on IDS 10 UC5 and replicate it after cdr start, despite the docs. Nilesh Ozarkar explained that cdr start resumes log evaluation at the replay position where it stopped, and 'cdr stop replicate' stops capture for a replicate. Madison Pruet said cdr cleanstart advances capture to a new point. Frank thanked them.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
HI, Folks, Just a curious question, According the doc, "cdr stop" will stop capturing data to be replciated, "cdr suspend" will continue capturing data but not sending . Form our test, ER still captures data to be replicated even after you run "cdr stop" and it will replicate it after you issue "cdr start". Any comments? IDS 10 UC5, AIX 5.3 Thanks, Frank
Frank, When you do 'cdr start', ER resumes evaluation of the logical log at the replay position (the position where ER stops evaluating the logical log when 'cdr stop' was executed.) That's why you notice data being replicated when 'cdr start' was issued. Use 'cdr stop replicate' to stop data capture and transmission for that specific replicate. HTH, -Nilesh ids-bounces@iiug.org wrote on 11/20/2007 01:07:07 PM: > HI, Folks, > > Just a curious question, > According the doc, "cdr stop" will stop capturing data to be > replciated, "cdr suspend" will continue capturing data but not > sending . > > Form our test, ER still captures data to be replicated even after > you run "cdr stop" and it will replicate it after you issue "cdr > start". > > Any comments? > > IDS 10 UC5, AIX 5.3 > > Thanks, > Frank > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >
CDR stop will stop will stop the capture. cdr start will resume the capture as of the point that cdr stop was issued. If you want to compl= etly advance to a new point in time with capture, you would need to issue 'c= dr cleanstart' = "FRANK" = <yunyaoqu@gmail.c = om> = To Sent by: ids@iiug.org = ids-bounces@iiug. = cc org = Subj= ect ER's cdr stop & cdr suspend = 11/20/2007 01:07 [10418] = PM = = = Please respond to = ids@iiug.org = = = HI, Folks, Just a curious question, According the doc, "cdr stop" will stop capturing data to be replciated, "cdr suspend" will continue capturing data but not sending . Form our test, ER still captures data to be replicated even after you run "cdr stop" and it will replicate it after you issue "cdr start". Any comments? IDS 10 UC5, AIX 5.3 Thanks, Frank ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. =
Nilesh and Madison , Thank you very much and Happy Thanksgiving!! On Nov 20, 2007 4:03 PM, Nilesh Ozarkar <nilesho@us.ibm.com> wrote: > Frank, > > When you do 'cdr start', ER resumes evaluation of the logical log at the > replay position (the position where ER stops evaluating the logical log > when 'cdr stop' was executed.) That's why you notice data being replicated > when 'cdr start' was issued. Use 'cdr stop replicate' to stop data capture > and transmission for that specific replicate. > > HTH, > > -Nilesh > > ids-bounces@iiug.org wrote on 11/20/2007 01:07:07 PM: > > > HI, Folks, > > > > Just a curious question, > > According the doc, "cdr stop" will stop capturing data to be > > replciated, "cdr suspend" will continue capturing data but not > > sending . > > > > Form our test, ER still captures data to be replicated even after > > you run "cdr stop" and it will replicate it after you issue "cdr > > start". > > > > Any comments? > > > > IDS 10 UC5, AIX 5.3 > > > > Thanks, > > Frank > > > > > > > > ******************************************************************************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > >