Greetings! Unfortunately, this seems to be a kind of normal: As long as the DB is running, it will keep "leaking" file space . Our virgin 2 GByte DB grew to 400 GB eventually, after running for months. "Shutdown defrag" frees a lot of the claimed file space, but not all and it depends on a restart.
Best solution I found so far is to Extract the DB to script and rebuild the DB from script. This brings the DB reliable down to the actual size and also provides nice backup snapshots in case of corruption. (SHUTDOWN DEFRAG corrupted our databases last year, but seems to have gotten much more stable recently -- just a "gut feeling" though.) Best regards Andreas On Thu, 2021-12-09 at 04:20 -0800, torlpedo wrote: > Hi all, > > Creating a medium sized database (300MB with 800MB disk usage) and > then exiting with SHUTDOWN COMPACT makes the database read-only, > making impossible to modify the data via DML commands. > > I tried opening the DB in read-write mode in the connection string > using ACCESS_MODE_DATA without success. > > Has everybody else encountered the same issue? > > BR, > Ivan > > > > -- > You received this message because you are subscribed to the Google > Groups "H2 Database" group. > To unsubscribe from this group and stop receiving emails from it, > send an email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/h2-database/89d53406-be8e-4a15-9f9e-bf4f24e67092n%40googlegroups.com > . -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/64f82decc38efbee02f754694c02506f2e899581.camel%40manticore-projects.com.
