Hello - Please ecuse my numbmess on this one

I have been running a site at EV1 for 5+ years. It was time to get a new rack, and I was excited to get upgraded. That has now turned to frustration with a MySQL issue I am experiencing

I am currently on a Ensim 3.1 seup with MySQL at mysql-3.23.41-1 (yes, I read the other thread here about being beaten with a stick)

I got one of the new conroe 3040's with Ensim Pro X (10.1) and MySql mysql-4.1.20-2.RHEL4.1 and I am doing pre-migration testing to get the plans fleshed out for the live migration.

I first found a the ensim backup and restore tool someone here so helpfully provided, and with the exception of a few small changes, it worked, except I did not see (until it was too late) that a call in the restore3.1.php called a python2.2 exec instead of the new python2.3 exec, so as it built the sites, it failed to do the data base restores.

I thought, no matter, I can create them and restore using a more current backup (today's) any way. That's when I started getting into issues. For one, I couldn't create data bases as root any more (saw the thread on perms, but hesitated, trying to undertand the CORRECT process). So I created the data bases using the site admin control screen in Ensim(DB Prefix yadatest_com, and DBname VB35).

Then I was unable to restore them from shell using the site's MySQL Admin ID. The attempt resulted in an access error;


I went thru MyPhpAdmin and granted ALL on the yada id, retried, no joy. I was ONLY able to restore them from shell using MySql "root" access.

But then I knew I made a wrong turn, as vbulletin(3.5) cannot access the newly restored data base. I did make the necessary adjustments to Vbull's config.php;

• addition of the data base prefix
  
• the correct data base name.
  
• verified data base user name and password were unchanged from previous rack

Specific error;


So now, I am quite confused. Any ideas or sugestions, or gentle prods with an electrical instrument to get me moving in the right direction again?

Thanks

Never Mind.. I sorted it.. So silly.

The data base name prefix specified in the siteadmin panel has nothiong to do with vbulletins "table prefix" - One simply specifes the table name in it's entireity(data base prefix+tablename) and leave the prefix in the config.php alone.