Having troubles when installing threw phpMyAdmin.
Downloaded the SEDB31d.zip and attempted to import a single SQL file.
Tried accepting both character sets, Latin1 and ASCII.
I install SQL files at least one a week and never receive timeout errors like this one.
Am I missing something?
Possibly a SQL compatibility mode option?
ANSI
DB2
MAXDB
MYSQL323
MYSQL40
MSSQL
ORACLE
TRADITIONAL
phpMyAdmin
Moderator: SEOW Developers
-
IV/JG7_4Shades
- Posts: 2203
- Joined: Mon 08 Jan 2007 11:10 pm
- Location: Perth, Western Australia
Hi Grams,
It depends on which .sql file you are trying to load. The SEDB "Reference" file is very large and not for general use. The other ones are trimmed down databases specific for individual maps, but they are still pretty big. Perhaps Tunis is the smallest and simplest. If you can increase your query memory size and timeout, that would help.
I know that lots of people use MySQL command line to do this, and other people use phpMyAdmin. But others use GUI tools like SQLYog or Navicat.
Cheers,
4Shades
It depends on which .sql file you are trying to load. The SEDB "Reference" file is very large and not for general use. The other ones are trimmed down databases specific for individual maps, but they are still pretty big. Perhaps Tunis is the smallest and simplest. If you can increase your query memory size and timeout, that would help.
I know that lots of people use MySQL command line to do this, and other people use phpMyAdmin. But others use GUI tools like SQLYog or Navicat.
Cheers,
4Shades
IV/JG7_4Shades
SEOW Developer
SEOW Developer
MySQL client version: 4.1.22
MySQL charset: UTF-8 Unicode (utf8)
phpMyAdmin - 2.11.4
Importing file:
SEDB31d_TunisLite.sql
"Fatal error: Maximum execution time of 300 seconds exceeded"
89 tables are created.
Searched server variables and settings for values of "300".
delayed insert timeout = 300
innodb open files = 300
key cache age threshold = 300
It seems to be a simple time out issue.
Like I said in the last post. I have never seen this error before.
And don't like messing with the mySQL settings without knowing first.
Any more help would be great.
MySQL charset: UTF-8 Unicode (utf8)
phpMyAdmin - 2.11.4
Importing file:
SEDB31d_TunisLite.sql
"Fatal error: Maximum execution time of 300 seconds exceeded"
89 tables are created.
Searched server variables and settings for values of "300".
delayed insert timeout = 300
innodb open files = 300
key cache age threshold = 300
It seems to be a simple time out issue.
Like I said in the last post. I have never seen this error before.
And don't like messing with the mySQL settings without knowing first.
Any more help would be great.
-
IV/JG7_4Shades
- Posts: 2203
- Joined: Mon 08 Jan 2007 11:10 pm
- Location: Perth, Western Australia
Hi Grams,
I think you might increase the delayed insert timeout to 500 seconds. Make sure that your MySQL server supports InnoDB tables, which are used by SEOW. The MySQL version (4.1.22) is pretty old now, but SEOW should still work with it.
Do you have a reasonably fast network connection to the MySQL server?
Cheers,
4Shades
I think you might increase the delayed insert timeout to 500 seconds. Make sure that your MySQL server supports InnoDB tables, which are used by SEOW. The MySQL version (4.1.22) is pretty old now, but SEOW should still work with it.
Do you have a reasonably fast network connection to the MySQL server?
Cheers,
4Shades
IV/JG7_4Shades
SEOW Developer
SEOW Developer