|
Problem IT20743
|
Status: Closed |
IBM SPECTRUM PROTECT SNAPSHOT CLONE OPERATION FAILS WITH DBT2103N IF PATH DOES NOT CONTAIN THE DB NAME IN UPPER CASE.
|
| product: |
FLSHCPY DB2 AGE / 5608AC6DB / 81A - DB2 |
| Problem description: |
When performing a cloning operation with the IBM Spectrum
Protect Snapshot for DB2 in an environment that does not contain
the database name in upper case for the path to the data/logs,
the processing may fail with the error:
DBT2103N Directory
"/db2/fcmprdlogs/fcmcln/SQLOGDIR/NODE0000/LOGSTREAM0000/" does
not exist
In this example the production data is located on the
/db2/fcmprdlogs filesystem within the
/fcmprd/SQLOGDIR/NODE0000/... directory
During the relocate processing the relocate_cfg_file* is updated
with the paths for the data/logs for the clone. Depending on the
path that is used for this non-default configuration it is
possible that the correct location will be created on the file
system but the path within a configuration file or this relocate
will not be updated appropriately. In this example the /fcmprd/
subdirectory is updated to /fcmcln/ but the file system with
name "/db2/fcmprdlogs" is not. This results in DB2 looking for
the logs within
"/db2/fcmprdlogs/fcmcln/SQLOGDIR/NODE0000/LOGSTREAM0000/, but
they are actually in
/db2/fcmclnlogs/fcmcln/SQLOGDIR/NODE0000/LOGSTREAM0000/. This
can affect both the data and the log directory paths depending
on how they are configured
IBM Spectrum Protect Versions Affected: all
IBM Spectrum Protect Snapshot for DB2
Initial Impact: High
Additional Keywords: TSM, Tivoli, Storage, Manager, TDP, FCM |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Spectrum Protect Snapshot for DB2 all versions up *
* to 8.1.0 and users of Tivoli Storage FlashCopy Manager for *
* DB2 all versions performing a database cloning. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See ERROR DESCRIPTION *
****************************************************************
* RECOMMENDATION: *
* Apply fixing level when available or implement a workarround *
* described in the "Local Fix" section. This problem is *
* currently projected to be fixed in level 8.1.0.2. Note that *
* this information is subject to change at the discretion of *
* IBM. *
**************************************************************** |
| Local Fix: |
Use database name with upper case in all paths where database
data and log files are located. For example file system name
where DB2 database saves log files may be similar to:
/db2/PRD/db2prd/SQLOGDIR/NODE0000. |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.05.2017
09.08.2017
09.08.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
