DB2 - Problembeschreibung
Problem IT27786 | Status: Geschlossen |
BKI9206E UNABLE TO USE XYZ WHEN EXPECTING "S1234567.LOG" ERP DB2 BACKOM QUERY OR RESTORE MIGHT FAIL FOR DB NAMES WITH "_" | |
Produkt: | |
DP-MY SAP W/DB2 / 5698ERPD2 / 71A - DB2 | |
Problembeschreibung: | |
When querying or retrieving backups taken with IBM Spectrum Protect for Enterprise Resource Planning Data Protection for SAP for DB2, the utility backom may fail, if the database name contains an underscore "_" character. Customer/L2 diagnostics: ------------------------ 'backom -c q_log' or 'backom -c q_all' will put out this error message to the console: BKI9206E: Additional support information: Unable to use XYZ when expecting "S1234567.LOG" or "1234567" at tdpadutl-logsequencenum.cpp(58). Product versions affected: IBM Spectrum Protect for Enterprise Resource Planning Data Protection for SAP for DB2 Versions 7.1 and later Initial impact: Medium Additional keywords: ISP SP TSM TDP DP underscore TS001522404 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users of IBM Spectrum Protect for Enterprise Resource * * Planning Data Protection for SAP for Db2 versions up to * * 8.1.4.0 on all supported platforms having database name * * containing an underscore "_" character. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Apply fixing level when available. This problem is currently * * projected to be fixed in level 8.1.4.1 Note that this * * information is subject to change at the discretion of IBM. * **************************************************************** Backup functionality is not affected by this problem. | |
Local-Fix: | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 16.01.2019 29.04.2019 29.04.2019 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version |