|
Problem IT26821
|
Status: Closed |
SPECTRUM PROTECT SNAPSHOT DB2 STANDBY DATABASE NAMES LONGER THAN 6 CHARS ENDS WITH AN ERROR FMM6825E
|
| product: |
FLSHCPY DB2 AGE / 5608AC6DB / 81A - DB2 |
| Problem description: |
When Spectrum Protect Snapshot for DB2 performs a DB2 standby
backup operation for databases with names that longer than 6
chars it ends
with an FMM6825E SQL1000N error indicating it is not a valid
database alias name.
$ ./fcmcli -f backup_db2standby
IBM Spectrum Protect Snapshot offload agent ...
FMM6808I The production database 'ABCDEFG1' will be cataloged.
FMM6825E A DB2 API call failed with the following error:
---- error report ----
app. message = catalog db
line = 523
file = esd-db2ctl.cpp
SQLCODE = -1000
SQL1000N "R_ABCDEFG1" is not a valid database alias name.
FMM6809E Unable to catalog production database 'ABCDEFG1' as
'R_ABCDEFG1'.
IBM Spectrum Protect Versions Affected:
All versions on all platforms.
Customer/L2 Diagnostics :
The 'DB2 list db directory' shows database name with more than
six characters,
> db2 list db directory
System Database Directory
Number of entries in the directory = 2
Database 1 entry:
Database alias = ABCDE1
Database name = ABCDEFG1
Local database directory = /db2/ABCDEFG1
Database 2 entry:
Database alias = ABCDEFG1
Database name = ABCDEFG1
Local database directory = /db2/ABCDEFG1
Initial Impact: Medium |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of IBM Tivoli Storage FlashCopy Manager for Unix/Linux *
* all versions on all supported platforms and users of IBM *
* Spectrum Protect Snapshot for Unix/Linux versions up to *
* 8.1.4 on all supported platforms when backing up a DB2 *
* standby database with a database name longer than 6 *
* characters. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See error description *
****************************************************************
* RECOMMENDATION: *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.11.2018
17.12.2018
17.12.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
