Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC78044 Status: Closed

SQLEMERGESQLCA() REPORTS INCORRECT NODE SENDING -1229 IF THE SENDING NODE
CANNOT BE REACHED.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
The sqleMergeSqlca() ambiguously reports the node affected when 
reporting -1229 error because the node affected cannot be 
reached.  In these cases the node reported is itself. 
 
Looking at the db2diag.log, it is implied that "node number 0" 
is the node where sqlcode -1229 is coming from. 
 
2011-07-25-16.25.54.728351-240 I115019723A467     LEVEL: Severe 
PID     : 12517520             TID  : 491852      PROC : db2sysc 
0 
INSTANCE: xxxxxx               NODE : 000         DB   : xxx 
APPHDL  : 0-36843              APPID: *N0.db2bp1.xxxxxxxxxxxx 
AUTHID  : xxxxxx 
EDUID   : 491852               EDUNAME: db2agent (xxx) 0 
FUNCTION: DB2 UDB, base sys utilities, sqleMergeSqlca, probe:20 
MESSAGE : Received sqlcode -1229 for request 80000017 from node 
number 0 
 
However, in this case, node 11 is the one having troubles.  Node 
11 is not sending -1229 because it cannot be reached. 
SqleMergeSqlca() is reporting node 0 as the one sending -1229 
but sqlca (sqlerrd 6th parameter) reports that -1229 came from 
node 11 (0xB).  Node 11 is the node that should have been 
reported by SqleMergeSqlca() as sending -1229. 
 
 
2011-07-25-16.25.54.744499-240 I115020191A834     LEVEL: Severe 
PID     : 12517520             TID  : 491852      PROC : db2sysc 
0 
INSTANCE: xxxxxx               NODE : 000         DB   : xxx 
APPHDL  : 0-36843              APPID: *N0.db2bp1.xxxxxxxxxxxx 
AUTHID  : xxxxxx 
EDUID   : 491852               EDUNAME: db2agent (xxx) 0 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
logging func, probe:0 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1229   sqlerrml: 0 
 sqlerrmc: 
 sqlerrp : SQL09072 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x0000000B 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate:
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL platforms, DPF env                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* ERROR DESCRIPTION:                                           * 
*                                                              * 
* The sqleMergeSqlca() ambiguously reports the node affected   * 
* when                                                         * 
* reporting -1229 error because the node affected cannot be    * 
*                                                              * 
* reached.  In these cases the node reported is itself.        * 
*                                                              * 
*                                                              * 
*                                                              * 
* Looking at the db2diag.log, it is implied that "node number  * 
* 0"                                                           * 
* is the node where sqlcode -1229 is coming from.              * 
*                                                              * 
*                                                              * 
*                                                              * 
* 2011-07-25-16.25.54.728351-240 I115019723A467     LEVEL:     * 
* Severe                                                       * 
* PID     : 12517520             TID  : 491852      PROC :     * 
* db2sysc                                                      * 
* 0                                                            * 
*                                                              * 
* INSTANCE: xxxxxx               NODE : 000         DB   : xxx * 
*                                                              * 
* APPHDL  : 0-36843              APPID:                        * 
* *N0.db2bp1.xxxxxxxxxxxx                                      * 
* AUTHID  : xxxxxx                                             * 
*                                                              * 
* EDUID   : 491852               EDUNAME: db2agent (xxx) 0     * 
*                                                              * 
* FUNCTION: DB2 UDB, base sys utilities, sqleMergeSqlca,       * 
* probe:20                                                     * 
* MESSAGE : Received sqlcode -1229 for request 80000017 from   * 
* node                                                         * 
* number 0                                                     * 
*                                                              * 
*                                                              * 
*                                                              * 
* However, in this case, node 11 is the one having troubles.   * 
* Node                                                         * 
* 11 is not sending -1229 because it cannot be reached.        * 
*                                                              * 
* SqleMergeSqlca() is reporting node 0 as the one sending      * 
* -1229                                                        * 
* but sqlca (sqlerrd 6th parameter) reports that -1229 came    * 
* from                                                         * 
* node 11 (0xB).  Node 11 is the node that should have been    * 
*                                                              * 
* reported by SqleMergeSqlca() as sending -1229.               * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
* 2011-07-25-16.25.54.744499-240 I115020191A834     LEVEL:     * 
* Severe                                                       * 
* PID     : 12517520             TID  : 491852      PROC :     * 
* db2sysc                                                      * 
* 0                                                            * 
*                                                              * 
* INSTANCE: xxxxxx               NODE : 000         DB   : xxx * 
*                                                              * 
* APPHDL  : 0-36843              APPID:                        * 
* *N0.db2bp1.xxxxxxxxxxxx                                      * 
* AUTHID  : xxxxxx                                             * 
*                                                              * 
* EDUID   : 491852               EDUNAME: db2agent (xxx) 0     * 
*                                                              * 
* FUNCTION: DB2 UDB, trace services, sqlt_logerr_data          * 
* (secondary                                                   * 
* logging func, probe:0                                        * 
*                                                              * 
* DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes                * 
*                                                              * 
*  sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1229           * 
* sqlerrml: 0                                                  * 
*  sqlerrmc:                                                   * 
*                                                              * 
*  sqlerrp : SQL09072                                          * 
*                                                              * 
*  sqlerrd : (1) 0x00000000      (2) 0x00000000      (3)       * 
*                                                              * 
* 0x00000000                                                   * 
*                                                              * 
*            (4) 0x00000000      (5) 0x00000000      (6)       * 
*                                                              * 
* 0x0000000B                                                   * 
*                                                              * 
*  sqlwarn : (1)      (2)      (3)      (4)        (5)         * 
* (6)                                                          * 
*            (7)      (8)      (9)      (10)        (11)       * 
*                                                              * 
*  sqlstate:                                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fix Pack 9.                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in Version 9.5 Fix Pack 9.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.08.2011
18.03.2012
19.03.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.