Vivek, It sounds to me like you have a character set configuration confusion...
What was the character set of your old Oracle DB? What is the character set of your new Oracle 12C DB? If they don't match, how did you migrate the data between them to make sure the character sets were converted properly for all stored data? What was the configuration setting of the AR System server for character set on the 7.1 instance? What is the configuration setting of the AR System server for character set on the 9 instance? The AR System DOES NOT have to match the DB character set. However, the AR System character set is the key to what the client interaction is. What you are seeing is typical if for example you have the character set configured for Latin1 but Swedish is actually a Latin2 character set language so the system doesn't understand the characters that are not part of the Latin1 (basically English with a few extras) character set. If the DB is configured with the Unicode Character Set, it supports all languages. You can configure AR System 9 with the Unicode character set too. Then mixing and matching languages is just fine. You can change the AR System character set and restart the server to have it take effect. If the DB character set has to be changed, that is a major production as the data has to be reprocessed. NOTE: If you had a Unicode DB but a Latin1 AR System, any records created during the time of mismatch may be incorrect in the DB and those you have to correct manually by fixing the text. That is because the data would not have been encoded correctly as the character set mappings between AR System and the DB were occurring while you entered data that was not understood by the AR System character set. Hopefully, not too confusing and hopefully a pointer to the direction to look. One more note about the Windows User Tool client that could be the issue: The Windows User Tool DOES NOT support Unicode. You can configure a given instance with a character set. It will show all entries in that character set correctly but languages in other character sets will not show correctly. But, those same records would show correctly in another User Tool configured with the appropriate character set for the entries. There is no solution for this. The Windows User Tool can only be in one character set. The mid-tier on the other hand works in the Unicode character set so can mix and match languages without issue (assuming the underlying environments are Unicode otherwise it is restricted to the character set of the underlying server). Lots of specific details, but again, hopefully, this helps point to what may be wrong in your environment. Doug Mueller -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of VIVEK GARG Sent: Sunday, April 24, 2016 7:48 PM To: [email protected] Subject: Issues with country specific characters on User tool 7.1 in Remedy upgrade from 7.1 to 9 Hi, While trying to upgrade Remedy 7.1 to Remedy 9, we have first installed oracle 12c, then migrated entire production data from Remedy 7.1 on oracle 12c, then installed Remedy 8.1 and then we did a installation of remedy 9. Things working fine for us but we are only stuck with one issue of country specific characters while accessing Remedy through user tool 7.1. for e.g. When we save records in Swedish language, table records display those records in some strange characters. Please let me know if anyone knows how to fix this. Thanks, Vivek _______________________________________________________________________________ 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"
