Results 1 to 3 of 3
  1. #1
    Join Date
    Jan 2012

    Unanswered: create a UTF-16 database

    Hi all,
    I'm planning a UNICODE DB2 10.1 database with the majoity of Asian characters data, so I'm wondering if I need to create it with a UTF-8 or UTF-16 code set.
    When trying to create both on my local Linux machine I'm able to create it in the UTF-8 case, but not with UTF-16.
    I try:
    > db2 create database mydb using codeset utf-16 territory default collate using IDENTITY_16BIT
    but it fails complaining with a wrong territory, even if the infocenter says all the territory codes should be supported with utf-16.
    The same command with utf-8 instead of utf-16 succeeds.

    Could you please let me know why it happens?

  2. #2
    Join Date
    Apr 2006
    Provided Answers: 11
    I don't think you can use codeset utf-16 only utf-8
    utf-16 can be used for collating sequence
    and also means you use graphic/var-graphic
    Best Regards, Guy Przytula
    Database Software Consultant
    Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
    Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
    DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5-V11 Fundamentals- DB Admin - Advanced DBA -Dprop..
    Information Server Datastage Certified

  3. #3
    Join Date
    Jan 2012
    Yes I'll be using several VARGRAPHIC columns.
    Do you agree that if I plan to have lots of Asian strings in those VARGRAPHIC columns, as well as in other VARCHAR columns, I should choose uft-8 codeset and IDENTITY_16BIT collating sequence (instead of IDENTITY) when creating my database?


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts