× 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.


  1.  Home
  2. MIDRANGE-L
  3. June 2012

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

I had the same problem. What I ended up doing is :

REPLACE(SUPV_COMMENTS, x'00', ' ') AS SUPV_COMMENT

I know it isn't a fix, but a work-around.

--
Mike Wills
http://mikewills.me


On Fri, Jun 29, 2012 at 12:07 PM, Matt Olson <Matt.Olson@xxxxxxxx> wrote:

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.