DB2 - Problem description
| Problem IC91283 | Status: Closed |
SQL0901N IS RETURNED FOR A QUERY THAT FEATURES A UNION ALL VIEW WITH A HOST VARIABLE PREDICATE ON THAT VIEW. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
db2diag.log messages:
2012-08-27-08.55.33.950015+060 E1828223E780 LEVEL: Error
PID : 8636 TID : 46970030778688PROC :
db2sysc 0
INSTANCE: DB2INST1 NODE : 000 DB : TESTDB
APPHDL : 0-4075 APPID:
12.345.678.901.2345.67890123456
AUTHID : DBAUTH
EDUID : 343 EDUNAME: db2agent (TESTDB) 0
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:10
MESSAGE : ADM14005E The following error occurred: "AppErr".
First Occurrence
Data Capture (FODC) has been invoked in the following
mode:
"Automatic". Diagnostic information has been recorded
in the
directory named
"/var/ibmdb2/db2inst1/sqllib/db2dump/FODC_AppErr_2012-08-27-08.5
5.33.
949844_8636_343_000/".
2012-08-27-08.55.33.951018+060 I1830911E856 LEVEL: Severe
PID : 8636 TID : 46970030778688PROC :
db2sysc 0
INSTANCE: DB2INST1 NODE : 000 DB : TESTDB
APPHDL : 0-4075 APPID:
12.345.678.901.2345.67890123456
AUTHID : DBAUTH
EDUID : 343 EDUNAME: db2agent (TESTDB) 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: 19
sqlerrmc: Already found DOID1
sqlerrp : SQLNG0BD
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x0000004C (5) 0xFFFFC86B (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
2012-08-27-08.55.33.952324+060 I1835754E5488 LEVEL: Severe
PID : 8636 TID : 46970030778688PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : TESTDB
APPHDL : 0-4075 APPID:
12.345.678.901.2345.67890123456
AUTHID : DBAUTH
EDUID : 343 EDUNAME: db2agent (TESTDB) 0
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_sibling,
probe:200
MESSAGE : section stmt
DATA #1 : Hexdump, 985 bytes
<<Hex dump with SQL statement>>
The above -901 error happens due to a logic problem in a sanity
check where it has incorrectly flagged the SQL statement as an
error in the sql compiler when in fact, there is nothing wrong
with the compile and it should have been allowed to continue to
complete the SQL query compile. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 3. * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
First fixed in DB2 Version 10.1 Fix Pack 3. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.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 |
|