There could be many reasons for this error.
a. Incorrect use of "force" option in copy.
b. Incorrect SID OR Table Name on target.
For a.
The "force" option in copy can be used in the following circumstances:
1. To sync a target table when the source/target pair is already in replication and allow the copy process to sync the target table without any regard to replication.
2. To sync a target table when the source/target pair is not in replication. In this case, the copy will use Oracle Export/Import to sync the target table but since there is no replication between source and target tables, the tables may or may not be in sync for long depending on the user activity on the source table.
In this case the problem encountered is due to the fact that the "force" option is used on a source/target pair where the source table is replicating to a different target table, and not to the one specified in the copy command. So the copy will not work on that source/target pair. This is not the correct way to use copy/sync commands with force option.
b.
1. Correct the entries in the copy command If the SID or the Table Name is wrong.
2. Verify SID case type it should be same either in small case or in Capital case in connection.yaml file in both source and target site.
