I upgraded to FC9 due to sequencial scan errors on FC6. I am now
getting OBDC errors when trying to connect. Does anyone have any
ideas?

Thanks!

Scott

ERROR [HY000] [Informix][Informix ODBC Driver][Informix]Database
locale information mismatch. ERROR [IM006] [Microsoft][ODBC Driver
Manager] Driver's SQLSetConnectAttr failed ERROR [HY000] [Informix]
[Informix ODBC Driver][Informix]Database locale information mismatch

Sending Mail through wrote:
> I upgraded to FC9 due to sequencial scan errors on FC6. I am now
> getting OBDC errors when trying to connect. Does anyone have any
> ideas?
>
> Thanks!
>
> Scott
>
> ERROR [HY000] [Informix][Informix ODBC Driver][Informix]Database
> locale information mismatch. ERROR [IM006] [Microsoft][ODBC Driver
> Manager] Driver's SQLSetConnectAttr failed ERROR [HY000] [Informix]
> [Informix ODBC Driver][Informix]Database locale information mismatch
>

Yes.
Later IDS versions (9.x, 10.x and 11.x) are sensitive about accepting
connections from clients when the DB_LOCALE information is not correct.
Please check to see your database creation locale, and configure your DB_LOCALE
variable on the client side with the same settings.

Many times the clients (ODBC, .NET etc) used the windows locale which is not
the default DB locale if your DB server is Unix. Later ClientSDK will check and
use the DB locale, but previous versions were not very smart and used
en_US.CP12522. You can change this on your client settings (either DSN
datasource or connection string).

Be alert to another issue that can arise from this:
The older configurations (wrong DB_LOCALE) could cause invalid characters to
get into the DB. If you have the same values in DB_LOCALE and CLIENT_LOCALE
there will be no codeset conversion. This means that in previous setups you
could end up with CP1252 characters in a en_US.819 DB...
With the new settings you may see error -11007 (or similar) if the queries find
this invalid characters in the DB result sets...

Further info:
1- There is an environment variable that you can set up in your DB server
environment that will maintain the previous (wrong) behavior... I would advise
against it, but you can consider it as a temporary workaround

2- Latest (FC7) version in the v10 line has a client variable that will change
the codeset conversion rules... In previous versions you could get "corrupt"
data from conversion made in codesets. By "corruption" I mean the fact that
some characters that don't exist in en_US.819 and only in CP1252 could be
converted to an "unknown" character. You would never be able to reverse the
conversion. Latest versions will raise an error in these situations, and the
mentioned client side variable will once again use the old (wrong) behavior.

If you need further info please get back here... I would love to write an
article for the blog about this but I really don't have time right now...


Regards.

--
Fernando Nunes
Portugal

http://informix-technology.blogspot.com
My email works... but I don't check it frequently...

Fernando Nunes" <spam@domus.online.pt> wrote in message
news:fg2b38$u9m$1@aioe.org...
> Sending Mail through wrote:
>> I upgraded to FC9 due to sequencial scan errors on FC6. I am now
>> getting OBDC errors when trying to connect. Does anyone have any
>> ideas?
>>
>> Thanks!
>>
>> Scott
>>
>> ERROR [HY000] [Informix][Informix ODBC Driver][Informix]Database
>> locale information mismatch. ERROR [IM006] [Microsoft][ODBC Driver
>> Manager] Driver's SQLSetConnectAttr failed ERROR [HY000] [Informix]
>> [Informix ODBC Driver][Informix]Database locale information mismatch
>>
>
> Yes.
> Later IDS versions (9.x, 10.x and 11.x) are sensitive about accepting
> connections from clients when the DB_LOCALE information is not correct.
> Please check to see your database creation locale, and configure your
> DB_LOCALE variable on the client side with the same settings.
....
> If you need further info please get back here... I would love to write an
> article for the blog about this but I really don't have time right now...


Guy Bowerman already did write such an article in his blog.

Neil Truby wrote:
> Fernando Nunes" <spam@domus.online.pt> wrote in message
> news:fg2b38$u9m$1@aioe.org...
>> Sending Mail through wrote:
>>> I upgraded to FC9 due to sequencial scan errors on FC6. I am now
>>> getting OBDC errors when trying to connect. Does anyone have any
>>> ideas?
>>>
>>> Thanks!
>>>
>>> Scott
>>>
>>> ERROR [HY000] [Informix][Informix ODBC Driver][Informix]Database
>>> locale information mismatch. ERROR [IM006] [Microsoft][ODBC Driver
>>> Manager] Driver's SQLSetConnectAttr failed ERROR [HY000] [Informix]
>>> [Informix ODBC Driver][Informix]Database locale information mismatch
>>>
>> Yes.
>> Later IDS versions (9.x, 10.x and 11.x) are sensitive about accepting
>> connections from clients when the DB_LOCALE information is not correct.
>> Please check to see your database creation locale, and configure your
>> DB_LOCALE variable on the client side with the same settings.
> ...
>> If you need further info please get back here... I would love to write an
>> article for the blog about this but I really don't have time right now...
>
>
> Guy Bowerman already did write such an article in his blog.
>
>

Not quite... By no means I want to take his deserved credits, but there is more
to it than what Guy wrote...
Believe me... I should know as I was responsible for the test cases for the
latest bug/feature

Regards.

--
Fernando Nunes
Portugal

http://informix-technology.blogspot.com
My email works... but I don't check it frequently...