Re: MySQL 4.1+ Password Incompatibility

On Thu, 25 Aug 2005 09:00:37 -0700 (PDT), William R. Mussatto wrote: Hi William > Does anyone know of activestate's DBD::mysql has been rebuilt yet? > Bumped my forhead against that problem awhile back. Thanks You could try here http://cpan.uwinnipeg.ca/search?query=DBD%3A%3Amysql&mode=module

Re: DBI/Sybase problem

On Wed, 2005-08-24 at 14:09 -0400, Anderson, James H (Company IT) wrote: > For a given server, dbconnect works in most cases, but fails for a > specific userid/pswd. However, using isql I can connect to the server > using the userid/pswd that hangs when used in DBI. Off hand I don't see why that w

RE: Connect failure: OCIEnvNlsCreate (check ORACLE_HOME and NLSsettings etc.)

Victor, Yes, this all makes sense - specifically your find for setting LD_LIBRARY_PATH. That sentence triggered a recollection for me. This was the issue I was refering to a few months ago. As for how to set these vars for the httpd process owner, I think you will need to do this in a .conf

DBD: db_login/SQLConnect err=-1 with unixODBC/FreeTDS on Linux

Hello, I am using DBD:ODBC (unixODBC/FreeTDS) with Perl 5.8.5 on Solaris and I am able to connect to a MS SQL 2000 database successfully. I am now trying to migrate the app to RHEL3 and for some reason I cannot connect to the same SQL db. I can connect to the MS SQL db using the isql tool. I ru

RE: Connect failure: OCIEnvNlsCreate (check ORACLE_HOME and NLS settings etc.)

Hi Ron, Thanks for the reply. I've done another search of the group but not found anything specifically permissions-related. I assume you mean the permissions of the owner of the httpd processes (on this box, 'nobody') ..? I did pick up a suggestion that the %ENV settings might need to be done at

Re: MySQL 4.1+ Password Incompatibility

Paul DuBois said: > You'll need to rebuild DBD::mysql linked against a 4.1 MySQL client > library. > > > On 8/25/05 8:38, "Shawn Iwinski (siwinski)" <[EMAIL PROTECTED]> wrote: > >> I'm having trouble getting DBI connect to a MySQL 4.1+ server. I have >> to use MySQL's OLD_PASSWORD to set the passw

MySQL 4.1+ Password Incompatibility

I'm having trouble getting DBI connect to a MySQL 4.1+ server. I have to use MySQL's OLD_PASSWORD to set the password on the server in order for DBI to connect. This means less secure passwords for MySQL -- 41 byte hashes instead of 45 byte hashes. Could someone assist in helping me connect to M

Re: MySQL 4.1+ Password Incompatibility

You'll need to rebuild DBD::mysql linked against a 4.1 MySQL client library. On 8/25/05 8:38, "Shawn Iwinski (siwinski)" <[EMAIL PROTECTED]> wrote: > I'm having trouble getting DBI connect to a MySQL 4.1+ server. I have > to use MySQL's OLD_PASSWORD to set the password on the server in order >

Re: MySQL 4.1+ Password Incompatibility

Shawn Iwinski (siwinski) wrote: I'm having trouble getting DBI connect to a MySQL 4.1+ server. I have to use MySQL's OLD_PASSWORD to set the password on the server in order This isn't a DBI issue, the problem is that the passwords in your privilage tables (IE from 3.x or 4.0) are not compa

RE: Connect failure: OCIEnvNlsCreate (check ORACLE_HOME and NLS settings etc.)

Victor, I believe this is a permissions issue. There was a posting to this group a few months ago that was very similar in nature. Look around the archives for it. - Ron Reidy Lead DBA Array BioPharma, Inc. -Original Message- From: Victor Churchill [mailto:[EMAIL PROT

Connect failure: OCIEnvNlsCreate (check ORACLE_HOME and NLS settings etc.)

Hello all, I've searched and found a few references to the above error, but none that seems to suit my situation. I wonder if anyone here may have an idea of what I should look for next... I have a pretty straightforward setup (I hope!): Database server on box "DB" : Oracle Database 10g Relea