Highlighted
Absent Member.
Absent Member.
5250 views

Changing Database Character Sets


Discussion posted 3/6/08 by George Bonvanie
Details:

richja

When we originally set installed TeamTrack we utilized an Oracle database instance using the US7ASCII character set. We are now in the process of preparing for the teamtrack 7.x upgrade due out at any time which only supports the UTF-8 character set. So because we can't change the character set on the existing database (there are other systems that use that database), we are looking to move the teamtrack schema to a new instance using the UTF-8 character set.
We have done this with a test instance of teamtrack but have had to modify the configuration of some of the table's columns, expanding their size to accomodate the existing data in the new format. We also had to change some of the varchar2(4000 byte) columns to CLOBs. This could present a problem since Oracle handles varchar2 and CLOBs differently. However, we haven't seen any problems with the way the test server is running and handling the modified columns.
Has anyone done this already or have any knowledge about what problems we may encounter? Any information would be greatly appreciated.
Posted 1/10/2008 9:33 AM
0 Likes
1 Reply
Highlighted
Absent Member.
Absent Member.

Re: Changing Database Character Sets


This is an old migrated post that has been assigned status Complete.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.