Re: Run 'onunload' on an HDR secondary?

I think you would want to do the onmode -c block and then breack replication then you are sure that nothing happened to secondary that would make it inconsistent. onmode -c block doesn't just force a checkpoint it holds the databasein a blocked state until you execute the unblock command. So I would type : onmode -c block ; onmode -d standard ; onmode -c unblock To make sure that fat fingering it doesn't keep the database blocked for very long. But onmode -d standard may make sure the secondary is in a consistent state before it releases it but probably not because the reason you might be breaking HDR is because the secondary is broken and can't be made consistent. David E. Grove wrote: > <mpruet@comcast.net> wrote in message > news:1152878622.836318.55940@h48g2000cwc.googlegroups.com... > > > > The secondary is in recovery mode and the recovery threads will > > continue to apply logs from the primary. > > > > > > I tried running onunload on the secondary, and it ran to completion just > fine. However, I conclude from above that the resulting onunload file may > not be consistent. > > I will do the suggested disabling of replication, then do the onunload, then > re-enable replication. > > Follow up questions.... Just out of curiosity... Is it actually necessary to > 'onmode -c block', etc. on the primary? Would I actually risk inconsistency > by not forcing a checkpoint? Also, could I avoid touching the primary and > just 'onmode' the secondary back to standard? (I'm thinking it would then > just be like when you initially start HDR, before you get the secondary > operational, and I could easily 'onmode' it back to secondary. [I got > plenty of log space on the primary.]) > > Thank you all for comments. > > Regards, > > DG