DB2 FOR LUW / DB2FORLUW / A50 - DB2

When user calls MON_GET_HADR() monitor function after upgrading 
from fix packs prior to v105fp4 to v105fp4, without running 
db2updv105, they will get a trap as following: 
 
On member 0 I call the table function mon_get_hadr and it 
crashes my member.  An FODC trap file is generated. 
 
 db2inst1> db2 "select * from table(mon_get_hadr(-2)) as t" 
SQL1224N  The database manager is not able to accept new 
requests, has 
terminated all requests in progress, or has terminated the 
specified request 
because of an error or a forced interrupt.  SQLSTATE=55032 
 
 
From the trap file: 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x0900000000C3FF9C 
monFormatHadrInfo__FPCcP13sqlrwHadrInfoR14hadrParametersUiP5sqlc 
a + 0x69C 
0x0900000000C3F3AC monGetHadr + 0x72C 
0x090000000FDACF7C sqloInvokeFnArgs + 0x6338 
Stack traceback unavailable. 
</StackTrace> 
 
 
db2inst1> db2level 
DB21085I  This instance or install (instance name, where 
applicable: "db2inst1") 
uses "64" bits and DB2 code release "SQL10054" with level 
identifier 
"0605010E". 
Informational tokens are "DB2 v10.5.0.4", "s140813", "IP23616", 
and Fix Pack 
"4". 
Product is installed at "/opt/IBM/db2/V10.5_1". 
 
db2diag.log, FODC files, and db2trc have been copied to 
/TMP/test/HADR and attached to this defect.

**************************************************************** 
* USERS AFFECTED:                                              * 
* MON_GET_HADR CRASHES MEMBER                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* First fixed in fix pack 10.5 fp 5                            * 
****************************************************************

N/A

First fixed in fix pack 10.5 fp 5

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

03.09.2014
09.03.2015
09.03.2015