All work
- LP #1041208: DBI and DBD issue on RHEL 4PT-1015Resolved issue: PT-1015
- LP #932327: Quoter (de)serialize UTF8 data fails on CentOS 5.6PT-472Resolved issue: PT-472
- LP #926598: DBD::mysql bug causes pt-upgrade to use wrong precision (M) and scale (D)PT-462Resolved issue: PT-462
- LP #916999: pt-table-checksum error: DBD::mysql::st execute failed: called with 2 bind variables when 6 are neededPT-451Resolved issue: PT-451
- LP #1127450: pt-archiver --bulk-insert may corrupt dataPT-354Resolved issue: PT-354
LP #1041208: DBI and DBD issue on RHEL 4
Description
Environment
Details
Details
Assignee
Reporter
Priority
Activity
lpjirasync January 24, 2018 at 6:53 PM
**Comment from Launchpad by: Daniel Nichter on: 26-10-2012 17:37:50
Since this isn't a bug in any tool, I'm going to close the issue. One quick hack around the problem is to install the tarball, which only warns about dependency problems. Afaik all tools that use DBD::mysql are conditionalized on it. For example, pt-query-digest can run without DBD::mysql even though it can also use it (e.g. --processlist). In any case, there's nothing we can do for RHEL4 support, unless you want to open a support with with Percona, but that will probably be way too cost-prohibative.
lpjirasync January 24, 2018 at 6:53 PM
**Comment from Launchpad by: Brian Fraser on: 18-09-2012 18:58:49
Greg, I really wouldn't know without looking at the actual errors. Can you attach/paste a log here?
lpjirasync January 24, 2018 at 6:53 PM
**Comment from Launchpad by: Greg Lane on: 06-09-2012 12:53:19
I just wanted to update on this issue. I've been able to get perl-5.16.1 installed got cpanm working and DBI installed all using perlbrew. The problem continues to be DBD::mysql. I had to get libmysqlclient installed so that I could use mysql_config. Now getting a error 255. I could do a force but would that work with the toolkit if I did do a force? Also what tools specifically need the DBD::mysql. I didn't necessary expect to use all the tools I just wanted to install all then find the ones I want using my dev and test servers.
lpjirasync January 24, 2018 at 6:53 PM
**Comment from Launchpad by: Brian Fraser on: 27-08-2012 18:13:36
The toolkit doesn't really have a list; We've been meaning to put one together for a while but never actually get around. But this http://www.percona.com/mysql-support/policies/supported-platforms/ is a good guideline; if it's there, we'll try to fix the packaging issues; but on the other hand, if you have a mediumly modern Perl (that is, from this millenium) and some equally non-ancient DBI and DBD::mysql, we will try to fix your bugs (which is what happens with Mac, and to some measure, the BSDs and Solaris).
Good luck with the hurracaine!
lpjirasync January 24, 2018 at 6:53 PM
**Comment from Launchpad by: Greg Lane on: 27-08-2012 12:38:45
Thanks for the response. I will give this a try hopefully sometime this week but right now we got a hurricane bearing down on us so I have to make other preparations for disaster recovery. Is there a place that show is supported? I read through the documentation and didn't find any?
**Reported in Launchpad by Greg Lane last update 26-10-2012 17:38:00
I'm am trying to install the percona toolkit 2.1 onto my dbdev and dbtest servers and I keep getting the warning of the DBI and DBD versions. RHEL 4 only goes up to 1.40 on DBI and DBD isn't even supported on RHEL 4. I would like to test this tool out and then dwindle it down to what I need but I don't want to install with warnings. I'm currently running MySQL 5.1.31 on RHEL 4 and there isn't any input or output files due the fact that it isn't installed.