|
Problem IC66280
|
Status: Closed |
ARCHIVE LOG DOES NOT WORK USING TSM PASSWORD PROMPT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| 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 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 Summary: |
****************************************************************
* 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 |
| available fix packs: |
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
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66507
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.02.2010
22.04.2010
22.04.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
