Loads can fail if there is a problem such as a power outage which affects the connection to the database or even the environment in which GO Loader is running itself. Luckily, during loading of a set of GML, GO Loader is constantly writing logs and these logs can be used to restart a load from the point of failure.
The directory where logs are created is set in the ‘Logging’ sub-tab on the ‘Loader Configuration’ tab in GO Loader Studio. If you also have selected 'Generate log sub-directories', the latest logs are created in a time-stamped sub-directory.
When a load fails, the current status of the load is maintained in the following files;
- progress.txt,
- startList.txt,
- failedList.txt &
- pendingList.txt.
When the failure is caused by inability to access the database, GO Loader ensures the pending list and failure lists contain the full set of files to restart. This can be done in GO Loader Studio by using the 'Select List' rather than 'Select File' option and load the remaining files as normal.
If the failure included GO Loader itself , it may not have had chance to fully write the current situation to the logs. In this instance, use the information in the progress.txt and all the lists to ensure the information is consistent before restarting the load as before.

Leave a comment