I've been asked to explain my solution...

I had an existing query that began to fail as soon as I added LCASE(COLUMN)
as selection in the query...which is why I started researching my issues
with that function. I dug deeper into my job log and found that my issue
was with a comparison I was performing on a different column in my WHERE

There was an invalid comparison in the WHERE clause that was not being
detected at SQL statement compile time. As well, becuase of the chosen
access plan (path) the invalid comparison was not encountered because
affected records had already been removed from selection.

Adding the LCASE(COLUMN) argument changed my access path. The new path
encountered the invalid argument while affected records were still available
for selection and failed at run-time.

Hopefully this is not too vague without schema info.


Ryan Hunt

"Ryan Hunt" <ryan.hunt@xxxxxxxxxxxxx> wrote in
message news:fel8ri$qbd$1@xxxxxxxxxxxxxxxx
I am getting data conversion mapping error (type 6: Numeric data that is
valid) when trying to use the LCASE function on a CHAR(30) column. The
difference I see between this column and other that I can LCASE is that it
is a CCSID 37 while the others are CCSID 65535.

CCSID means very little to me... It sounds like a collation option, but
an MS SQL DBA/DBD, I am used to database level collations...not column

Is the CCSID blocking use of the LCASE function?

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email:
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].