Handling corrupted or invalidated feeder files

If a corrupted or invalid feeder file is detected, all the saved feeders will be deleted and the server will exit with appropriate messages in the log file.

In that case, you must restart the server to reload and re-compute all of the feeders. The messages in the log will be of the form:

27660 ERROR 2010-05-14 19:10:26.455 Cognos® .Server All persistent feeder files will be deleted and server will shut down

27660 ERROR 2010-05-14 19:10:26.455 TM1® .Server Restart server to re-load database.

Feeder files are deemed "invalid" if there is a format error in the file, or if the date-time of the feeder file is older than the corresponding cube (.CUB) file which may happen if one tries to manually copy feeder or cube files from one data directory to another. When a feeder file is deemed to be invalid, a message is written to the system log file explaining the exact reason that the feeder file is deemed to be invalid. The message has the form:

ERROR 2010-05-14 19:00:22.987 TM1 .Server Invalid feeder file detected for cube "xxxx" reason: ...

This message will typically (in the case of a multi-threaded load or an error with an cube which loads early in the startup process) not be near the end of the file, but rather will be in the middle of the load sequence. Searching the message log for "ERROR" will show the error.