To: Reen, Elizabeth [ICG-IT] <er71957_at_imcnam.ssmb.com>; Oracle-L <oracle-l_at_freelists.org>
Subject: Re: Characterset change
Hi Liz,
Thanks much for the information.
I wonder, if there is a way to measure how much of storage impact we would see with the characterset migration?
AFAIK, we currently don't store anything non-english.. Even in the worst case if we had something, I'd estimate it to be <1%.
-Upendra
From: Reen, Elizabeth <elizabeth.reen_at_citi.com<mailto:elizabeth.reen_at_citi.com>>
Sent: Wednesday, January 16, 2019 4:17 PM
To: 'nupendra_at_hotmail.com'; Oracle-L
Subject: RE: Characterset change
Time is part of your problem. If your varchar columns are defined in bytes, then your data may be too big to move. Certain characters go from single byte to multi byte thus expanding the size of your data. That has killed several conversions in my career. The amount of work was too much.
Liz
Elizabeth Reen
CPB Database Group Manager
From: [External] oracle-l-bounce_at_freelists.org<mailto:oracle-l-bounce_at_freelists.org> <oracle-l-bounce_at_freelists.org<mailto:oracle-l-bounce_at_freelists.org>> On Behalf Of [External] Upendra nerilla
Sent: Wednesday, January 16, 2019 3:12 PM
To: Oracle-L <oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>>
Subject: Characterset change
Hello Oracle Experts -
Environment: Redhat 6.7, EE 12.1
DB size: 4TB
We have been looking into switching the Characterset of a DB from "WE8ISO8859P15" to "AL16UTF8".
This is a standalone Enterprise Edition database (non-RAC, No Data Guard).
We have looked at DB Migration Assistant and DataPump as possible options. Both involves quite a bit of downtime,
wondering if there is a better way to perform this activity? Would Transportable tablespace be an option?
