Certainly the most versatile and intriguing component of Oracle’s advanced replication facility is multi-master table replication. Any replicated table can be updated anywhere, and the changes will appear in all participating master sites. However, as with any sophisticated technology, you must configure multi-master replication with great care in order to avoid perils and pitfalls.
This section describes the API calls used to create and to maintain replicated tables, points out techniques to make the administration job easier, and describes some practices that will help you to avoid trouble.
The fundamental DBMS_REPCAT procedures for administering replicated tables are as follows:
Adds a uniqueness conflict resolution handler to the table.
Adds an update conflict resolution handler to the table.
Creates an empty column group.
Drops a column group.
Drops a uniqueness conflict handler.
Drops an update conflict handler.
Creates a column group and assigns columns to the group.
Specifies which columns should send their previous values to remote sites for comparison during updates and deletes.
Specifies the column(s) to use to uniquely identify records in the table.