The “compare using” errors out with “Parse error message : Configuration specification not complete; must include source, target and route” as the following entries in the compare server log show:
desvr 2018-03-20 14:42:47.131985 27108 776331152 001: Input line: owner.source_table1 owner.target_table1
desvr 2018-03-20 14:42:47.131985 27108 776331152 001: Job ID : 3
desvr 2018-03-20 14:42:47.131985 27108 776331152 001: Source Data : ORA11GR2
desvr 2018-03-20 14:42:47.131985 27108 776331152 001: Parse error message : Configuration specification not complete; must include source, target and route
desvr 2018-03-20 14:42:47.131985 27108 776331152 001: Source Table: "owner"."table1"
desvr 2018-03-20 14:42:47.131985 27108 776331152 001: Target Table: "owner"."table1"
desvr 2018-03-20 14:42:47.131985 27108 776331152 001: Target Route: Not_Available
desvr 2018-03-20 14:42:47.131985 27108 776331152 001: Status : Error
The problem occurs when source and target SIDs have same value but different case (upper/ lower) and when the file used contains no datasource and target route spec. Normally it should work as the file (synchronization routing file) need not contain these but the command errors out in specific occurrences where the source and target SIDs have differing cases (upper or lower) and the file used in such “compare using” or “repair using” does not use the complete syntax for a config file but only uses syntax like:
owner.source_table1 owner.target_table1
owner.source_table2 owner.target_table2
Instead of a syntax similar to a config file like:
datasource:o.SOURCE_SID
owner.source_table1 owner.target_table1 target_system@o.target_sid
owner.source_table2 owner.target_table2 target_system@o.target_sid
To get around the issue, use the full syntax of a config file for the file that contains the entries for the tables to be sync’d when running “compare using” or “repair using”
