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

DB2READLOG API FAILED WITH SQL2038N DUE TO CHANGING OVERFLOWLOGPATH
ONLINE

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
This problem occurs when the OVERFLOWLOGPATH database
configuration parameter is changed online while the application
using the db2ReadLog() api (such as Qrep or CDC) is running.

In particular, the problem occurs when such application is using
multiple database connections to call db2ReadLog() api, where
some of the db2ReadLog() execution is aware of the
configuration change while some other execution is not aware.

The following is an example of the db2diag.log message when
encountering this problem:


2022-04-21-20.33.53.074686+480 I1078335778E952       LEVEL:
Error
PID     : 378486               TID : 139777873536768 PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   :
SAMPLE
HOSTNAME: MYHOST1
EDUID   : 37                   EDUNAME: db2lfr.0 (SAMPLE) 0
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMOpenLog,
probe:5876
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic
Error"
          DIA8526C A fatal error occurred in data protection
services.
DATA #1 : String, 47 bytes
Retrieved extent not tracked in retrieve table.
DATA #2 : String, 49 bytes
lfrScanID / logStreamId / extentNum / retrieveRc:
DATA #3 : SQLPLFR_SCAN_ID, PD_TYPE_SQLPLFR_SCAN_ID, 8 bytes
LFR Scan Num            = 23071763
LFR Scan Caller's EDUID = 3455
DATA #4 : db2LogStreamIDType, PD_TYPE_DB2_LOG_STREAM_ID, 2 bytes
0
DATA #5 : SQLPG_EXTENT_NUM, PD_TYPE_SQLPG_EXTENT_NUM, 4 bytes
58334
DATA #6 : unsigned integer, 8 bytes
1

2022-04-21-20.33.54.955160+480 I1078617372E1097      LEVEL:
Warning
PID     : 378486               TID : 139675339581184 PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   :
SAMPLE
APPHDL  : 0-47540              APPID:
*LOCAL.db2inst1.220421103035
AUTHID  : DB2INST1             HOSTNAME: MYHOST1
EDUID   : 1839                 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services, sqlpgReadLogAPI,
probe:6677
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic
Error"
          DIA8526C A fatal error occurred in data protection
services.
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
-2038
DATA #2 : Boolean, 1 bytes
false
DATA #3 : Boolean, 1 bytes
true
DATA #4 : db2LRI, PD_TYPE_db2LRI, 24 bytes
lriType: 1 LFS/LSN: 2320394964/0000001DCAA07918
DATA #5 : db2LRI, PD_TYPE_db2LRI, 24 bytes
lriType: 1 LFS/LSN: 2320394964/0000001DCAA07918
DATA #6 : db2LRI, PD_TYPE_db2LRI, 24 bytes
lriType: 1 LFS/LSN: 2320394964/0000001DCAA07918
DATA #7 : db2LRI, PD_TYPE_db2LRI, 24 bytes
lriType: 1 LFS/LSN: 18446744073709551615/FFFFFFFFFFFFFFFE
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Using applications that call db2ReadLog api                  *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Fix in next release                                          *
****************************************************************
Local Fix:
Before making online change to the OVERFLOWLOGPATH database
configuration, stop the applications that call db2ReadLog() api.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Using applications that call db2ReadLog api                  *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Fix in next release                                          *
****************************************************************
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.04.2022
28.07.2022
08.09.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)