home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC66280 Status: Geschlossen

ARCHIVE LOG DOES NOT WORK USING TSM PASSWORD PROMPT

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
In version 9.5 log archive works correctly with the following 
configuration for log archiving, using on dsm.sys password 
prompt option: 
 
 First log archive method                 (LOGARCHMETH1) = TSM 
 TSM management class                    (TSM_MGMTCLASS) = 
 TSM node name                            (TSM_NODENAME) = 
 TSM owner                                   (TSM_OWNER) = 
 TSM password                             (TSM_PASSWORD) = ***** 
 
In v9.7 the same exact configuration fails. 
 
Archive log will only work if we udpate TSM_PASSWORD and then 
 
LOARCHMETH1 (either on that order or at the same time) with the 
database online. 
Once the database is restarted the log archiving will fail until 
the configuration is changed again.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In version 9.5 log archive works correctly with the          * 
* following configuration for log archiving, using on dsm.sys  * 
* password prompt option:                                      * 
*                                                              * 
*  First log archive method                 (LOGARCHMETH1) =   * 
* TSM                                                          * 
*  TSM management class                    (TSM_MGMTCLASS) =   * 
*  TSM node name                            (TSM_NODENAME) =   * 
*  TSM owner                                   (TSM_OWNER) =   * 
*  TSM password                             (TSM_PASSWORD) =   * 
* *****                                                        * 
*                                                              * 
* In v9.7 the same exact configuration fails.                  * 
*                                                              * 
* Archive log will only workwe udpate TSM_PASSWORD and then    * 
* LOARCHMETH1 (either on that order or at the same time) wiht  * 
* the database online.                                         * 
* Once the database is restarted the log archiving will fail   * 
* until the configuration is changed again.                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 Fix Pack 2                            * 
****************************************************************
Local-Fix:
Use password generate option or update the database 
configuration after a restart with the right settings again: 
Update db cfg for <database alias> using TSM_PASSWORD 
<password> LOGARCHMETH1 TSM<:TSM options> 
 
Note that it is important that both parameters are updated at 
the same time or that the order of update is first TSM_PASSWORD 
then LOGARCHMETH1
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in Version 9.7 Fix Pack 2
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC66507 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
12.02.2010
22.04.2010
22.04.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList