Topic
  • 2 replies
  • Latest Post - ‏2013-03-28T06:35:25Z by KaoriN
sbjerry
sbjerry
23 Posts

Pinned topic About the code page

‏2013-03-26T03:45:19Z |
As a Chinese user, we are always confused by the character set and code page, it has brought a lot of troubles.

Reading from the Installation and Configuration Guide, OPTIM is influenced by several aspacts, such as workstation's locale, oracle client character set, optim directory's character set, DB2CODEPAGE, and so on.

In my workstation on Windows2008, the code page of OS is 936, the OPTIM directory is UTF8, the DB2CODEPAGE=1208(the DB2 instance hosts the optim directory) ,The ORACLE Client's NLS_LANG=AMERICAN_AMERICA.AL32UTF8,

And the source Oracle DB is AL32UTF8

But in the I attach a PR0TOOL.005 which records the trace of convert process, I saw "CreateICUAnchor ICU Conv: oracle-zhs16gbk opened. CP:936, DBType:'0',MBType:'1'...."

Why the ICUAnchor ICU Conv is oracle-zhs16gbk ? What's the priority of these code page/ character set?
Updated on 2013-03-28T06:35:25Z at 2013-03-28T06:35:25Z by KaoriN
  • sbjerry
    sbjerry
    23 Posts

    Re: About the code page

    ‏2013-03-26T04:12:50Z  
    As I tested, the ICUAnchor is decided by the format of the OS. But not know ICUAnchor's function yet.
  • KaoriN
    KaoriN
    5 Posts

    Re: About the code page

    ‏2013-03-28T06:35:25Z  
    • sbjerry
    • ‏2013-03-26T04:12:50Z
    As I tested, the ICUAnchor is decided by the format of the OS. But not know ICUAnchor's function yet.
    Hi,

    This entry means that Optim just opens the converter for future use. As you may be aware, Optim opened other converters, too. Optim decides a converter when Optim uses in context. On your environment, the opened converters are rarely used.

    Thanks,
    Kaori