suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT27170 Status: Closed

REMOVE SERVICE PASSWORD REQUIREMENTS FOR DB2TRC ON -DEBUG
DB2.SQLCC.SQLCCTCPCONNMGR_CHILD.115 -SUSPEND COMMAND

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The following db2trc command has been used to suspend the influx
of incoming connections during maintenance windows and starting
from db2 v10.5 FP9 and db2 v11.1 Mod2 FP2, a service password
requirement
has been added to this same command due to a security
vulnerability fix which serves no purpose:

db2trc on -debug DB2.SQLCC.sqlcctcpconnmgr_child.115 -suspend

The customers using this technique, are unable to use it once
upgraded to db2 v11.1 Mod2 FP2 or db2 v10.5 FP9 and giving
service pass every
time they need to use it, make it hard and inefficient.

This APAR will remove the service password requirement for the
above stated db2trc command.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 10.5 Fix Pack 11 or higher                    *
****************************************************************
Local Fix:
As a workaround, request a service password from db2 support.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.12.2018
25.02.2020
25.02.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)