EcoStruxure Geo SCADA Expert Forum
Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-09-03 11:28 AM
Hello all,
Is there a way to view the record key that goes with each line of data that is in the tables of CDBHistoric and CDBPoint?
We are attempting to decipher duplicate data issues and need these values to understand the sequence with which the data was entered to the tables.
Thanks!
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-09-04 09:38 AM
The database schema will show you the details of these tables. Use the following URLs in a web browser:
https://<server name>:<web server port>/Schema/CDBHistoric
https://<server name>:<web server port>/Schema/CDBPoint
Historic data is organised into weekly files per object (point):
- In the CDBHistoric table the Id field indicates which object (point) the record is associated with. This matches the Id field in the CDBPoint table.
- In the CDBHistoric table the FileId field indicates which object and week the record is in. Weeks are numbered from 1-JAN-1601. This field encodes the object ID and week number in hexadecimal with a suffix for raw ('R') or modified ('M'). For example "0000004D00005652R" is raw record for object 77 (0x4D) and week 22098 (0x5652) - this is the week beginning 8-JUL-2024.
- In the CDBHistoric table the FileOffset field indicates the order in which the records were stored within the weekly file identified by the FileId field.
So the file offset will give the sequence in which the records were created for a particular week/object, but there is no way to get the sequence between different weeks or different objects from this table.
Log files from the driver which is the source of the point can capture the data being received from the outstation/device and the data then being passed from the driver to the server which stores the data in the historian which would give more insight into the sequence.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-09-04 09:38 AM
The database schema will show you the details of these tables. Use the following URLs in a web browser:
https://<server name>:<web server port>/Schema/CDBHistoric
https://<server name>:<web server port>/Schema/CDBPoint
Historic data is organised into weekly files per object (point):
- In the CDBHistoric table the Id field indicates which object (point) the record is associated with. This matches the Id field in the CDBPoint table.
- In the CDBHistoric table the FileId field indicates which object and week the record is in. Weeks are numbered from 1-JAN-1601. This field encodes the object ID and week number in hexadecimal with a suffix for raw ('R') or modified ('M'). For example "0000004D00005652R" is raw record for object 77 (0x4D) and week 22098 (0x5652) - this is the week beginning 8-JUL-2024.
- In the CDBHistoric table the FileOffset field indicates the order in which the records were stored within the weekly file identified by the FileId field.
So the file offset will give the sequence in which the records were created for a particular week/object, but there is no way to get the sequence between different weeks or different objects from this table.
Log files from the driver which is the source of the point can capture the data being received from the outstation/device and the data then being passed from the driver to the server which stores the data in the historian which would give more insight into the sequence.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-09-05 10:11 AM
Thank you very much. The combination of FileID and File Offset fields enabled us to arrange the data into the order in which it entered the database tables.
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.