UTF-8 Conversion
Nate Hicks asked whether converting an instance to UTF-8 requires handling the sysmaster and related databases. Fernando Nunes said conversion means export, set locale, import, and a server can hold databases with different locales while the sys databases stay iso-8859-1. He warned: no distributed queries across locales, byte versus char function semantics, field lengths possibly too short, and invalid characters.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
When converting an instance to UTF-8 or any other DB_LOCALE do you need to do the sys* tables? If so how? I'm not sure what's going to touch them other than the instance itself so did not do them initially because I don't think anything else is going to touch it but that. Thanks. Nate Hicks
Not sure if I got your question... To "convert" the data, you need to export/import... so you won't touch the "sys*" tables. As a side note, any user can create a table that starts with "sys"... user tables start at tabid=100 Regards On Wed, Feb 12, 2014 at 6:15 PM, NATE HICKS <nathaniel.hicks@trnswrks.com>wrote: > When converting an instance to UTF-8 or any other DB_LOCALE do you need to > do > the sys* tables? If so how? I'm not sure what's going to touch them other > than > the instance itself so did not do them initially because I don't think > anything else is going to touch it but that. > > Thanks. > > Nate Hicks > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently... --001a1136ad2e461d2d04f239bb37
Yeah by conversion I meant export/set locale/import. the sys* stuff I was referring to are the sysmaster and associated databases, not tables. sorry for the confusion.
Oh... the confusion was mine! Again, yes... on a single server you can have databases with different locales and the sys* are supposed to be the "default iso-8859-1. Keep in mind that changing the locale may have some implications (this is not a complete list): - We don't support distributed queries across databases with diferent locales - If you change from single byte to multi-byte some functions may not behave as we'd expect (check if the function semantic is bytes or chars) - If you change from single to multi-byte the field length may not be enough on some fields - You may have invalid characters in your databases Regards On Wed, Feb 12, 2014 at 6:30 PM, NATE HICKS <nathaniel.hicks@trnswrks.com>wrote: > Yeah by conversion I meant export/set locale/import. the sys* stuff I was > referring to are the sysmaster and associated databases, not tables. sorry > for > the confusion. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently... --047d7b3430de9fbd2b04f23a3a50