WCCILdata - PARAM/SEVERE - DataManager insertAttribute not successful, too many lines in table - query aborted

The following log-message is displayed when a query limit of the data manager is reached. The log message is written to the PVSS_II.log-file.

WCCILdata (0), 2011.10.06 09:07:01.195, PARAM,SEVERE, 81, Syntax error, DataManager insertAttribute not successful, too many lines in table - query aborted

The log message with symbolic names:

WCCILdata (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. The number of lines is limited by using the config entry maxLinesInQuery in the [data]-section.

If the function getLastError() is used in the script where the function to read the historical data was started, the following error is displayed. 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:

WCCILui (1), <TIMESTAMP>, PARAM,SEVERE, 81, Syntax error, DataManager insertAttribute not successful, too many lines in table - query aborted

If this error is reported, check which historical query was started and whether this query should be allowed or not. The maximum value for the config entries must be specified by taking into account the opinion of the users operating the plant.

Do not increase the value 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, see the Online help and the keywords "Error tolerance" and "stability".

If the limit for historical alert queries is reached, the config entry does not limit the number of lines. In this 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