Post
Highlighted: the lines this signal was extracted from
Hi everyone, I’m looking for some help from people who have experience with Waters UNIFI. 1-The main issue is with data processing after acquisition. sometimes the processing starts normally but then stops before completing. No peaks appear in Detected Candidates. I have already checked several thing:Lock mass signal is stable. The Work in Progress list is empty. I created a completely new system and a new method from scratch.Despite this, the problem still occurs. The strange thing is that the exact same system and method can work correctly sometimes, while at other times the processing fails, without any modification being made to the system or method. Has anyone experienced this kind of intermittent processing problem with UNIFI? 2-In Database Manager, I sometimes see these two red messages: WATBLOB is full (100%) WATSTREAMB is full (100%) What is strange is that I have already deleted data through the UNIFI interface, and I have also deleted the backup files, but the red 100% messages in Database Manager remain. So I’m wondering: What exactly are WATBLOB and WATSTREAMB? Is there a specific procedure to safely free this space? Could this be related to the intermittent processing failures or UNIFI becoming slow? I don’t want to manually delete anything from the database or Windows folders without knowing exactly what it does. 3-I also noticed that our backup...
Keep reading with a free account
The rest of this post, and every signal for Waters, is in your free account.
Also quoted as evidence
In Database Manager, I sometimes see these two red messages: WATBLOB is full (100%) WATSTREAMB is full (100%) ... I have already deleted data through the UNIFI interface, and I have also deleted the backup files, but the red 100% messages in Database Manager remain.
From the post
I also noticed that our backup storage grows very quickly. We can reach around 4 TB in only a few months.
From the post
Sometimes, the next morning, I find that the system has stopped with a “CM-A communication failure”, and the sequence has not been completed.
From the post