River2 database size limit

There's a limit to how big an object database can grow -- approximately 2 gigabytes.

Every time River2 does something that could result in using space, it checks if the database is approaching its maximum size. When it gets close, it won't continue. And it adds a message to the Log page so you can take the steps necessary to get your River2 server running smoothly again.

Usually there is enough room for lots more scanning, but the database has gotten fragmented. You can compact the database and then continue.

These instructions assume you're using config.root to store your River2 data. If you don't know wehther you are, then you are. There is another file you could be using, river2data.root. Just substitute it everywhere these instructions talk about config.root.

With OPML running on your server, bring the application to the front, then bring config.root to the front, by choosing it from the Window menu. This is very important. If you don't do this, the rest won't work.

Choose Quick Script from the Misc menu and enter this one-line script:

It could take quite some time to complete, as much as five or ten minutes. This is creating a compact copy of the config.root database.

Once it's finished, quit OPML.

Then be sure flaunch.exe isn't running.

Copy tmp.root into the apps sub-folder of the Guest Databases sub-folder of the OPML application folder.

Delete the old config.root, or to be perfectly safe, rename it to configx.root (in case something went wrong in the previous steps, this means at least you'll be able to repeat the steps).

Rename tmp.root to config.root. Re-launch OPML. It should pick up where it left off, with a compact config.root.

If you have questions, post a note on the River2 users mail list.

Be sure to say that you followed the instructions in this howto, and provide as much information as you can about what you did, and where things went wrong.