failarchpath - Failover log archive path configuration parameter
This parameter specifies a path to which the Db2® database system will try to archive log files if the log files cannot be archived to either the primary or the secondary (if set) archive destinations because of a media problem affecting those destinations. This specified path must reference a disk.
- Configuration type
- Database
- Applies to
-
- Database server with local and remote clients
- Client
- Database server with local clients
- Partitioned database server with local and remote clients
- Parameter type
- Configurable Online
- Default [range]
- Null [ ]
If there are log files in the path specified by the current value of failarchpath, any updates to failarchpath will not take effect immediately. Instead, the update will take effect when all applications disconnect.
When using Advanced Log Space Management (ALSM), it is recommended that you set a failarchpath value to allow archiving to take place if the primary log archive target is malfunctioning. This precaution helps prevent the extraction scan from going idle.
It is recommended the failarchpath be on a different file system then the main archive logpath to ensure the same media failure does not affect both paths.
Updates to this specific database configuration is restricted to one change per activation cycle. To proceed with further updates, activate or restart to reset the configuration state.
You may encounter the following message if an update is attempted before reactivation:
SQL5160N Updates to "failarchpath" are currently disallowed. An operation is currently pending for this parameter. All applications must disconnect from the database and the database must be reactivated before new updates to this parameter can be applied.