Manual values for historian is no longer inserted into the correct archive
Summary
Inserting manual values into an archive of the historian, or changing manually changing a value, creates a new archive instead of changing / inserting the value in the correct archive
Description
Inserting manual values into an archive of the historian, or changing manually changing a value, creates a new archive instead of changing / inserting the value in the correct archive
Solution
An issue has been addressed in the historian where a manual value was stored in a new archive. Nowchanged values or inserted values result in a new archive only when spontaneous archiving is used
Information
Problem introduced with build 4
Issue Number: 29404
Fixed on Date: 24.4.2013
Versions: 7.00 0 BUILD 9 | 7.10 0 BUILD 6571
Related Articles
FAQ: Historian configuration general recommendations
1. Recommendation on hardware: Storage Memory CPU - SSD (Solid-State Drive). - Disk space capacity as detailed in the attached Excel sheet outputs. - RAM required to load the archive data is about 4 times greater the size of the respective ARX files. ...
Historian values created via the programming interface with a timestamp of 00:00:00 for the first day of the month can no longer be deleted
Summary When historian values are created via the programming interface with a timestamp of 00:00:00 and the first day of the month, these values are inserted into the historian, but can in turn no longer be deleted. DescriptionWhen historian values ...
Archive configuration for best SQL evacuation performance
The time required to evacuate data to a database increases linearly with the number of insert SQL statements. In earlier zenon versions, recorded values were evacuated to the target database sequentially using single-insert statements. From zenon 11 ...
Historian: At reload an old value is written again / received values with old external timestamp not discarded
Description In the Service Engine, data from already closed archives is written to the current, open archive capsule in the Historian. This problem can occur: By project reload. If the PLC sends variable values with an external timestamp from the ...
FAQ: After updating to zenon 7.20 I dont see newly SQL evacuated historian data anymore in the trend (ETM), Report Generator, Report Viewer and Archive Revision, only the former evacuated values are displayed.
Summary Solution There is an available update, see Article ID195426 / ID165155. We highly recommend to update to the linked build ID195426 If you do not update, there is a Workaround Change the GUID column of the table from CHAR to VARCHAR. With ...