-
Title
What is "force" option in compare -
Description
Compare has a "force" option for tables not in replication and this article delves on this option. -
Cause
General information. -
Resolution
Like copy command, the compare also allows the use of “force” option to compare tables that do not form part of replication. It is a quick way to determine if such tables are in sync. However, unlike copy that allows a cold sync of such tables, the compare only determines if they are in sync or not. Both copy and compare share one characteristics, that is, they do not take into account the changes that are currently occurring on the source table. So by the time the compare prescribes the target table as in sync, there is every likelihood that it can be out of sync by then, or in future, depending on the activity on the source table. This command is very useful if the tables are not changing and are static for the most part. Other than this, its prescription cannot be used since the state of sync of a table can change due to user activity and the fact that the table is not part of replication.
Here is a sample session of how it is used:
Here is my active config:
config1 Active o.ORA11GR2
Last Modified At: 11-Jul-17 19:35 Size: 131 Internal Name: .conf.28
sp_ctrl (alvsupu15:5438)> view config config1
datasource:o.ORA11GR2
#source tables target tables routing map
sha90.table2 sha90.table2 alvsupu16@o.ORA11GR2
I issue compare with “force” on a table that is not in replication and it succeeds:
sp_ctrl (alvsupu15:5438)> compare sha90.table1e at alvsupu16@o.ORA11GR2 force
comparing 1 of 1 objects
compare started; job id 3
sp_ctrl (alvsupu15:5438)> job status
Job ID : 3
PID : 13264
Host : alvsupu15
Started : 14-JUL-17 19:16:03
Job Type : Compare
Status : Done - 1 object completed
ID Tablename Status Time Total Rows %Co
mp Total Time
------ ------------------------------------ ---------- ---------- ---------- ---
-- ----------
1 "SHA90"."TABLE1E" Out Sync N/A 2 100 0:05