Slow ODBC Connection
Pam Ekstrand reported 20-30 second ODBC connect times on Informix 9.40FC4 with -952 password validation errors in the online log before success. Richard Spitz saw the same with the 2.81TC2 driver when the data source user differs from the Windows user, and said later drivers fail with Access 2003. Scottishpoet asked for case numbers; david asked support to test. Unresolved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hello, We have users who have just starting connecting to our informix 9.40FC4 database using informix ODBC drivers and they are experiencing 20 to 30-second connect times. When they try to connect, the online.log shows a -952 message: Password validation for user (xxx) failed. Check for password aging/account lock-out. But the user then does end up connecting successfully to the database. Any thoughts on where I might look for causes? It seems that it must be trying to validate the password in the wrong place first, and then eventually does validate it. Thanks much for any help. Pam Ekstrand Database Administrator OneNeck IT Services 480-315-3087 Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it. sending to informix-list
"Ekstrand, Pam" <Pam.Ekstrand@OneNeck.com> schrieb: >We have users who have just starting connecting to our informix 9.40FC4 >database using informix ODBC drivers and they are experiencing 20 to >30-second connect times. When they try to connect, the online.log shows >a -952 message: > >Password validation for user (xxx) failed. >Check for password aging/account lock-out. > >But the user then does end up connecting successfully to the database. I've been seeing this with Windows clients using the 2.81TC2 ODBC driver, when a system data source is used and username and password entered in the data source properties are different than the user logged into Windows. I assume that the ODBC driver tries the logged on user first. When that fails, it uses the user from the data source. Another problem with the ODBC driver is that when the user specified in the data source changes his password, the driver always uses the old password, and when that fails, the data source properties dialogue comes up and asks for the new password. Somehow I cannot get the driver to store the new password. I am rather dissatisfied with the way IBM supports the ODBC drivers. 2.81TC2 is the latest version that works with Access 2003, all later versions produce errors. This has been discussed in this NG before, but to no avail. Regards, Richard
"I am rather dissatisfied with the way IBM supports the ODBC drivers. 2.81TC2 is the latest version that works with Access 2003, all later versions produce errors. This has been discussed in this NG before, but to no avail. " Hyou or your support provider contact IBM Informix S0pport and reported this as a problem? Case or bug numbers?
"I am rather dissatisfied with the way IBM supports the ODBC drivers. 2.81TC2 is the latest version that works with Access 2003, all later versions produce errors. This has been discussed in this NG before, but to no avail. " Hyou or your support provider contact IBM Informix Support and reported this as a problem? Case or bug numbers?
Hmmm.. has this combination been tested? Can someone in support test it please?