DB2 - Problem description
Problem IC78499 | Status: Closed |
UPDATE STATEMENT MAY FAIL WITH SQL0901N "SOURCE FOR INPUT RCOB HAS NOT BEEN INSTANTIATED" | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
UPDATE statement could fail with SQL0901N "Source for input RCOB has not been instantiated", against DB2 LUW data source, if ONE of the following conditions is met: 1) there are more than 255 table names in the SET statement of UPDATE ; 2) a row-based assignment clause is used, such as "update n1 set (c1, c2, c3, ...) = (<subquery>)", whereas number of table names in the <subquery> is N, number of columns in (c1,c2,...) is M, and M * N > 255 . The following is an example of db2diag.log for this issue. 2011-04-01-18.21.00.598180+540 I260351044A626 LEVEL: Severe PID : 24503 TID : 2199279102288PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : DBNAME APPHDL : 0-17049 APPID: 172.24.122.25.49617.11033122564 AUTHID : DB2FENC1 EDUID : 51944 EDUNAME: db2agent (DBNAME) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:275 MESSAGE : MASTER TIME INFO DATA #1 : Hexdump, 32 bytes 0x0000020724042B20 : 0000 0000 4D94 A1E2 0009 0000 0000 2553 ....M.........%S 0x0000020724042B30 : C78E 118B BC39 C5B4 0000 0000 0000 0000 .....9.......... 2011-04-01-18.21.00.598241+540 I260351671A190 LEVEL: Severe PID:24503 TID:2199279102288 NODE:000 Title: MASTER TIME INFO Dump File:/home/db2inst1/sqllib/db2dump/24503.51944.000.dump.bin 2011-04-01-18.21.00.598422+540 I260351862A875 LEVEL: Severe PID : 24503 TID : 2199279102288PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : DBNAME APPHDL : 0-17049 APPID: 172.24.122.25.49617.11033122564 AUTHID : DB2FENC1 EDUID : 51944 EDUNAME: db2agent (DBNAME) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:300 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 47 sqlerrmc: Source for input RCOB has not been instantiated sqlerrp : SQLNG07A sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000 (4) 0x00000001 (5) 0xFFFFFFC4 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * User using update statements conforming to the condition. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.7 Fix Pack 6. * **************************************************************** | |
Local Fix: | |
temporarily set server option db2_select_scalar_SQL to N for the UPDATE: set server option db2_select_scalar_SQ to 'N' for server FED_SVR <issue the UPDATE> set server option db2_select_scalar_SQ to 'Y' for server FED_SVR | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 9.7 Fix Pack 6. | |
Workaround | |
Temporarily set server option db2_select_scalar_SQL to N for the UPDATE: | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.09.2011 05.06.2012 05.06.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.6 |