Error on DB import with Adminer

[kerns]

What issue or error are you experiencing?

Error on import of db (~ 350mb in size)

Fatal error : Allowed memory size of 268435456 bytes exhausted (tried to allocate 321598096 bytes) in /Applications/Local.app/Contents/Resources/extraResources/adminer/adminer.php on line 100

---

Is this an issue with memory allocation, and if so, how can I address it? Thank you!

---

System Details

• Local Version:
  Version 9.0.2+6676

• Operating System (OS) and OS version:
  macOS Sonoma 14.2.1

[kerns]

For further context…

[Nick-B]

Hi @kerns

You should still be able to manually import the database as a workaround using the steps here:

PHP memory limit error when importing a SQL file in Adminer

That error is basically saying that PHP (the underlying software running Adminer) didn’t have enough memory to handle the upload of that SQL file. Are you able to import the site by creating a zip of the sql file along with the wp-content folder? Something like what’s outlined in the “Restoring From Only Local Site files” section of this help doc: https://localwp.com/help-docs/how-to-import-a-wordpress-site-into-local/ If you do need to manually import the database of a large SQL file, I rec…

[Nick-B]

Hi @kerns

Another update here as I have been working with another user getting the same error. More details and a feature request to follow here:

Increase memory limit of mysql server beyond 256M

Hi @hyperterry I checked with the Devs on this and the value for adminer memory is actually hard coded. I spun up a feature request here to make this an editable value for users. For now, the only workaround will be the manual import steps, but please vote, comment, and follow along here for future updates.

[kerns]

Thanks, @Nick-B – but why isn’t it possible to edit a file somewhere as a quick fix? I will try the other method suggested but I’m just curious.

[Nick-B]

It’s just not something that we have made publically accessible yet, so that’s why we created the feature request

Similar to PHP memory, we’d rather not just “blanket raise” the value in Local to something super high but give the ability to users to raise as they need down the road.

[kerns]

Thx @Nick-B – but as a temporary workaround, is it not possible to find an ini or config file and manually edit it? Is it compiled somehow in a way that makes it inaccessible? I will try the other method …but I am not sure it will work.

[Nick-B]

Yes that is the goal of the feature request is to make it publically accessible because currently it is not unlike the PHP memory which you can access and edit.