|
Problem IC91361
|
Status: Closed |
SQLCODE -1229 RECEIVED ON DB2LUSED CONTINUOSLY EVEN AFTER A LOT OF TIME HAS PASSED AFTER THE LAST NODE RECOVERY |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
In DPF systems, users may observe that the db2lused continues to
get the below error messages even after a node
recovery has completed successfully much in the past:
----------------------------------------------------------------
-------------
AUTHID : XXXXX HOSTNAME: XXXXXX
EDUID : 11053 EDUNAME: db2lused (DATABASE_NAME)
0
FUNCTION: DB2 UDB, base sys utilities, sqleMergeSqlca, probe:20
DATA #1 : String, 92 bytes
Due to node failure at node 0 received sqlcode -1229 for request
80000004 from node number 0
DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1229 sqlerrml:
49
sqlerrmc: X SRC_CODEPAGE DATABASE_NAME OS_DETAILS
DESTINATION_CODEPAGE
sqlerrp : SQLRR06A
sqlerrd : (1) 0x81580016 (2) 0x00000016 (3)
0x00000000
(4) 0x00000003 (5) 0xFFFFFB50 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
----------------------------------------------------------------
-----------
After a node failure the sqlca is set with -1229. When the node
recovery completes and returns from the corresponding functions,
the sqlca is not reset. So this -1229 from a previous node
failure gets dumped in sqleMergeSqlca and thus logged
continuously as seen above. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users below V10.1 FP3 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v10.1 FP3 or above. *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem fixed in V10.1 FP3 and above versions/fixpacks. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC91378 IC95233
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.04.2013
21.10.2013
21.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
