RE: Bi-Directional replication
- From: "Yong Huang" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "yong321" for DMARC)
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 28 Sep 2016 15:04:20 +0000 (UTC)
- Don't use Table-based sequences (e.g. for a no-gap sequence): you can't
have no-gap sequences.
- If you are using SEQUENCEs, don't replicate them but ensure they can't
produce the same value in each DB.
...
Since sequences pose a great challenge, maybe GUID as given by the sys_guid()
function is a good option? Theoretically, the raw values from this function
will never be repeated by any database. Of course this won't solve the problem
that the same record (same from the business point of view) may be inserted
twice.
Instead of bi-directional replication, if budget is not an issue and the two
data centers are not too far apart, say less than 100 km, extended RAC can also
be considered.
Yong Huang
--
//www.freelists.org/webpage/oracle-l
Other related posts:
