Topic: problem with db:migrate involving a table drop MySQL, OSX 10.6 DwC

I have encountered an intermittent problem whereby rake db:migrate:down VERSION=xxx operations return positive output:

==  CreatePages: reverting ====================================================
-- drop_table(:pages)
   -> 0.3532s
==  CreatePages: reverted (0.3533s) ===========================================

...however, upon inspecting with mysql, the table is NOT dropped.  Ultimately, I have to drop the table in mysql.  db:migrate:up for the same version executes successfully. 

It is an intermittent problem in that upon startup, both UP and DOWN operations for the same migration work fine.  It seems to be that only after my system has been on for a few days, this behavior develops.  I solve it by by restarting my OS.

MY QUESTION:  what processes can I bounce on my host that might resolve this bug instead of a full OS restart?

My system details:
OS:  Mac OSX 10.6.8
Ruby:  1.87 (2009-06-12 patchlevel 174)
Gem:  1.8.8
Rails:  3.0.10
MySql:  Ver 14.14 Distrib 5.5.15, for osx10.6 (i386)

Thanks in advance, RoR rocks!