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 IT34156 Status: Closed

ALLOW FMP POOLING FOR SPECIFIC USER IDS

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
It was observed on systems with QRep enabled, QRep uses a
different user id than the Fenced user id and that makes FMP
infrastructure not to pool the agents which drives delays in the
QRep user id processing DML statements. The delays get more
noticeable when the Apply side is applying smaller transactions
on large DPF systems. On a customer system, it was observed, the
set up of FMP processes to read a file by EXTBL interface took
anywhere from 1 - 1.5 seconds.

This fix will enable pooling of FMP for specific user ids. The
userid will be provided to the engine via a regvar.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.5.5.0 or higher                            *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.5.5.0 or higher                            *
****************************************************************
Comment
Upgrade to Db2 11.5.5.0 or higher
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.09.2020
20.11.2020
20.11.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)