This is a QDBM problem. We are replacing this database in the coming months. For now, we are not sure why it does this but it usually happens when your index is corrupt.
This is a QDBM problem. We are replacing this database in the coming months. For now, we are not sure why it does this but it usually happens when your index is corrupt.