Storing and Checking Character Codepoints in an UTF8/AL32UTF8 (Unicode) database
(Doc ID 69518.1)
Last updated on AUGUST 23, 2021
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Oracle Database - Standard Edition - Version 18.104.22.168 and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 12-Mar-2018***
This article explains
* what UTF8 and AL32UTF8 is
* how to check if data is correctly stored in an UTF8/AL32UTF8 database
* how determine the codepoint for an UTF8/AL32UTF8 character
For a more general overview of using AL32UTF8 please read first
<Note 788156.1> AL32UTF8 / UTF8 (Unicode) Database Character Set Implications
Anyone using UTF8 or AL32UTF8 as NLS_CHARACTERSET.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!