Re: Disk space issues with not automatically deleted journal receivers

Hi Patrik,

Am 17.08.2025 um 00:01 schrieb Patrik Schindler <poc@xxxxxxxxxx>:

when developers create databases and tables through SQL, journaling is automatically set up, and set to mngrcv(*system), which is good. But the journal is not set to delete detached receivers by default. This in turn slowly but steadily eats up disk space.

This is only true, if you use the CREATE COLLECTION statement before creating you tables in that collection. This creates a library including default journal and receivers.

If you create your library manually and do a STRJRNLIB, the tables that you later create with CREATE TABLE are automatically journaled in the same journal as the library, and you have full control.

IMHO you should never leave journaling to the system defaults - whether is a production or test environment - even not for a personal playground.

You need to define a journaling and backup "strategy" first - otherwise you risk losing data.

I have no better idea what to do but use wrklib option 12 for every SQL created library, and delete all but the highest numbered receivers. This makes me lose receivers which haven't been saved (by the automatic daily savchgobj), yet.

Use the JOURNAL_RECEIVER_INFO view to find the receivers, that are detached and on already have a "last saved" date - these are the ones to delete.

HTH
Daniel