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 IT28884 Status: Geschlossen

MEMORY LEAK IN REGEX FUNCTION

Produkt:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problembeschreibung:
A query using a REGEXP built in function can potentially produce
a memory leak.

Using a command like this:

db2pd -db dbname -memblocks appl 20 sort | more

You might see a the total size growing for a function inside
sqlri_regexp.C like this:

Memory blocks sorted by size for appshrh pool: (PoolID: 20,
SecondID: 0, PoolAdd
r: 0x00007F0C3E3804C0)
PoolID     PoolName   TotalSize(Bytes)     TotalCount LOC   File
20         appshrh    1115552768           8536       1526
sqlri_regexp.C
20         appshrh    557776384            8536       1539
sqlri_regexp.C
20         appshrh    956032               8536       1482
sqlri_regexp.C


This can lead to an SQL0973N error where the database has run
out of application heap.
Problem-Zusammenfassung:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 v11.1 Fixpack 5                               *
****************************************************************
Local-Fix:
N/A
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.04.2019
23.02.2020
23.02.2020
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version