Hi,
NO NO NO!!! You can not do the conversion on the database level. There are all
manner of counters and stuff that counts bytes instead of characters, and your
system will become corrupt.
If you do not have any character that will convert to multibyte in your
application, for example on a field label, you might possibly get it to work.
As for the data, it will work to some extent, but data might have swollen into
more bytes than you allow in certain fields without you knowing about it. This
will give users problems when changing old records.
Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)
Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11/12):
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.
> Note:In BMC Remedy AR System 6.x, it is possible to run a BMC Remedy AR
> System server in non-Unicode mode with a Unicode database. In BMC Remedy AR
> System 7.x and later, this type of configuration is not supported.
>
> I have tried in my test system prior to upgrade and it worked well.
>
> 01. export the database dump
>
> exp system/admin tablespaces=ARSYSTEM file=ARSYSTEM.dmp
>
> 02. Import again within the database which is configured as unicode instance
>
> imp system/admin tablespaces=arsystem file=arsystem.dmp FROMUSER=ARADMIN
> TOUSER=ARADMIN
>
> When you import it on unicode instance, it will do charset conversion
>
> Export file created by EXPORT:V10.02.01 via conventional path
> import done in US7ASCII character set and AL16UTF16 NCHAR character set
> import server uses AL32UTF8 character set (possible charset conversion)
>
> 03. once you able to get the db import, run the 7.1 installer and select
> unicode this time
> 04. Perform upgrade install of 7.6.04.
>
>
> Hope this helps
>
> ~ Vaibhav
>
>
>
> On Tue, Feb 12, 2013 at 10:56 AM, Grooms, Frederick W <
> frederick.w.gro...@xo.com> wrote:
>
>> What do you have on the ARS server for the language environment variables?
>>
>> LANG, LC_ALL, NLS_LANG
>>
>>
>> -----Original Message-----
>> From: Action Request System discussion list(ARSList) [mailto:
>> arslist@ARSLIST.ORG] On Behalf Of Antonio Monizza
>> Sent: Tuesday, February 12, 2013 11:11 AM
>> To: arslist@ARSLIST.ORG
>> Subject: Re: Upgrade ARS 7.1 to ARS 7.6.04 SP4 - UNICODE issue
>>
>> ** Hi Kiran,
>>
>> I'm afraid I don't quite understand your suggestions, please note our
>> current frame:
>>
>> given that
>>
>> 1) we need to upgrade from 7.1 to 7.6.04 but we need to stay on our
>> current app server machines and our current db machines
>> 2) our current production ARS 7.1 installation is non UNICODE and current
>> oracle db is UNICODE and everything has always been running fine so far
>>
>> what's puzzling for us is that it seems that the upgrade from 7.1 to
>> 7.6.04 (running the installer) is forcing us to convert our ARS app server
>> installation from non UNICODE to UNICODE, while we would like to avoid that
>> because it would imply extra costs, time, maybe machines etc..
>>
>> Answers from BMC on this topic so far have been that either we convert our
>> oracle instance from UNICODE to non UNICODE to continue with the upgrade,
>> OR we do a new fresh install of ARS 7.6.04 on a new db instance, in
>> UNICODE, and then move objects and data from current servers to new
>> instances/servers.
>>
>> Both ways are hardly viable for us, due to a number of
>> reasons/constraints, that's why we're seeking advise here
>>
>> thanks for your help
>>
>> Kind Regards,
>> Antonello Monizza
>>
>> -----Original Message-----
>> On Tue, Feb 12, 2013 at 4:45 PM, Hullule, Kiran wrote:
>> **
>> 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.
>>
>> -----Original Message-----
>> From: Action Request System discussion list(ARSList) [mailto:
>> arslist@ARSLIST.ORG] On Behalf Of Antonio Monizza
>> Sent: Monday, February 11, 2013 10:39 PM
>> To: arslist@ARSLIST.ORG
>> 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
>>
>>
>> _______________________________________________________________________________
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>> "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"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
