Results 1 to 2 of 2

Thread: Globalization

  1. #1
    Join Date
    Mar 2004
    Posts
    1

    Unanswered: Globalization

    Hi,

    We are in the process of internationalizing our product called Reveleus, which is an end-to-end BI product.

    We have already done the internationalization on Oracle. We now plan to do it on DB2. For that, could you please provide me with some of the answers we are looking for.

    1) Database encoding
    How do we specify the database encoding?
    Can the database encoding be altered once the database is created?
    What are the various encodings supported by DB2 UDB?
    What are the things that get affected by the Database Encoding ?

    2) NLS parameter
    What are the NLS (National Language Support) parameters that db2 provides to support internationalization?

    3) Client communication
    How does a client specify the encoding of the data that it is sending/receiving? (Equivalent to NLS_LANG in Oracle).
    How does a client specify the language and territory portion of a locale?
    If language and territory can be specified, then what all do they affect?
    (Eg: - database messages, date, number formatting, sorting etc)

    4) String functions
    Do string functions like substring, instr, length etc work in terms of characters or bytes? If they work in terms of characters, then do we have equivalent functions which work in terms of bytes?

    5) Data loading
    Do the data loading utilities like load handle non-ASCII data and how?
    Will the log files created during load activities always be in English or can they be configured?
    For fixed width files, does the positions correspond to bytes/chars ?
    Is there any way we can specify byte/char semantics ?

    6) Database messages
    Is it possible to get the database messages in a language other than English? If yes, is it possible for a client to configure the language in which the messages would appear?

    7) Can I have the following in any non-ascii characters (ex: In Korean Characterset)
    a) Table Name
    b) Column Names
    c) Other database object names (views/procedure names etc)

    Thanks in Advance

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1

    Re: Globalization

    Originally posted by kishorem
    Hi,

    We are in the process of internationalizing our product called Reveleus, which is an end-to-end BI product.

    We have already done the internationalization on Oracle. We now plan to do it on DB2. For that, could you please provide me with some of the answers we are looking for.

    1) Database encoding
    How do we specify the database encoding?
    Can the database encoding be altered once the database is created?
    What are the various encodings supported by DB2 UDB?
    What are the things that get affected by the Database Encoding ?

    2) NLS parameter
    What are the NLS (National Language Support) parameters that db2 provides to support internationalization?

    3) Client communication
    How does a client specify the encoding of the data that it is sending/receiving? (Equivalent to NLS_LANG in Oracle).
    How does a client specify the language and territory portion of a locale?
    If language and territory can be specified, then what all do they affect?
    (Eg: - database messages, date, number formatting, sorting etc)

    4) String functions
    Do string functions like substring, instr, length etc work in terms of characters or bytes? If they work in terms of characters, then do we have equivalent functions which work in terms of bytes?

    5) Data loading
    Do the data loading utilities like load handle non-ASCII data and how?
    Will the log files created during load activities always be in English or can they be configured?
    For fixed width files, does the positions correspond to bytes/chars ?
    Is there any way we can specify byte/char semantics ?

    6) Database messages
    Is it possible to get the database messages in a language other than English? If yes, is it possible for a client to configure the language in which the messages would appear?

    7) Can I have the following in any non-ascii characters (ex: In Korean Characterset)
    a) Table Name
    b) Column Names
    c) Other database object names (views/procedure names etc)

    Thanks in Advance
    That's a lot of questions. :-) You'll find most of the answers about NLS in "Administration Guide: Planning" and "Application Development Guide" (you can find a link to the DB2 manuals in the "Useful Stuff" post on this board).

Posting Permissions

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