This chapter has covered the concepts needed to implement N-way replication. The provided code made it tangible. Now, what does it take to go to the next level?

Start with the conflicts. In this case we used the built-in MAXIMUM conflict resolution handler. In your case, start with the business units that you are supporting and learn the business use cases. Then drive down to the tables involved in the transactions from the uses cases. Setting up conflict resolution is implemented at the table level. But you need to think at the transaction level.

The example in this chapter is for a table. Taking this skeleton code you can move up to schema level by using the related schema-level procedure. For example, we used the following in this chapter:

Table level:

DBMS_STREAMS_ADM.ADD_TABLE_RULES
DBMS_STREAMS_ADM.ADD_TABLE_PROPAGATION_RULES
DBMS_APPLY_ADM.SET_TABLE_INSTANTIATION_SCN
DBMS_STREAMS_ADM.ADD_TABLE_RULES

by changing it to Schema level:

DBMS_STREAMS_ADM.ADD_SCHEMA_RULES
DBMS_STREAMS_ADM.ADD_SCHEMA_PROPAGATION_RULES
DBMS_APPLY_ADM.SET_SCHEMA_INSTANTIATION_SCN
DBMS_STREAMS_ADM.ADD_SCHEMA_RULES

By making minor syntax changes, you can quickly start Stream'ing at the schema level. Please refer to Chapter 4 on using Data Pump to export and import a schema.