bionrealty.blogg.se - Collate data

#Collate data how to

The following query shows how Oracle treats special characters with regards to sort operations. INSERT INTO t1 VALUES (4, 'LOwenbrauerei', 'BrAunlingen') INSERT INTO t1 VALUES (3, 'Lowenbrauerei', 'Braunlingen') INSERT INTO t1 VALUES (2, 'LÖwenbrauerei', 'BrÄunlingen') INSERT INTO t1 VALUES (1, 'Löwenbrauerei', 'Bräunlingen') Notice the variation in the first letter of the first name. Sqlplus the following test table and populate it with some data containing special characters. We can do this by setting the NLS_LANG environment variable correctly before starting SQL*Plus. Before we start using UTF data we need to make sure SQL*Plus will handle it properly. To understand the impact of collation, it's important to understand the default behaviour of an Oracle database.

Other setting can be used, but the output may not resemble that shown in this article.

The database character set is A元2UTF8, NLS_LANGUAGE=AMERICAN and NLS_TERRITORY=AMERICA.

Your COMPATIBLE parameter is set to 12.2 or higher.

Without this you will see this error, "ORA-43929: Collation cannot be specified if parameter MAX_STRING_SIZE=STANDARD is set."

Your MAX_STRING_SIZE parameter is set to EXTENDED.

Your are using Oracle Database 12c Release 2 (12.2).

Extended Data Types in Oracle Database 12c Release 1 (12.1).

The wider implications of using collations, as well as the restrictions associated with them can be found here.

#Collate data how to

This article is only covering the basics of how to set the collation.