Unicode database
in [DB2]
|
From: Tony on 23 Jul 2010 10:38 Hi all, I've a UNIX box which has a DB2 client (UDB v9.5) connecting to a remote DB2 server(UDB v9.5) and some SAS applications running on top of the DB2 client. The remote DB2 server is planning to convert from non-unicode to unicode. I'm wondering what's the impacts on my client side? Thanks in advance!
From: Hardy on 23 Jul 2010 14:24 On Jul 23, 9:38 am, Tony <tonyedr...(a)gmail.com> wrote: > Hi all, > > I've a UNIX box which has a DB2 client (UDB v9.5) connecting to a > remote DB2 server(UDB v9.5) and some SAS applications running on top > of the DB2 client. The remote DB2 server is planning to convert from > non-unicode to unicode. I'm wondering what's the impacts on my client > side? > > Thanks in advance! you should be OK with the same client.
From: Tony on 23 Jul 2010 15:02 Thanks for the reply! So you mean I don't need to change the DB2 client configration, and the SAS applications should be no change as well? Thanks. On Jul 23, 2:24 pm, Hardy <wyh...(a)gmail.com> wrote: > On Jul 23, 9:38 am, Tony <tonyedr...(a)gmail.com> wrote: > > > Hi all, > > > I've a UNIX box which has a DB2 client (UDB v9.5) connecting to a > > remote DB2 server(UDB v9.5) and some SAS applications running on top > > of the DB2 client. The remote DB2 server is planning to convert from > > non-unicode to unicode. I'm wondering what's the impacts on my client > > side? > > > Thanks in advance! > > you should be OK with the same client.
From: Helmut Tessarek on 23 Jul 2010 18:33 > So you mean I don't need to change the DB2 client configration, and > the SAS applications should be no change as well? Thanks. You don't have to change the client configuration. The conversion between codepages is done automatically. Let's say you are using a unicode database (codepage 1208) and your client on AIX is using codepage 819. According to DRDA specification the conversion is always done on the receiving side. If you use e.g. the DB2 CLP and send a query to the database, the flow is as follows: 1) query or actually the bound values are converted at the server 2) server sends result in UTF8 3) client converts the data to codepage 819 The same is true for your SAS applications. IMPORTANT: You might want to check the collating sequence for the unicode database. You can choose the collating sequence only at the time you create the database. By default the collating sequence is IDENTITY, which will most likely result in a different sort order. -- Helmut K. C. Tessarek DB2 Performance and Development /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */
|
Pages: 1 Prev: db2 activate database results in 1226 - Overflow agent is notallowed Next: DB2 & LDAP problem |