The command copy table results in "Table <owner>.<tablename> is not in replication, use force option to copy" (4297695)

The command copy table results in "Table . is not in replication, use force option to copy"

Copy command errors with "Table <owner>.<tablename> is not in replication, use force option to copy"

1.The active config file does NOT have the table specified in the copy command and the copy/append command was used WITHOUT force option.

For example, the copy command was issued for TABLE2 but the config file does not contain TABLE2 and the following copy command is used sp_ctrl (source_server:port_num)>copy owner.table2 to owner.table2 attarget_server@o.target_SID

2. If the SID is in a different case to the SID used in the copy command.
Example: If the SID mentioned in the config file is in upper case, as below.
"MILIESCU"."CONTRIBADR" "MILIESCU"."CONTRIBADR" mfpm2:orap1_codfisc@o.MFP_REPLIC
and in if the copy command is run as
copy miliescu.contribadr to saiven.contribadr at mfpm2:orap1_miliescu@o.mfp_replic

1.The copy table can be used to sync target tables with the help of source table even if the table is not replicating. It only needs a configuration to be active between the source and target. It uses Oracles Export/Import utility to sync the table. However, in this case the force option must be specified.

For example:
sp_ctrl (source_server:port_num)> copy owner.table2 to owner.table2 attarget_server@o.target_SIDforce

2. Make sure the SID is in the same case as the config file.

The Reference Guide also covers in the section titled
Other considerations for using copy/append:

When using the copy/append command for a table not in a known replication route
the user must employ the force option. To employ copy/append on objects not in
replication the user must employ the force option.