<![CDATA[Hexagon Safety & Infrastructure - Post to topic GTECH ver 10.04.1906, Oracle 12c r2 and Character Set ]]> http://support.hexagonsafetyinfrastructure.com/infocenter/index?page=home Post to topic GTECH ver 10.04.1906, Oracle 12c r2 and Character Set en Copyright © 2002, 2012, Oracle and/or its affiliates. All rights reserved. Oracle Knowledge Information Manager http://blogs.law.harvard.edu/tech/rss <![CDATA[GTECH ver 10.04.1906, Oracle 12c r2 and Character Set ]]> SMUD upgraded to the 10.04.1906 version of GTECH end of last year.    During the first week of  the project we ran into an issue where the Oracle 12cr2 wanted the character set to be  AL32UTF8  but GTECH currently was on  WE8MSWIN1252 .  After consulting with our Hexagon team who consulted with support, we were told there would be no issues other than the minor ones already found (the oracle dB had a few rows that needed changing for a couple characters and one style rule that needed to be rebuilt).   

We recently found an issue with GNET Viewer and how it uses encyption for passwords.    This new character set changes certain leters in a password to be a space when it encyrpts them and puts them in the stored table.   This causes GNET to get an error, the next time the user tries to log on.    

We've been told it will be fixed in the 10.4.2006 release, and that only a couple of companies are using this character set.  

If you use this GTECH, Oracle 12cr2 and AL32UTF8, please be aware of this issue.   I have attached the error message we get and you can reach out either here or to my email tina.eichele@smud.org

 

]]> 2020-01-24 00:33:34 Etc/GMT