[Internetcafe]

I'm hoping to move to a VPS and the tech team at my new host have been attempting to restore my existing database but are continuously finding a database error created by :-

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

I've checked all templates and removed a couple of places I found the '<br /> .. re-submitted the database for restore but the error continues to create a problem.

How can I run a query to locate the '<br /> within the database ?

Thanks guys

[Farcaster]

You're probably going to find <br/> all over the place, actually. In the native format of templates and the cached page text from posts, etc, etc. If the import is failing though, they should be able to identify the particular insert statement that caused the failure though. I'm presuming this is coming from a mysqldump, of course, and not that it has been exported to a flat file. Once you have the exact error and the offending insert statement, that would give us enough information to help you identify what row in which table is causing the problem.

[snakes1100]

Sounds like a character collation issue if they cant import the db because of the br tags.

[Internetcafe]

Its not a <br /> problem .. notice the hyphen '<br />

[Farcaster]

Originally Posted by Internetcafe

Its not a <br /> problem .. notice the hyphen '<br />

Well, if there is an apostrphe in your data, it is most certainly escaped when being exported using the mysqldump. My previous statement stands. You need to find what row and what table this error is being caused on. They should be able to tell you that.

[SEOvB]

Originally Posted by Farcaster

Well, if there is an apostrphe in your data, it is most certainly escaped when being exported using the mysqldump. My previous statement stands. You need to find what row and what table this error is being caused on. They should be able to tell you that.

If that was the case wouldn't almost all database dumps and restores fail as most have ' in them?

[Internetcafe]

Tried again last night and techs report :-

ERROR 1064 (42000) at line 252033: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '<br /> <b>Fatal error</b>: Maximum execution time of 30 seconds exceeded in <b>' at line 1

Grrrrrr

[SEOvB]

You need to increase your max execution time in php.ini

Also backingup/restoring databases via a web browser isn't recommended. You should use SSH when possible

[Marco van Herwaarden]

The only reliable method of backing up and restoring a database is with shell access via telnet or ssh. This is because backing up with a PHP script like that in the Admin CP or phpMyAdmin can result in PHP timeouts errors and an incomplete backup file. Please see the instructions here:

Backup:
http://www.vbulletin.com/docs/html/m...nce_ssh_backup

Restore:
http://www.vbulletin.com/docs/html/m...ce_ssh_restore

P.S. If you don't have shell access, some people have also reported success with these scripts:

MySQLDumper:
http://www.mysqldumper.de/en/index.php

MySQLHotxcopy:
http://www.vbulletin.com/forum/showt...t=mysqlhotcopy

Bigdump:
http://www.ozerov.de/bigdump.php