Re: Indexes grow over time insanly big and can't be shrunk

Hi Gerrit, I don't have a theory about what caused this problem. Maybe COMPRESS_TABLE() has a serious bug. A couple questions: Q1) Do you have the results of SPACE_TABLE() for this situation? Q2) What value did you specify for the SEQUENTIAL argument of COMPRESS_TABLE()? Q3) Other than COM

Re: database in a jar : conglomerate does not exists

Thanks for letting us know how you resolved the issue. On 9/14/20 11:08 PM, RAPPAZ Francois wrote: Thank you all At the end - taking care for the version of derby to be the same when I build the database or when I search - deleting the old database (corrupted) and starting with a new one, the

Indexes grow over time insanly big and can't be shrunk

Hello everyone, we use Apache Derby v10.14.2.0 in our software and now have a problem with an installation. Every night we perform a compact on all tables - at least the ones which can be shrunk (SYSCS_DIAG.SPACE_TABLE() and SYSCS_UTIL.SYSCS_COMPRESS_TABLE(String, String, Smallint)). Normally

RE: database in a jar : conglomerate does not exists

Thank you all At the end - taking care for the version of derby to be the same when I build the database or when I search - deleting the old database (corrupted) and starting with a new one, then creating the table and populating it Solved the problem. Archiving the database in a jar was not