PVSS00data - PARAM/SEVERE - DataManager insertAttribute not successful, too many lines in table - query aborted
Enclosed you'll find the explanation for a log-message which can occur when a query limit is reached at the data-manager. The log-message is written to the PVSS_II.log-file.
PVSS00data (0), 2011.10.06 09:07:01.195, PARAM,SEVERE, 81, Syntax error, DataManager insertAttribute not successful, too many lines in table - query aborted
Log-message with symbolic names:
PVSS00data (0), <TIMESTAMP>, PARAM,SEVERE, 81, Syntax error, DataManager insertAttribute not successful, too many lines in table - query aborted
This log-message describes that the query result contains too many lines at the result. The number of lines is limited with the config-entry maxLinesInQuery for the [data]-section.
If the function getLastError() is used in the script where the function to read the historical data was started you’ll get the following error. When using the function throwError() the error is written to the PVSS_II.log-file.
E.g. the user-interface with number 1 was trying to read the values:
PVSS00ui (1), <TIMESTAMP>, PARAM,SEVERE, 81, Syntax error, DataManager insertAttribute not successful, too many lines in table - query aborted
If this error is reported please try to find out which historical query was started and afterwards check if this query should be allowed or not. The maximum value for the config-entries has to be defined in discussion with the users operating the plant.
Please do not increase the values for the config-entries to a very high value (e.g. 1000000) or set it to 0 (no limitation).
The limitation for queries is part of the system stability functions in WinCC OA. For details please have a look at the online-help, search for the keywords “Error tolerance” and “stability”.
If the limit is reached for historical alert queries the config-entry does not limit the number of lines. In that case the number of result entries is counted.
The limit calculation works as follows, "+ 1" is the header information:
<number of queried alert attributes> * <number of resut lines> + 1