DB2 - Problem description
Problem IC80605 | Status: Closed |
SQL0130N IS RETURNED WHEN "LIKE NULL" PREDICATE IS USED IN A DATABASE CREATED WITH UCA500R1 COLLATING SEQUENCE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When a database is created with UCA500R1 collating sequence, and a query similar to the following is issued, a. SQL0130N error is returned, $ db2 "select * from tab1 where x like null" SQL0130N The ESCAPE clause is not a single character, or the pattern string contains an invalid occurrence of the escape character. SQLSTATE=22025 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * v97fp5 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to V97fp6 * **************************************************************** | |
Local Fix: | |
Use "IS NULL" predicate instead of "LIKE NULL" | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC84226 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.12.2011 12.06.2012 12.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 |