Discussions
Categories
- 197K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 556 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 468 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
What is the best way to change NLS_CHARACTERSET?
We are using a Oracle 11.2.0.4 database.
We wanted to change NLS_CHARACTERSET from "WE8MSWIN1252" to "AL32UTF8".
Can anybody suggest us a efficient plan?
Please share blogs or steps if any.
Comments
-
Consider using the Oracle Database Migration Assistant for Unicode, aka DMU (link).
But start by reading the documentation (link) carefully before doing anything, so you may anticipate the possible difficulties.
And make sure that you have a fallback plan (e.g. full backup, guaranteed restore point, etc.) in case things go wrong during (or after) the migration and you have to roll it back. This is a migration.
Regards,
-
Besides, the 11.2.0.4 release is now out of support, which means Oracle will not provide with any fix for that release anymore (unless you have paid for the Market-Driven Support extension, which entitles you to receive corrections of Severity-1 and security issues until 31 Dec. 2022).
This means that you'll probably have to upgrade to 19c very soon now, and therefore, you may want to delay the conversion to Unicode until after you've done that upgrade.
Regards,