Bug 21201 - Problem with Oracle and Web importing foreign characters
Summary: Problem with Oracle and Web importing foreign characters
Alias: None
Product: Red Hat Web Site
Classification: Red Hat
Component: Store
Version: current
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Martin C. Messer
QA Contact: Jay Turner
Depends On:
TreeView+ depends on / blocked
Reported: 2000-11-21 20:41 UTC by Jeffrey Cohen
Modified: 2015-01-07 23:42 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2003-07-22 17:05:53 UTC

Attachments (Terms of Use)

Description Jeffrey Cohen 2000-11-21 20:41:19 UTC
There seems to be a recurrance of foreign characters not importing properly
from the web into Oracle.

The following order: 3111741 from web order W2200617 imported with the
Customer name:

"SVERRIR C LAFSSON"  it should have been "...OLAFFSON"  

I beleive there was an O with an 'umlaut'  (the 2 little dots above a
letter) in the original customer name and somewhere along the line, an
interface corrupted this value to an invalid
character --(a square block)-- in the name field.

Can this be fixed???

Comment 1 Jeffrey Cohen 2000-11-21 20:44:55 UTC
I have since changed the information, Customer Name and Contact name on Account
# 274263.

I just over-typed the correct information, hopefully deleting the corrupted
character.  Hopefully the order will go now.


Comment 2 Samir Kothari 2000-11-21 21:44:35 UTC
If you look at the web_user_personal_info table for this user (464319), you
will see the following:


When I cut-n-paste into the bugzilla screen it converts it to:


It appears to be getting imported into oracle as the 1st case above.

Comment 3 Jeffrey Cohen 2000-12-14 13:17:18 UTC
Here is yet another example of corrupted characters...

 His proper name should be: Mindez Guido Josi Angel


Customer information

                                   Information for customer: mguido-RH2000 
            User ID
            First name
                                 Guido Josgngel
            Last name

Comment 4 Jay Turner 2001-05-15 12:50:08 UTC
Status update on this issue?  Thanks :-)

Comment 5 Tom Lancaster 2001-05-21 23:08:51 UTC
According to the Oracle reference: "All character data in the version 8 database
is assumed to be in the character encoding scheme specified in the CREATE
DATABASE command that created the database."
I really don't know what this is. 
The NLS LANG variable also has something to do with it. I seem to remember Paul
Lindner saying that the web tables supported UTF8, which should be able to deal
with the above cases. 

Comment 6 Martin C. Messer 2003-07-22 17:05:53 UTC
Dealing with this same issue elsewhere.

Note You need to log in before you can comment on or make changes to this bug.