Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
zandy@skyinet.net — — source: Informix-list mailing list archive (1991-1998)
In article <3563127B.AE556CCD@pdx.informix.com>,
Stephen Hemminger <sch@pdx.informix.com> wrote:
>
> Some of this is fixed in 7.3.
> The trick is to bring server up with the environment variable
> CDRBLOCKOUT set (any value will do). Then do the dbexport, then
> restart server without environment set.
>
> example:
> % onmode -yk # shutdown server> % CDRBLOCKOUT=on oninit -iy # start server
> % dbexport
> % onmode -yk
> % oninit -iy>
> Note: any transactions that happen while server is running with
> CDRBLOCKOUT will not be replicated!
>
What if I temporarily suspend the replicate before exporting?
I'm running Primary/Target by the way
and the target database is the one I will dbexport.
Would the primary server(s) send their data
after I remove the CDRBLOCKOUT Environment variable,
bounce the Engine and then resume the replicate?
Thanks again,
Zandy
-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/ Now offering spam-free web-based newsreading
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.