I've done this using the following steps:
- stop remedy
- convert oracle instance to unicode
- run a set of conversion scripts that convert 8-bit ascii characters
to the target unicode character we want
- run the arserver install and install the unicode arserver against
the upgraded oracle instance
This assumes that there are no 8-bit ascii characters in any of the db
tables that are used to generate workflow/form checksums (e.g., form
name, active link name, etc.)
Axton Grams
On Tue, Oct 14, 2008 at 9:47 AM, Misi Mladoniczky <[EMAIL PROTECTED]> wrote:
> Hi Raido,
>
> I have only done this by:
> 1. installing a new system
> 2. importing the def-file
> 3. copying all the data between old and new server with RRR|Chive (except
> the User-form)
>
>Best Regards - Misi, RRR AB, http://rrr.se
>
>> Hi,
>>
>> Just got a response from BMC that they do not support an upgrade of a
>> non-unicode database to unicode. Just wanted to get some feedback if
>> anyone
>> has ever tried this and if it worked. Are there no other options than
>> rebuilding the system? Any lessons learned would be appreciated.
>>
>> Thanks,
>>
>> Raido
>>
>> ___
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>>
>> --
>> This message was scanned by ESVA and is believed to be clean.
>>
>>
>
> ___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
