Need to restore database

[stevenrwoolley]

Need to restore database. I am trying to restore my database and for some reason the page times out. Is it possible that I have the file is too big?

db_steven_otp-20060122123650.sql 01/22/2006 12:36:57 12,473,260 bytes

 

I have been using the admin section on the oscommerce site and the myphpadmin but not seeing any changes. What do you think, any suggestions would be great.

 

Thank You,

 

Steven R. Wooley

[AlanR]

You're trying to upload that from your local PC?

[stevenrwoolley]

At first iIwas uploading from the backup folder in the admin section, Now I just broke up the file into 4 sections and try to upload it from my pc using phpmyadmin and still did not work, at least i did not see any changes to the site, but i did not get any errors. ???

[AlanR]

Zip it up. Database backups are perfect candidates for compression, there are tons of repetitive characters and statements. You'll find it ends up about 15% of the original size(gzip is even better). Then import it into phpMyAdmin, it understands Zip format.

 

Also if you have your own copy of phpMyAdmin running you can define server import and export directories and even define them to be the osC backups directory.

 

If you don't have your own copy of phpMyAdmin running you can download it from phpmyadmin.net.

[stevenrwoolley]

When I use winzip and upload the file using myphpadmin I get several errors

 

"There is a chance that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if the parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:

----BEGIN CUT----

eNpzDQryD7JScDZUcDZS8HH1s1IwUjBWMLQ05woOAYozc3E5hwVbKah4plgpFBfmFCQWFacW6eVk

JukVZBTolCkY6RkZKxgZGJjoG1joG1gqGBhaGRlZmVoq5KTmWiq4VhQoqHD5VgYH+lgpmOgZ6BmZ

6RaXJOalJBal6Obkp3OFBgcp+AfrKDi6u/qF6CiEuQLtDM/MU/B0VTDTM+AK8HUEOkgPyNQtyDHi

CvAIACnR8Q8GmWasZ2io4JOZV1rB5ePo526lkJqnm1mcr2thYWqpa8gFtjPAm5lFhIGBgYOhYYqZ

SX735Ly76VwMa4L3MSgARVOS4otLUstS8+LzSwp0gb4wMzA0MjI0MjYzNdAD+vbN399Ft09M0uf6

v1+tsDS/xPqctULS+Tfb/D0MVgXsyHxrm67RuWmLT6yY5823fZ0BAUK6hbMgCk1Vruatb/817+Nq

br1QBzGOnVzMQqsWc030FDhzKj7WaPMmo//Tt8bI68jLLVs9+2Vf6T+L2IjFT4Vrk7+WC1stPTPf

bPPTpL/b/6fezTfrr35/r/bvr6tx6/IfAQCy85MI

----END CUT----

----BEGIN RAW----

 

ERROR: C1 C2 LEN: 2 3 197

STR:

 

CVS: $Id: sqlparser.lib.php,v 2.23 2004/08/09 01:22:59 lem9 Exp $

MySQL: 4.0.26-standard-log

USR OS, AGENT, VER: Win IE 6.0

PMA: 2.6.0-pl2

PHP VER,OS: 4.3.11 Linux

LANG: en-iso-8859-1

SQL: PK??64o??n?g

?S? db_steven_otp-20060122123650.sql???r?Ȓ/

??"?; b???OH0?P?i?=g(???L]I?펉PP-q?"5$?n??????.U@?

??

?I??_]2??2???\,?????u?8]X??}c?w:?̟6??b???e?o6?{??}???^?o?

----END RAW----

SQL-query:

 

PK??64o??n?g ?S? db_steven_otp-20060122123650.sql???r?Ȓ/ ??"?; b???OH0?P?i?=g(???L]I?펉PP-q?"5$?n?????? .U@? ?? ?I??_]2??2???\,?????u?8]X??}c?w:?̟6??b???e?o6?{??}???^?o?

MySQL said:

 

#1064 - 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 'PK' at line 1 "

 

I am compleatly lost now.

[AlanR]

Does your phpMyAdmin have the notice...

 

Imported file compression will be automatically detected from: None, gzip, bzip2, zip ?

 

The lines you posted look like junk.

 

You may have to resort to importing it in chunks, at least that way you can check the tables visually for garbage.

 

I always move large files and folders around in compressed form, it cuts down on errors and you can always do an MD5 to check for file integrity.

[stevenrwoolley]

Yes, it has autodetect, none, gzip and bzip. I used autodetect. I also split up the file into 4 smaller files and it seemed to make no difference. I did however not get any errors, and it did not time out, but I can see no changes to the database. The only backup that seems to work is one that is over two months old and I have made a few changes to the database since then.

[AlanR]

The only backup that seems to work is one that is over two months old and I have made a few changes to the database since then.

Yeah, maybe the newer ones are corrupted. Like I said you can open them up in a text editor and quickly scroll through them. Errors usually jump right out at you. Always move them around in compressed form if you can. It's usually in transmission of ascii files that characters become garbled.

 

You should have the gzip option available from within osC.