DB2 - Problem description
Problem IC87593 | Status: Closed |
DATABASE RESTORE COULD FAIL IN PURESCALE IF STORAGE PATH MOUNTS ARE NESTED ON NON-GPFS FILE SYSTEMS | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
In a scenario where GPFS file systems have been mounted on a sub-path of a storage path a database restore could fail during attempts to create mount resources because the storage path appears to be on a non-GPFS path. It is acceptable and supported to have a storage path point to a non-GPFS file system as long as the expanded form of the storage path (/<storage_path>/<instance>/NODE####) is a GPFS mount point. Database level restore does not recognize this configuration and fails to add proper resource mounts causing the restore to fail. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * See Error Description * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 for Linux, UNIX, and Windows version 10.1 Fix * * Pack 2 * **************************************************************** | |
Local Fix: | |
Do not use nested mount points. If nested mount points are used do so at the base storage path level and not on the expanded form. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in DB2 for Linux, UNIX, and Windows version 10.1 Fix Pack 2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.10.2012 16.12.2012 16.12.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.2 | |
10.5.0.2 |