The article has been updated successfully.SOD gives me a 'config file changed' error
Q:I have been trying to run my xml file to extract data from IRIS_DataCenter and whenever I run SOD by typing
sod -f name.xml
this error message shows up:
Your config file has changed since your last run. It may not be advisable to continue this SOD run.
All hope abandon, ye who enter in!
Do you happen to know what could cause this problem?
A:
SOD is saying that the recipe being used in the current run is different from the one in the database that already exists. In general, SOD is supposed to be able to be restarted after a stoppage and pick back up where it left off. However, if the user switches to a new recipe without cleaning up the old database, it is often a mistake, and so SOD issues a warning.
The fix is to simply delete the SodDb directory before restarting SOD.
If you really want to continue the old sod run, but using the new recipe, you can force that with the "--replace-recipe" argument. This will replace the recipe in the db and start processing. This is really only used for really big, long lived sod runs where starting over at the beginning is not an option.
Related Articles
No related articles were found.Attachments
No attachments were found.Visitor Comments
Article Details
Last Updated
1st of July, 2011
