By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,924 Members | 1,793 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,924 IT Pros & Developers. It's quick & easy.

Change format US-1252 to UTF-8

P: n/a
HI All,

I am using Windows,
Database territory = US
Database code page = 1252
Database code set = IBM-1252
Database country/region code = 1
Database collating sequence = UNIQUE

now I want change to UTF-8 format in DB2 , data is in databases .
I am new to DB2, Pl. help me.

Thanks in Advance.

Ravi.

Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Code set (code page) is determined at database creation time and cannot
be changed (UDB Command Reference).

The only option I know would be to move the data to a new database. If
you have a mature application, this could cause issues changing all of
the access mechanisms used by applications. Two copies would allow you
to move to UTF-8 then move back to keep the database name.

If all access to the database is through clients that have a local alias
refering to the database name then moving the data to a new database
would require changing client configurations and would not involve
application changes.

Phil Sherman
Ravi wrote:
HI All,

I am using Windows,
Database territory = US
Database code page = 1252
Database code set = IBM-1252
Database country/region code = 1
Database collating sequence = UNIQUE

now I want change to UTF-8 format in DB2 , data is in databases .
I am new to DB2, Pl. help me.

Thanks in Advance.

Ravi.

Nov 12 '05 #2

P: n/a
Phil Sherman wrote:
Code set (code page) is determined at database creation time and cannot
be changed (UDB Command Reference).

The only option I know would be to move the data to a new database. If
you have a mature application, this could cause issues changing all of
the access mechanisms used by applications. Two copies would allow you
to move to UTF-8 then move back to keep the database name.

If all access to the database is through clients that have a local alias
refering to the database name then moving the data to a new database
would require changing client configurations and would not involve
application changes.


You could work with CATALOG DATABASE and UNCATALOG DATABASE without
affecting any applications/clients.

--
Knut Stolze
Information Integration Development
IBM Germany / University of Jena
Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.