RE: Characterset Question

Interesting that the source is also AL32UTF8, but the data is transferred via Informatica. My guess is that's where the issue is.

Scott Canaan '88
Sr Database Administrator
Information & Technology Services
Finance & Administration
Rochester Institute of Technology
o: (585) 475-7886 | f: (585) 475-7520
srcdco_at_rit.edu<mailto:srcdco_at_rit.edu> | c: (585) 339-8659

CONFIDENTIALITY NOTE: The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.

From: Mark W. Farnham <mwf_at_rsiz.com>
Sent: Friday, March 22, 2024 2:50 PM
To: Scott Canaan <srcdco_at_rit.edu>; oracle-l_at_freelists.org Subject: RE: Characterset Question

That should be a lossless conversion with the possible exception of clob/blob.

However, figuring out the appropriate NLS_PARAMETER values for the client and the server have to be set right.

How are you bringing data from Peoplesoft over to your new database?

IF it is application to database, setting the client and server parameters should take care of it.

IF it is database (old) to database (new), then there is possibly some data in the (old) database that is not actually US7ASCII and some cleanup may be required.

https://docs.oracle.com/en/database/oracle/oracle-database/19/nlspg/supporting-multilingual-databases-with-unicode.html

should give you a leg up, and there are more similar documents on Oracle.

I'm a bit rusty on this, my friend, but I think that is about correct.

mwf

From: oracle-l-bounce_at_freelists.org<mailto:oracle-l-bounce_at_freelists.org> [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Scott Canaan ("srcdco") Sent: Friday, March 22, 2024 2:23 PM
To: oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org> Subject: Characterset Question

We are in the process of migrating all of our Oracle databases from Red Hat 7 to Red Hat 8. In creating the new databases in Red Hat 8, we've been going with the default characterset of AL32UTF8. Many of the old databases are US7ASCII. We are having trouble with applications trying to insert into text fields in the new database. In one case, bringing data from Peoplesoft that has a degree symbol fails because that comes over as 2 bytes instead of one. I thought that AL32UTF8 should handle those characters. What needs to be done to accommodate this?

Scott Canaan '88
Sr Database Administrator
Information & Technology Services
Finance & Administration
Rochester Institute of Technology
o: (585) 475-7886 | f: (585) 475-7520
srcdco_at_rit.edu<mailto:srcdco_at_rit.edu> | c: (585) 339-8659 CONFIDENTIALITY NOTE: The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.

--
http://www.freelists.org/webpage/oracle-l