-
Title
The "activate config" results in 'Encountered errors parsing the configuration file. Type "verif -
Description
When activating a config file, the following errors are observed:
sp_ctrl > activate config <config_name>
Encountered errors parsing the configuration file. Type verify config <config_name> for details.
When issuing verify config to get more details on the errors, the errors may show up or the command may direct the user to the $SP_SYS_VARDIR/temp directory to view the errors encountered. Here are two screen shots:
A.The config file and/or error listing is very small:
sp_ctrl >activate config <config_name>
Encountered errors parsing the configuration file. Type verify config <config_name> for details.
sp_ctrl > verify config <config_name>
Datasource:o.sourceSID
user2.src_test1 () user2.src_test1target_server@o.targetSID
Error --> Syntax error in vertical partitioning column list
USER2.SRC_TEST2(C1) USER2.SRC_TEST2 Horizontally partitioned using SRC_TEST
1 error found while verifying config errors
Or
B.The config file and/or errors encountered is a very long list:
sp_ctrl > verify config <config_name>
Verified config file too large to display
View detailed config in $SP_SYS_VARDIR/temp/<config_name>
When the file $SP_SYS_VARDIR/temp/<config_name> is viewed, the following errors are observed in it:
.
2287: owner.source_table owner.target_tabletarget_server@o.targetSID
Error --> Source may not be replicated because it is neither a table nor a sequence -
Cause
There is an error in the config file.
-
Resolution
This new functionality in Shareplex 7.0 and up directs the users to use the verify config command to look for errors that caused the earlier attempt to activate a config file to fail. Another way to do it is to view the file listed in the screen shot. Typically the file containing errors and displayed in the screen shot of failed activation is located in $SP_SYS_VARDIR/temp/<config_name>. If the listing of the errors is very large, the command may direct the user to view a version of the config file containing the errors and located in $SP_SYS_VARDIR/temp/<config_name> as mentioned above. It may sometimes make it easy for the user to find the errors in a file as well besides displayed in the screen shot of the failed activation.