Unicode is only in our data. We had a unicode database, then an outsourcer dba created our new db in '09 to be non-unicode but this went unnoticed for a year. We have a China office and they didn't mention their 'data' characters were not appearing correctly, so in worklog type fields we have ??? where unicode type characters were. We need to go back to unicode for our data.
I don't use unicode type characters in the objects so that should not be an issue. The dba already did a unicode conversion on the db side and there were only 160 records affected and we are choosing just to replace extraneous characters with an x. It works for us in the situations where that data exists. So from a unicode perspective I think we're ok. My understanding, although it could be in error, is that ARS isn't specified as unicode per se, it takes on whatever oracle is. We just spent time on the phone with Support and we're going to try this approach this afternoon. Install empty oracle 11g db on new linux server 10g client Install ARS 7.5P4 Export/import the oracle database (dba oracle function) In ar.conf change db path from ARSYSTEM to ARSYSTEM1 Test to confirm we can connect via Remedy Then do the 8.1 install Slightly different than our first two attempts, will let you know how it goes! Thanks for all the info ... Susan On Tue, Jun 25, 2013 at 1:42 PM, Misi Mladoniczky <[email protected]> wrote: > Hi, > > Mark is right. You need to do the Unicode conversion through the API and > through importing def-files. > > If you have no Unicode-characters in your system whatsoever, it might work > with a straight database conversion. > > The problem is that the AR System in most cases counts Bytes and not > Characters, which really makes things confusing. > > My RRR|DefDiff utility actually do compare a non-unicode-def-file with a > unicode-def-file, but I had to do some changes in the byte-counts of > character-strings to get it working... > > Best Regards - Misi, RRR AB, http://rrr.se > > > Well, and that's because we put the new 11g database right on the linux > > server and the dba did the 10g to 11g conversion at that time. Maybe he > > needed to that unicode conversion in a separate place first. > > > > On Tue, Jun 25, 2013 at 11:17 AM, Susan Palmer <[email protected] > >wrote: > > > >> Hi Mark, > >> > >> The unicode conversion happened separately from our steps. In our steps > >> we were using the unicode database. > >> > >> Thanks, > >> Susan > >> > >> On Tue, Jun 25, 2013 at 11:12 AM, Walters, Mark > >> <[email protected]>wrote: > >> > >>> ** > >>> > >>> You can’t convert a non-Unicode ARS database to a Unicode one – which > >>> is > >>> what I think you’re suggesting using the steps below. You’ll need a > >>> clean > >>> install of 8.1/Unicode and some sort of migration of data. If you > check > >>> back through the archives there are various threads which go into the > >>> details of why the conversion is not likely to work.**** > >>> > >>> ** ** > >>> > >>> Mark**** > >>> > >>> ** ** > >>> > >>> *From:* Action Request System discussion list(ARSList) [mailto: > >>> [email protected]] *On Behalf Of *Susan Palmer > >>> *Sent:* 25 June 2013 15:04 > >>> *To:* [email protected] > >>> *Subject:* Moving from Solaris to Linux**** > >>> > >>> ** ** > >>> > >>> ** **** > >>> > >>> Hi Everyone,**** > >>> > >>> **** > >>> > >>> Our current environment is Solaris 10 with Oracle 10g non-unicode and > ARS > >>> 7.5P4. We are trying to move to a Linux CentOS release 6.4 Final (Red > Hat > >>> Linus 6.4) with Oracle 11g unicode and ARS 8.1. These are VM > instances.* > >>> *** > >>> > >>> **** > >>> > >>> We are finding the Linux box does want Oracle 10g. Since we are moving > >>> to a new server we wanted to do fresh installs at the 10g level and do > an > >>> import of our database, then proceed with the oracle upgrade and ARS > >>> upgrade.**** > >>> > >>> **** > >>> > >>> So we thought we would start with an 11g db on the linux box and go > from > >>> there but when we tried the 7.5 install it said it wouldn't work on > 11g. > >>> When I check the compatibility chart it indicated 10g or higher for > 7.5.* > >>> *** > >>> > >>> **** > >>> > >>> So the basic steps we'd like to do:**** > >>> > >>> Install 11g on the linux server.**** > >>> > >>> Export 10g from current server and import it into 11g.**** > >>> > >>> Install ARS 7.5 (we received an error at this point saying it wouldn't > >>> work on 11g ???)**** > >>> > >>> Install ARS 8.1**** > >>> > >>> **** > >>> > >>> Has anyone done something similar? Is there something wrong with our > >>> approach?**** > >>> > >>> **** > >>> > >>> Appreciate any feedback you can provide.**** > >>> > >>> **** > >>> > >>> Thanks,**** > >>> > >>> Susan**** > >>> > >>> **** > >>> > >>> Susan Palmer**** > >>> > >>> ShopperTrak**** > >>> > >>> 233 S Wacker Drive 41st floor**** > >>> > >>> Chicago, IL 60606**** > >>> > >>> 312-529-5325**** > >>> > >>> [email protected]**** > >>> > >>> **** > >>> > >>> _ARSlist: "Where the Answers Are" and have been for 20 years_ **** > >>> _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" > > > > > _______________________________________________________________________________ > 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"
