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

DB2 MAY PANIC WHILE RUNNING A QUERY DUE TO A MEMORY CORRUPTION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
A DB2 query may panic an instance in sqlrlgua function call due
to an incorrect memory assignment if it references an invalid
view.

During when the invalid view is being regenerated, it may cause
a panic with the following function calls seen in the stack:

0        pthread_kill
1        _p_raise
2        raise
3        abort
4        abort@glue78D
5        sqloExitEDU
6        sqle_panic
7        sqloCrashOnCriticalMemoryValidationFailure
8        SQLO_MEM_POOL::diagnoseMemoryCorruptionAndCrash
9        SQLO_MEM_POOL::diagnoseMemoryCorruptionAndCrash
10
.MemTreePut.fdpr.clone.3__13SQLO_MEM_POOLFP8SMemNodeUlP17SqloChu
nkSubgroup
11       sqlofmblkEx
12       sqlrlgua
13       sqlnn_auth_check
14       sqlnq_view_finish_qgm
15       sqlnq_ddl_create_view_end
16       sqlnn_regen_view
17       sqlrl_regen_view
...
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* See SYSROUTE APARs to see where this APAR is addressed       *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.10.2016
09.05.2017
09.05.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)