15.5.2.1.1 Exceptions

The DIFFERENCES procedure may raise the following exceptions:

15.5.2.1.2 Restrictions

Note the following restrictions on calling the DIFFERENCES procedure:

• You must create tables missing_rows_sname.missing_rows_oname1 and missing_rows_sname.missing_rows_oname2 before running this procedure.

• The columns in table missing_rows_oname1 must match the columns passed to column_list or array_columns exactly.

• The replication group to which the tables belong must be quiesced.

15.5.2.1.3 Example

For an example of how to use the DIFFERENCES procedure, see the example under the RECTIFY procedure.

15.5.2.2.1 Exceptions

The RECTIFY procedure may raise the following exceptions:

15.5.2.2.2 Restrictions

Note the following restrictions on calling RECTIFY:

• The DIFFERENCES procedure must have been run prior to running RECTIFY.

• The replication group to which the tables belong should still be quiesced.

• If duplicate rows exist in the reference table but not the comparison table they will be inserted into the comparison table.

• If duplicate rows exist in the comparison table but not the reference table they will be deleted from the comparison table.

15.5.2.2.3 Example

Assume that the table SPROCKET.DAILY_SALES is replicated between sites D7CA.BIGWHEEL.COM (the references site) and D7NY.BIGWHEEL.COM (the comparison site). The following table shows the description of the DAILY_SALES table.

The following steps executed at D7CA.BIGWHEEL.COM would populate the tables missing_rows_daily_sales and missing_location_daily_sales and rectify these differences. These steps should be executed under the designated replication administrator account. Note that storage parameters are left out of the example for the sake of brevity and clarity, but they should be included whenever you run the DBMS_RECTIFIER_DIFF.DIFFERENCES procedure.

	CREATE TABLE missing_rows_daily_sales (
	sales_id	NUMBER(9),
	distributor_id	NUMBER(6),
	product_id	NUMBER(9),
	units		NUMBER(9,2)
	);

	CREATE TABLE missing_location_daily_sales (
	present	VARCHAR2(128),
	absent	VARCHAR2(128),
	r_id	ROWID
	);

	BEGIN
		DBMS_REPCAT.SUSPEND_MASTER_ACTIVITY('SPROCKET');

		DBMS_RECTIFIER_DIFF.DIFFERENCES( -
			sname1			=> 'SPROCKET', 
			oname1			=> 'DAILY_SALES', 
			reference_site		=> 'D7CA.BIGWHEEL.COM', 
			sname2			=> 'SPROCKET', 
			oname2			=> 'SPROCKET', 
			comparison_site		=> 'D7NY.BIGWHEEL.COM', 
			where_clause		=> NULL, 
			column_list		=> 'SALES_ID,DISTRIBUTOR_ID,PRODUCT_		            							  ID,UNITS', 
			missing_rows_sname	=> 'REPADMIN', 
			missing_rows_oname1	=> 'MISSING_ROWS_DAILY_SALES', 
			missing_rows_oname2	=> 'MISSING_LOCATIONS_DAILY_SALES ,
			missing_rows_site	=> 'D7CA.BIGWHEEL.COM', 
			max_missing		=> 500, 
			comit_rows		=> 100);

		DBMS_RECTIFIER_DIFF.RECTIFY( -
			sname1			=> 'SPROCKET', 
			oname1			=> 'DAILY_SALES', 
			reference_site		=> 'D7CA.BIGWHEEL.COM', 
			sname2			=> 'SPROCKET', 
			oname2			=> 'SPROCKET', 
			comparison_site		=> 'D7NY.BIGWHEEL.COM', 
						       ID,UNITS', 
			missing_rows_sname	=> 'REPADMIN', 
			missing_rows_oname1	=> 'MISSING_ROWS_DAILY_SALES', 
			missing_rows_oname2	=> 'MISSING_LOCATIONS_DAILY_SALES -
			missing_rows_site	=> 'D7CA.BIGWHEEL.COM', 
			comit_rows		=> 100);
	END;

TIP: These procedures can take a long time to run. If the volume of data is significant, it will probably be easier for you to simply reinstantiate the comparison table by importing an export of the reference table.