Hi,

1. Use the API to transfer both DATA and your Application (DEF-files).

2. When transering data through the API, it is good to make set Client Charset
to UTF-8, otherwise your data might get corrupted.

I have typically used RRR|Chive to do this. Just add a parameter in the
rrrchive config file saying clientcharset=UTF-8.

The problem you could encounter is that wide characters take up more space.
For example a Swedish character "Å" might take two bytes in the database. So
some strings might not fit in the Unicode system even thought it fit in the
old system. In this case you can increase the size of these fields, or
truncate your data.

If you use a good API-program for the transer, you will be notified on errors
where the data did not fit. Which record it is, and which field.

        Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)

Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13):
* 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.

> Hello All,
>
> We have to test the nonunicode to uncode migration of Remedy ARS 7.6.
>
> Please sahre the possible scenarios that should be considered. or Some
> special cases that needs to be tested both from client and web.
>
> OS: windows
> Database:Oracle
> Remedy ARS 7.6
>
> regards
> Sahil
>
> _______________________________________________________________________________
> 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"

Reply via email to