|
Problem IC95437
|
Status: Closed |
FEDERATED FMP TRAPPED WHEN QUERY JDBC NICKNAME WITH CLOB DATA LONGER THAN 32K |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Federated FMP process trapped when selecting a JDBC nickname
with LOB column data greater than 32k:
SELECT * FROM TESTLOB
--------------------------------
SQL1476N The current transaction was rolled back because of
error "-1476".
SQLSTATE=40506
<StackTrace>
-------Frame------ ------Function + Offset------
0x000000000000F4E8 ?unknown + 0x0
0x09000000073C6518 fetch_lob__14Jdbc_StatementFPiUiPUiT3PUc +
0x1298
0x09000000073BD33C fetch_lob__10Jdbc_QueryFPiUiPUiT3PUc + 0x5C
0x09000000233BC4A8 sqlqg_FMP_Fetch__FP12sqlri_rquery + 0x108
0x0900000023372DA0
sqlqgRouter__FP17sqlqg_FMP_RequestPP15sqlqg_FMP_ReplyP10sqlri_uf
ob + 0x1FA0
0x0900000023376884 sqlqg_fedstp_hook + 0x1A4
0x09000000332A103C sqlqgDyload__FP10sqlri_ufob + 0x334
0x09000000333026E0 sqlerFedFmpListener + 0x790
0x0900000033B030B4 sqlerWorkerThreadEntry__FPv + 0x4E8
0x09000000006314F4 _pthread_body + 0xDC
</StackTrace>
This issue can be reproduce with a Postgre SQL case:
1. On Postgre SQL side, create a table:
CREATE TABLE public.testlob("C1" text)
2. Insert data equals or greater than 32k into above table.
3. On Federation Server side, create a nickname pointing to
above table
4. Select the nickname.
The issue may also happen to other JDBC data srouces. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* The users is accessing a JDBC nickname with LOB longer than *
* 32k *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Federation Server V10.5FP3. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
The problem is firstly fixed in Federation Server V10.5FP3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.08.2013
27.02.2014
27.02.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
