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.
CDR_DBSPACE setup on existing ER environment
Answered: amber (hollow confidence) — Only one reply, from someone who had not tried it, suggesting dumping the catalog with cdr list catalog, dropping syscdr and rebuilding; it also says the replicate rebuild is not avoided.
💣 This thread may describe something risky to do carelessly
Advice to drop the syscdr database of a running Enterprise Replication environment is an untested, unsupported-style procedure that can break replication.
drop syscdrcdr list catalog -a
Advisory only — not a substitute for testing in a non-production environment first.
Alexandre Marini — source: IBM Community (ConnectedCommunity.org) Informix forum
Hi, all.
I already have a running ER without
CDR_DBSPACE set.As per the documentation and technotes, the only way to set CDR_DBSPACE is setting it to desired dbspace, restart the engine, and create all the data replication definitions.
My actual environment is very large so I want to avoid the large process of replicates definitons.
Would it be possible to workaround this exporting the syscdr and importing it, just stopping and starting ER in between? Somebody already did this way?
Thanks a lot, happy Easter!!!
------------------------------
Alexandre Marini
------------------------------
#Informix
↪ replying to Alexandre Marini
Paul Watson — source: IBM Community (ConnectedCommunity.org) Informix forum
Not tried that approach but cdr list catalog –a to file, drop syscdr, and use the catalog to rebuild will/did/should work. But that will not avoid the rebuilds
Cheers
Paul
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.