Error "source table <name> is not replicating to target table <name>" when running co (4330746)

Error received on the source when running compare:

"05/20/06 22:30 Notice: Source table "PROD1"."HUB_TRANSACTIONTYPE" is not replicating to target table "PROD1"."HUB_TRANSACTIONTYPE" [sp_cnc/10471]
05/20/06 22:28 Process exited sp_desvr (for HUB) [pid = 18104] - exit(0)
05/20/06 22:28 Child process completed"

See Resolution.

CAUSE:

1. The table is not in replication.

2. Either the source or the target table does not exist in database.

3. There could be network errors such as The Target hostname had not been set in the /etc/hosts file on Source. (Refer to Solution 14064 - "Error: '004: Error: Invalid host name - "unknown" causing Compare to fail.":
https://support.quest.com/SUPPORT/index?page=solution&id=SOL14064).

4. A typographical error in the routing info in the config file.

5. Specifying the wrong hostname in the compare command. For example using alias for the hostname in the config file whereas specifying the physical hostname in the compare command.

6. New tables were added to the config file and the tables are activating successfully whereas the compare command gives the error above as a file named conf.xxxx located in /vardir/db directory is not updated to reflect the fact that these new tables are replicating. (NOTE: xxxx denotes the activation ID).

7. For Shareplex 4.5 or 4.0, when running compare config, if using vertical partitioning and if the entry for the table is more than 2300 bytes, Shareplex would break every 2300 odd byte to arrive at a table name and determine that it is not replicating to target table.

RESOLUTION:

The following can be done to correct the above problems:

1. Before issuing the compare command, one may want to make a copy of the currently active config file, add the table(s) and activate the copy.

2. If the target table has been dropped, recreate it. If the source table has been dropped, recreate it, then take it out of replication and bring it back in.

3. Ensure that the Source and Target /etc/hosts files have entries for both the Source and Target hostnames and IP Addresses.

4. Correct the typographical error and run compare again.

5. Specify the same routing info in the compare command as it exists in the config file. For example, if the config file uses an alias instead of a physical host, specify the alias in the compare.

6. Make a copy of the currently active config file and activate the copy before running compare again. For some reasons the file /vardir/db/conf.xxxx did not get updated to reflect the fact that new tables have been added to replication. This will most likely update the file.

7. This bug is fixed in later release of Shareplex. One may want to avoid compare config on such tables and instead compare individual tables.