The option that I can think of is (to convert your non Unicode data to Unicode ) use remedy migrator tool and migrate your non unicode server to Unicode server (making sure you have identical setup ready )- 7604 as that of 7.1 when it comes to the applications. OR another option is use remedy migrator between existing 7.1 non Unicode to new 7.1 unicode server , this will take care of all characters , localized data conversion, then upgrade ARS only to 7604 - run BPCU tool to identify your customization and convert them into overlay. Once this is done think of rest of the application upgrade.
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Antonio Monizza Sent: Monday, February 11, 2013 10:39 PM To: [email protected] Subject: Upgrade ARS 7.1 to ARS 7.6.04 SP4 - UNICODE issue ** Hello listers, we're upgrading an ARS 7.1 patch 7 non UNICODE on AIX 5.3 against an Oracle DB with UTF8 character set to ARS 7.6.04 SP4 always on Oracle with UTF8 As a first step we're doing the upgrade on our dev environment, then we'll proceed with test env and finally with prod During the installation process, after the Type of Installation (Upgrade, Overwrite, Server group) step, for which we selected the Upgrade option, the Installer gave us the following error: "The database is configured for UNICODE but your system LANG variable is set to C You must change your LANG variable to a supported UNICODE language before you can complete this installation" Now: 1) our current ARS 7.1 non UNICODE installation has been always running without any problem on a UNICODE Oracle db 2) our idea is to avoid all the complications involved in transforming our ARS installation into a UNICODE ARS, mostly because we realized in the past that it wasn't possible to change ARS from non UNICODE to UNICODE during the execution of the ARS 7.1 upgrade scipt, and BMC told us to do a fresh new installation and data exp/imp instead, which is not feasible for us We just opened a ticket to BMC and they told us that the upgrade from Non-Unicode to Unicode environment and Unicode to non-Unicode is not supported from ARS 7.5 onward, and that we should tell our DBA to change the database to non-Unicode to proceed with the ARS 7.6 upgrade Again, for a number of reasons we cannot change our DB to non UNICODE. How should we proceed now? Any tips? Thanks a lot in advance Kind Regards, Antonello Monizza _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
