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

SQLCODE -1229 CONTINOUSLY WRITTEN IN DB2DIAG.LOG AFTER NODE FAILURE

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
The db2ctrld background agent will poll resource usage every few
seconds across the cluster. If one of these polling requests ran
into a node failure, a -1229 error will be written in
db2diag.log. The failure was resolved, but the sqlca in the db
controller may still have the -1229 and continuously write the
error in db2diag.log.

2021-01-14-02.20.45.220085-300 E2946E951            LEVEL:
Severe
PID     : 95099                TID : 17628080828768 PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000           DB   :
APPHDL  :                      APPID:
AUTHID  :                      HOSTNAME:
EDUID   : 269                  EDUNAME: db2dbctrld () 0
FUNCTION: DB2 UDB, base sys utilities, sqleMergeSqlca, probe:20
DATA #1 : String, 63 bytes
Remote node failure for request 80000004 detected by local node
DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1229   sqlerrml: 0
 sqlerrmc:
 sqlerrp : SQLRR06F
 sqlerrd : (1) 0x81580016      (2) 0x00000016      (3)
0x00000000
           (4) 0x00000000      (5) 0xFFFFFB50      (6)
0x00000000
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)

           (7)      (8)      (9)      (10)        (11)
 sqlstate:
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.5.6                                            *
****************************************************************
Local Fix:
restart the database
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.5.6                                            *
****************************************************************
Comment
Upgrade to 11.5.6
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.02.2021
11.06.2021
11.06.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)