If the critical files of Db2 damage, e.g. by erroneously deletion, file system corruption Db2 will no longer be available (#usable). Since some of the critical files are permanently updated a restore of the critical files does solve the problem. A loss of (part of) the local database directory requires a complete restore of a database which means hours of outage.
Mirroring the local database directory to a different path (preferably a different file system) could make Db2 tolerant to such kind of problems. This kind of enhancement could work roughly comparable to MIRRORLOGPATH, which allows to configure a mirror path for the log files, a DB parameter like DBDIRMIRRORPATH could allow to specify a mirror path for the local database directory
Why is it useful?
|Who would benefit from this IDEA?||The measurable benefit would be a fault tolerance of Db2 regarding the loss of critical files, resulting in avoiding full database restores for customers.|
How should it work?
The proposed solution for the problem is to specify a mirror path for the local database directory.
|Priority Justification||This functionality could avoid a complete database restore (outage)|
|Customer Name||Finanz Informatik|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "firstname.lastname@example.org" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions