|
Problem IT34304
|
Status: Closed |
SQL0344N ERROR MAY OCCUR IN NON-UNICODE, VARCHAR2 ENABLED DATABASE WHEN QUERY REFERENCES SYSIBM.SYSDUMMY1 or SYSIBM.DUAL
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
Query compilation may fail with SQL0344N in a non-unicode,
VARCHAR2-enabled database and the query references a Unicode
object as well as SYSIBM.DUAL or SYSIBM.SYSDUMMY1. For example:
create table Uni (c1 varchar(20)) ccsid unicode
insert into Uni values (select 'abc' FROM sysibm.dual)
SQL0344N The recursive common table expression "SYSIBM.DUAL"
has mismatched
data types, lengths or code pages for column "DUMMY".
SQLSTATE=42825
select * from uni union all select 'abc' from sysibm.sysdummy1
SQL0344N The recursive common table expression
"SYSIBM.SYSDUMMY1" has
mismatched data types, lengths or code pages for column
"IBMREQD".
SQLSTATE=42825 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 v11.5.5.1 *
**************************************************************** |
| Local Fix: |
Avoid the use of SYSIBM.DUAL or SYSIBM.DUMMY1. In the INSERT
example above, the subselect in the INSERT statement is not
necessary and can be rewritten as:
insert into Uni values ('abc');
In the UNION ALL example, the second subselect can be rewritten
as a values-clause
select * from uni union all values 'abc'; |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 v11.5.5.1 *
**************************************************************** |
| Comment |
First fixed in Db2 v11.5.5.1 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.09.2020
09.04.2021
09.04.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
