MOPTION
This functionality is controlled by several MOPTIONs. These must be updated directly in the database. There is intentionally no UI to do this because it should not be used lightly.
MOPTION 86 OPTCHAR value controls where the external files will be stored.
MOPTION 13002 OPTINT value controls the number of retries when trying to read the external files.
MOPTION 13003 OPTINT value controls the number of milliseconds between retries when retrying to read the external files.
Troubleshooting
If reads/writes from/to the external file have issues, these are some messages you might see in the logger:
WriteSqlBinaryData() failed
File buffer not set.
Failed (%ld) to open file '%s' for writing.
Failed (%ld) to write binary header to file '%s'.
Failed (%ld) to set binary file pointer in '%s'.
Failed (%ld) to write binary data to file '%s'.
Failed (%ld) to delete file '%s'.
Failed (%ld) to create directory '%s'.
Failed to generate binary file name.
Failed to generate binary file path.
Failed (%ld) to open file '%s' for reading.
Failed (%ld) to read binary file header from '%s'.
Invalid binary file header in '%s'.
Binary header had an invalid checksum in '%s'
Binary header checksum in '%s' did not match the database.
Binary file id in '%s' did not match the database.
Failed to compare binary file id for '%s'.
Failed (%ld) to set binary file pointer in '%s'.
Binary file buffer too small.
Failed (%ld) to read binary data from '%s'.
Base path to binary files too long.
Failed to generate binary directory path.
Binary file path too long.
Binary header had an invalid checksum.
Invalid binary file header.
Failed to generate binary file unique id.
Failed to generate binary directory path.
Binary file path too long.
Binary file base directory not set.
Binary folder name too long.
