The following errors are observed when activating a config file:
sp_ctrl (source_server:9100)> show log reverse
Info 2018-02-15 16:02:31.179189 18826 3744170512 Activation exited with code=1, pid = 18859 (activating datasource o.source_SID)
Error 2018-02-15 16:02:31.177075 18859 2562532816 Compile of "sqltargetconfig" for database o.source_SID failed: No valid tables were found in the config.
Warning 2018-02-15 16:02:31.176660 18859 2562532816 Activation: Invalid route, cannot parse. Skipping (owner.source_table) (activating datasource o.source_SID) [module ocf]
Notice 2018-02-15 16:02:31.174870 18859 2562532816 Activation: Oracle compatible parameter='11.2.0.0.0' (activating datasource o.source_SID) [module ocf]
Error 2018-02-15 16:02:30.043256 18859 2562532816 Activation: Error 'Error getting address for server_name: Name or service not known' getting id for server_name (activating datasource o.source_SID) [module rim]
Notice 2018-02-15 16:02:30.040882 18859 2562532816 Activation: Replicating according to target compatibility of "9.1.0" (activating datasource o.source_SID) [module sys]
Notice 2018-02-15 16:02:30.040374 18859 2562532816 Activation: Replicating according to target compatibility of "9.1.0" (activating datasource o.source_SID) [module sys]
Info 2018-02-15 16:02:29.924883 18859 3744170512 Activation launched, pid = 18859 (activating datasource o.source_SID)
Here is the config file:
sp_ctrl (source_server:9100)> view config sqltargetconfig
datasource:o.source_SID
owner.source_table owner.target_table target_server@r.target_SID
Carry out one of the following:
1. Check to see if any network issues are causing this. Such issues arise out of incorrect entries in /etc/hosts, firewall, etc. Correct the problems and activate again.
2. Another way to get around is to use the IP address of the target subject to the DNS able to resolve it. Edit the config file to use the IP address of target instead of the target server name. Then activate afresh.
For example, edit the target route as below (where the target IP is nn.n.nn.nnn):
datasource:o.source_SID
owner.source_table owner.target_table nn.n.nn.nnn@r.target_SID
3. It can also be due to a typo in the target route for entry ‘server_name’. The resolution involves editing the config file and activating again.
