If I reinstall DBD::mysql am I risking breaking all my running scripts that use it? If those scripts fail, my business would suffer a big loss of income. Most of my billable activities are fed by these scripts.

So, you have a broken system, or you may really break your system trying to fix it. In both cases, grab your last verified backup from before the incident and restore it. Problem solved.

If you don't have a backup, then one of these is for you: Kein Backup kein Mitleid / No backup no mercy.

Really, not having a working, verified backup is stupid. Running a business without a working, verified backup is even more stupid. See exhibits A, B, C, D, E.

Alexander

I have backups. Restoring yesterday's backup sacrifices today's billable income. And, I AM up and running ho html at the moment. I wonder if mysql is the fault because it works in one place but not another. That tells me to look to something other than mysql as the cause. I know most people would just rip up their server and reinstall everything instead of thinking the issue through.

UPDATE: For example, in your script that is working, right before the use DBD::mysql statement you could insert:

BEGIN {
  open my $fh, ">", "/tmp/name-of-script.INC.txt";
  printf $fh "%s\n", join "\n", @INC;
}
[download]