Import SQL limit


I try to import a platform gzip dump database on a new platform project with this command :

gunzip < dump/dump.gz | platform db:sql

and this is my error :

ERROR 1114 (HY000) at line 442: The table 'user' is full

But when I check the db space I have :

| Allocated disk | Estimated usage | % used |
| 4.0 GiB | 250.8 MiB | ~ 6% |

The plan of my new project is the same than the source dump project (5Go)

Is seems stop when the table reach 250mo (the same value of innodb_buffer_pool_size, but I haven’t the permission to change this value)

How can I import the dump without this error ?


Hello ben-platform, how are you?
I wish you a happy new year.

Please, could you verify the size of the database size?
The file is on .platform/services.yaml

It will look like this:

    type: oracle-mysql:8.0
    disk: 1024

Be aware that when deploying your project, the sum of all disk keys defined in and .platform/services.yaml must be equal or less than the plan storage size . For example, if your plan storage size is 5 GB, you can assign:

  • 2 GB to your application, 3 GB to your database
  • 1 GB to your application, 4 GB to your database
  • 1 GB to your application, 1 GB to your database, 3 GB to your Elasticsearch service
  • etc.

The ref:

Hi Otavio,

I m fine thanks, happy new year too :wink:

I think the datasize is correct :

In my

disk: 1024

and in my service.yml

    type: mariadb:10.4
    disk: 4096

The gzip dump size is about 300mo (on a mount ) and unzip size is about 3GO (but not present on a server)


Yeap, it looks, right.
Could you fire a ticket in support?
Therefore, you can provide a project where the support team can go deep on it.

Yes I 've already create a ticket yesterday but unfortunately I haven’t got answer