Re: Dealing with NUL (hex code 00) characters in files/tables -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Matt

Try

Select * from tablename where fieldname is null

Kind Regards
Alan Jordan

RODIN by Coglin Mill | 507.282.4151 x 103 | 507.261.4495 Mobile |
Rochester, Minnesota USA | www.thinkrodin.com

From: Matt Olson <Matt.Olson@xxxxxxxx>
To: "midrange-l@xxxxxxxxxxxx" <midrange-l@xxxxxxxxxxxx>,
Date: 06/29/2012 12:07 PM
Subject: Dealing with NUL (hex code 00) characters in files/tables
Sent by: midrange-l-bounces@xxxxxxxxxxxx

Folks,

We found an issue with the IBM DB2 Driver for .NET (also occurs if you try
to do the Data Transfer from IBM i) when dealing with characters in a CHAR
field (CCSID 37) that contain a NUL (hex code 00) character in the field.
In both cases (.NET driver and Data Transfer from IBM i) we get a
character code conversion error and the whole SELECT SQL statement fails.

Any easy way to find these values in all tables, and hopefully we can
track down how the heck this bad data is getting entered.

I attempted: select * from tablename where fieldname like '%' || chr(00)
|| '%' to no avail.

Matt

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.