[dsg-halla_solid] Magnet data log system

[Pablo Campero Rojas]

Hello,

Attached find some points of the discussion we had during our DSG meeting about the data archiving issue.

-Pablo
________________________________
From: Amrit Yegneswaran <yeg at jlab.org>
Sent: Friday, March 17, 2023 1:07 PM
To: Pablo Campero Rojas <campero at jlab.org>; dsg-halla_solid at jlab.org <dsg-halla_solid at jlab.org>; Amy Comer <acomer at jlab.org>
Cc: Patrizia Rossi <rossi at jlab.org>
Subject: Re: Magnet data log system


so i'm now totally lost
per amy for hall c Microsoft SQL 2019 express was not used
that's a non sequitur, back to square 1
so what was used for hallc
was there a problem at all with archiving

per brian there is disk space for 10 years
does each new file path open a new access file for 2GB
what is the path forward
dsg is marking time i guess

________________________________
From: dsg-halla_solid <dsg-halla_solid-bounces at jlab.org> on behalf of Amy Comer via dsg-halla_solid <dsg-halla_solid at jlab.org>
Sent: Thursday, March 16, 2023 4:39 PM
To: Pablo Campero Rojas <campero at jlab.org>; dsg-halla_solid at jlab.org <dsg-halla_solid at jlab.org>
Cc: Patrizia Rossi <rossi at jlab.org>
Subject: Re: [dsg-halla_solid] Magnet data log system

No it was not used.
________________________________
From: Pablo Campero Rojas <campero at jlab.org>
Sent: Thursday, March 16, 2023 3:43 PM
To: Amy Comer <acomer at jlab.org>; dsg-halla_solid at jlab.org <dsg-halla_solid at jlab.org>
Cc: Patrizia Rossi <rossi at jlab.org>
Subject: Re: Magnet data log system

Hi Amy,

Thanks for the info.
Are you using Microsoft SQL 2019 express for Hall C ?

-Pablo

________________________________
From: Amy Comer <acomer at jlab.org>
Sent: Thursday, March 16, 2023 1:47 PM
To: Pablo Campero Rojas <campero at jlab.org>
Subject: Re: Magnet data log system

Hi Pablo
We had a problem with the trends not showing archive data. The database (Microsoft Access) was full at 2GB. It was also a very old database.  It was suggested to upgrade to a larger new database. The expert from Rockwell at the time suggested upgrading to Microsoft SQL 2019 express having a maximum size of 10GB.
Amy
________________________________
From: dsg-halla_solid <dsg-halla_solid-bounces at jlab.org> on behalf of Pablo Campero Rojas via dsg-halla_solid <dsg-halla_solid at jlab.org>
Sent: Wednesday, March 15, 2023 3:34 PM
To: dsg-halla_solid at jlab.org <dsg-halla_solid at jlab.org>
Cc: Patrizia Rossi <rossi at jlab.org>
Subject: Re: [dsg-halla_solid] Magnet data log system

Hello Amy,

Can you let us know how to proceed with this matter?


Thanks,
Pablo
________________________________
From: Steven Lassiter <lassiter at jlab.org>
Sent: Wednesday, March 15, 2023 11:13 AM
To: dsg-halla_solid at jlab.org <dsg-halla_solid at jlab.org>; Pablo Campero Rojas <campero at jlab.org>
Subject: Re: Magnet data log system

Hi,

You should talk with Amy about how Hall C handled the 2GB size limitation.

We want to preserve and keep the data in whatever format is required so that one can do trend plotting from the HMI without interruption.

Go ahead and start a third and maybe fourth database file path.
At this point I am not concern about nuisance warnings. Only concern about not seeing archive data when it is needed.

thanks for the notice.
Steven
________________________________
From: dsg-halla_solid <dsg-halla_solid-bounces at jlab.org> on behalf of Pablo Campero Rojas via dsg-halla_solid <dsg-halla_solid at jlab.org>
Sent: Tuesday, March 14, 2023 12:26 PM
To: dsg-halla_solid at jlab.org <dsg-halla_solid at jlab.org>
Subject: [dsg-halla_solid] Magnet data log system

Hello Steven and Whit,

Over this weekend, I noticed that the data log file was automatically switched to the secondary directory path configured on the FTView data log system.
I checked this issue and found that the primary path become unavailable because of the Microsoft Access database file size limitation (only allows database files of 2 GB size) and since the current data file already reached this size is not allowing more data be archived in it.
Data is still being archived on the secondary path with no issues, but to avoid warnings about failing to reconnect automatically to the database file on the primary path, we have to initiate another data base file or at least subtract/reduce data from the current one.

The data recorded from January 17, 2023 would be still available on the Access file if it needs to be referred.

Is there any request for the time that you want to monitor on the trends?

Let me know how you would like to proceed.

-Pablo


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-halla_solid/attachments/20230322/4684fe0c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Solenoid Archiving Issue.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 12390 bytes
Desc: Solenoid Archiving Issue.docx
URL: <https://mailman.jlab.org/pipermail/dsg-halla_solid/attachments/20230322/4684fe0c/attachment-0001.docx>