As Misi pointed out there are many ways of managing the data migration between
a non-unicode and unicode system. An in-place conversion of an existing system
cannot be achieved by using the installers. In theory you may be able to
convert the database to unicode at the db level but this leaves you open to
several possible problems. Misi mentioned one - if you have characters in your
data that get converted from single to multiple bytes then you run the risk of
exceeding the field length limits and may lose data. Also, if you have any
such characters in the server metadata (form, field, worflow names/labels etc),
they will get converted but they are often stored in serialised strings which
include length values. For example in this case - 10\5\4\23\4\xäst\12\1 - the
4 before the letters indicates that 4 bytes follow. The ä will take up 2 or
more bytes in a unicode system and therefore the 4 is now incorrect. The
server will throw errors on startup as it parses this data and you may end up
with inaccessible forms or workflow items.
The only supported method of getting from a non-unicode to unicode system is by
migration from one to the other, not by direct conversion.
Mark
________________________________
From: Action Request System discussion list(ARSList) on behalf of Ramy S. Ayoub
Sent: Fri 30/01/2009 21:05
To: arslist@ARSLIST.ORG
Subject: Re: Upgarde ARserver 7.1 patch 5 from non-unicode to unicode
**
Mark - there is no other solution ?
On Fri, Jan 30, 2009 at 10:56 PM, Walters, Mark <mark_walt...@bmc.com> wrote:
You cannot convert an existing non-unicode AR instance to unicode by
running the installer. You need to perform a clean unicode install of ARS and
any applications and then migrate your data and workflow customisations via
export/import, Migrator or equivalent.
Mark
________________________________
From: Action Request System discussion list(ARSList) on behalf of Ramy
S. Ayoub
Sent: Fri 30/01/2009 19:40
To: arslist@ARSLIST.ORG
Subject: Re: Upgarde ARserver 7.1 patch 5 from non-unicode to unicode
**
Hi joe,
Longtime :) , we have our production servers running in non-Unicode as
we receive data from Seibel ebusiness (Remedy Integrated with Seibel through
tibco media ware , so the data become like ??? , so I found out the my arserver
non-Unicode.
So I run my upgrade in the dev environment but didn't give me the
chance to choose the Unicode , its given me direct upgrade.
any solution for this
On Fri, Jan 30, 2009 at 9:26 PM, Joe DeSouza <joe_rem...@yahoo.com>
wrote:
**
Would be useful if you would tell what went wrong when you tried
so someone can help you with what your problem was..
Joe
________________________________
From: Ramy S. Ayoub <ramyay...@gmail.com>
To: arslist@ARSLIST.ORG
Sent: Friday, January 30, 2009 2:23:45 PM
Subject: Upgarde ARserver 7.1 patch 5 from non-unicode to unicode
**
Dear List ,
Tired to upgrade our ARserver from non-Unicode to uni-code, as
we are running SQL-Server 2005
Any suggestion?
Regards,
Ramy Ayoub
__Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers
Are" html___
__Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
html___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
<http://www.arslist.org/>
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
__Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
