• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

phpmyadmin export database problem

D

drogatoo

Guest
Hy,
one of my clients is trying to export a database that has a table of 31M in size, but he can't.When he tries to export it to a file he receives a file of 0 bytes in size.Also when he exports it in plain text in the browser he gets a blank page.
I've managed to dump it in the shell but i cannot give the client access to the shell, he must do it through phpmyadmin.
I've tried several tweaks to the php.ini but with no result.
Here are the settings that I've tried to modify from php.ini
max_execution_time = 30
max_input_time = 60
memory_limit = 50M
post_max_size = 8M
upload_max_filesize = 50M
 
yes, there is such issue with large databases,
this has been already reported to Plesk developers, but no update/workaround yet
i hope this will be fixed soon in future Plesk versions.
 
Yeah, i hope so!

Mine is 22mb gziped and 100mb as .sql(txt) . :)

Waiting for an update!

This is urgent... :)
 
Here my fix:

1. Open your plesk php.ini (my plesk php.ini located: /usr/local/psa/admin/conf/php.ini)
2. Find memory_limit change to example: memory_limit = 256M
3. Stop and start psa services: /etc/init.d/psa stopall , /etc/init.d/psa start


i have centos linux 5.1, plesk 8.3 linux, 4096 DDRII ram, core duo 2 cpu..
 
Thanks that did the trick for me, I can export the database now.Never thought that the value should be that large.
 
Back
Top