Re: Characterset change
From: Rich J <rjoralist3_at_society.servebeer.com>
Date: Wed, 16 Jan 2019 14:41:45 -0600
Message-ID: <15fa92d7356b3efc1e2653ef0ea69fd5_at_society.servebeer.com>
Date: Wed, 16 Jan 2019 14:41:45 -0600
Message-ID: <15fa92d7356b3efc1e2653ef0ea69fd5_at_society.servebeer.com>
On 2019/01/16 14:11, Upendra nerilla wrote:
> 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?
This thread from last year may help:
https://www.freelists.org/post/oracle-l/Database-migration-options
Also, make sure those character sets are specifically supported for the migration in v12.1, as the destination must be a superset of the source:
https://docs.oracle.com/database/121/NLSPG/applocaledata.htm
I don't see "AL16UTF8" there anywhere...perhaps you meant "AL32UTF8"? Also presuming "AL16UTF16" for the national character set...
Rich
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Jan 16 2019 - 21:41:45 CET