That list was a high level overview of the steps. Some caveats you may run into: - characters that do not translate properly from non-unicode to unicode (7-bit ascii characters with ordinal value greater than 127). These have to be addressed at the db level after the import into the unicode db - arserver configuration (environment variables for locale/lang/oracle client, arserver configuration-ar.conf)
Axton Grams On Tue, Sep 16, 2008 at 9:58 AM, Axton <[EMAIL PROTECTED]> wrote: > You need to: > > - create a new db instance that uses the AL32UTF8 character set > - import your non-unicode db into the new instance > - you then need to upgrade/reinstall your arserver to a unicode version > > Axton Grams > > On Tue, Sep 16, 2008 at 2:26 AM, anil RAI <[EMAIL PROTECTED]> wrote: >> ** >> Hi, >> >> If ORACLE database is non Unicode and ARS is connected with non >> Unicode database. >> >> We have to upgrade the ARS as unicode then who is responsible for >> upgrading database to unicode supported. >> I mean BMC provides any document or white paper about how the DATABASE >> is upgraded to unicode. >> >> >> Thanks & Regards >> Anil >> ________________________________ >> Did you know? You can CHAT without downloading messenger. Click here >> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" >> html___ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
