From the bin directory, what do you get if you run
> ./arsystem env | sort
Look at the values of
What is the database character set you see when you run the following
SELECT * FROM NLS_DATABASE_PARAMETERS ;
We currently have a 9.1.02.003 system Red Hat Enterprise Linux Server release 7.2 (Maipo) (Linux 3.10.0-327.36.1.el7.x86_64)
Using NLS_CHARACTERSET US7ASCII
I have not seen your error
From: Action Request System discussion
list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of
I have a customer using what I think of as a first. An Oracle DB with charset
DB_CHAR_SET := (11) iso-8859-15
This is against ARS 9.1.00 201610281101 running on Linux 2.6.32-573.3.1.el6.x86_64 against Oracle 184.108.40.206.0 - 64bit Production.
I issue a Query and the response includes the default Form based list of query fields. There apparently is no way to request none. You can override the default which is the obvious work-around and will be tested shortly. Presumably, you may say the client is using the same character set and get around the issue being thrown by the translation dlls.
In this case the form’s query fields includes those with umlauts. When such a record (containing an umlaut in a form specified query field) is queried, the ARERR 91 occurs. When said query returns records with no umlauts in the generated “short description”, there is no error.
The client (Meta-Update) is running under Windows and is compiled with 9.1 libraries. An 8.1 library version also suffered the same problem. The Linux version has not yet been tested.
I would tend to think it is a client api responsibility – given the plethora of modified character translate open source dlls - but the fact that both the 8.1.2 and 9.1 compiles behave the same way (with changes in these supplied dlls) - makes me want to think of the server.
I guess after spending some hours, I am quite curious. I believe I have an enhancement that may work (to define the character set as above in the ARControl block) and one that most likely will work (to request an override to the form’s configured fields).
1) Anyone ever experienced this? We have not tried the Windows driver at this point.
2) Does anyone NOT use UTF-8 on their DB with anything above 7.6.04?
3) Any comments?
Thanks a bunch in advance for your efforts!
_ARSlist: "Where the Answers Are" and have been for 20 years_