FileRetry.FileSpec

Network issues can cause transaction log updates to fail, which might force a Planning Analytics database shutdown. This configuration parameter specifies the directory paths of the affected log files.

This parameter is not applicable to Planning Analytics Engine.

Parameter type: optional, dynamic

By default, the Planning Analytics database shuts down when transaction log updates fail. Specifying FileRetry.FileSpec defers the database shutdown while the database attempts to reestablish a connection.

The number of retry attempts and delay between attempts is determined by FileRetry.Count and FileRetry.Delay, respectively. If the network failure persists after the specified number of retries, Planning Analytics database will self-terminate.

As of IBM® Planning Analytics Local version 2.0.3, if this setting is not specified in Planning Analytics database configuration, the retry logic is applied to all files in the logs directory only.

To turn off the retry logic, specify one of the following options in the Planning Analytics database configuration:

  • FileRetry.FileSpec="" (explicitly setting the value to the empty value)
  • FileRetry.Count=0
Use a semi-colon delimiter to specify multiple paths. For example,
  1. FileRetry.FileSpec=c:\production\model\Logs

    On a write failure, the retry logic is applied to all files in the "c:\production\model\Logs" directory and any sub-directories.

  2. FileRetry.FileSpec=c:\production\model\Logs;\\network.ibm.com\production\Logs

    On a write failure, the retry logic is applied to all files in the "c:\production\model\Logs" directory and the network share of \\network.ibm.com\production\Logs and any sub-directories.

Note: Messages are written to the server log at the WARN level when this logic is enabled.
  • Error writing to <FILENAME>, retry in progress. is written when a write operation fails and a retry attempt is in progress.
  • Error writing to <FILENAME>, retry attempt failed. is written when the retry attempt fails.