collate_info - Collating information configuration parameter
This parameter determines the database's collating sequence. For a language-aware collation or locale-sensitive UCA collation, the first 256 bytes contain the string representation of the collation name (for example, "SYSTEM_819_US").
This parameter can only be displayed using the db2CfgGet API. It cannot be displayed through the command line processor.
- Configuration type
- Database
- Parameter type
- Informational
This parameter provides 260 bytes of database collating
information. The first 256 bytes specify the database collating sequence,
where byte n
contains the sort weight of the code point whose
underlying decimal representation is n
in the code page of
the database.
- 0 - The sequence contains non-unique weights
- 1 - The sequence contains all unique weights
- 2 - The sequence is the identity sequence, for which strings are compared byte for byte.
- 3 - The sequence is NLSCHAR, used for sorting characters in a TIS620-1 (code page 874) Thai database.
- 4 - The sequence is IDENTITY_16BIT, which implements the
CESU-8 Compatibility Encoding Scheme for UTF-16: 8-bit
algorithm as specified in the Unicode Technical Report #26 available at the Unicode Technical Consortium website at http://www.unicode.org - X'8001' - The sequence is UCA400_NO, which implements the Unicode Collation Algorithm (UCA) based on the Unicode Standard version 4.0.0, with normalization implicitly set to ON.
- X'8002' - The sequence is UCA400_LTH, which implements the Unicode Collation Algorithm (UCA) based on the Unicode Standard version 4.0.0, and sorts all Thai characters as per the Royal Thai Dictonary order.
- X'8003' - The sequence is UCA400_LSK, which implements the Unicode Collation Algorithm (UCA) based on the Unicode Standard version 4.0.0, and sorts all Slovakian characters properly.
- For a language-aware collation or locale-sensitive UCA collation, the first 256 bytes contain the string representation of the collation name.
- Collations based on the Unicode Collation Algorithm of the Unicode Standard version 4.0.0 have been deprecated in Version 10.1 and might be removed in a future release.
If you use this internal type information, you need to consider byte reversal when retrieving information for a database on a different platform.
You can specify the collating sequence at database creation time.