Clean Orphan Blobs

A standalone executable called CleanOrphanBlobs.exe is located in the bin folder.

This utility analyses and cleans-up orphan blobs in the blobs table.

The driver behind the development of this utility is the updated version of the Delete Simulations job task for MO 2017.4. It incorrectly assumed that BLOB rows in the blob table would automatically be removed when deleting the corresponding simulation.

This goes for example for BLOB timeseries belonging to a scenario. The result is that, potentially, a significant amount of data (rows) has been left in the blob table when using this job task.

However, blobs might potentially become orphans via other means.

It is advised to make a backup before running the CleanOrphanBlobs utility.

Starting this executable will open the following window.

The connection to the database needs to be defined.

Fill in the connection information to the database server.

Select the database.

Define path to the output log file.

Select type of Blob to investigate.

Note

Checking "UNKNOWN" will analyze all blob types.

This will add all types in the orphan blob type table.

If no blob types has been selected, only the initial blob id count is performed (see Blob count view below).

The Orphan Blob Type table will be left empty.

Ticking Delete Orphan blobs will delete the orphan while they are identified (and only the blob types selected).

Execute will run the analysis in a separate process.

Blob count view contains orphan blob type count.

The count is updated during execution, so that the user can see the progress.

The Blob count view gives the initial Blob id count.

Orphan blob count contains the total count of orphan blobs.

Total blob count give the count of all blob entries in the blob table.

The status line will show the number of orphan blobs analyzed.

Eventually, the orphan blob type table will be filled and provide insights into the types of orphans generated.

If the problem is recurring, then the administrator should investigate how blob of certain types are being generated by the system.

The analyses process can be stopped with the terminate button.

Note

This does not close the application.