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: 2023-04-20 08:00 AM . Last Modified: 2023-05-02 11:44 PM
Hill everyone, I run a process everyday to insert data into ORACLE DB from Geo SCADA, but today I got this error (attached image). Even I tried to insert the data manually but I'm sitll getting the same error. Any suggestion?
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: 2023-04-20 08:52 AM
The Query Processor diagnostics don't show the size, but it is logged in the DB log. Look for a line like the following (with "Resultset complete") which shows the number of rows and size for the result set:
20-APR-2023 15:44:58.432 2B30 [SCX] L09#01 QPTable 2 Resultset complete (47 rows, 10152 bytes)
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: 2023-04-20 08:25 AM . Last Modified: 2023-04-20 08:26 AM
The "Size limit exceeded" error indicates that the result set of your SQL query is too large, i.e. it using too much memory. You should review the query to ensure it isn't returning more data than expected.
The maximum size (default 250MB) can be changed, see Use the Parameters Settings to Define the SQL Query Row and Size Limit but you need to be careful about running out of memory or adversely effecting the performance of the system.
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: 2023-04-20 08:40 AM
Hi Andrew, Is there any way to know the size (MB) of my query?
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: 2023-04-20 08:52 AM
The Query Processor diagnostics don't show the size, but it is logged in the DB log. Look for a line like the following (with "Resultset complete") which shows the number of rows and size for the result set:
20-APR-2023 15:44:58.432 2B30 [SCX] L09#01 QPTable 2 Resultset complete (47 rows, 10152 bytes)
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: 2023-04-20 01:51 PM
Thanks for your recommendation Andrew, I'm gonna check the log.
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.
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: 2023-04-21 06:47 AM
The "exceeded.jpg" log shows a request from an OPC DA client (e.g. a mimic in ViewX) for 62 items where some of these items (probably points) are outside the engineering range for the item (e.g. overrange or underrange analogue points). This is totally unrelated to SQL queries that are too large.
You should be able to find entries in the DB log based on the timing or looking for the query that your process executes which is failing with the "Size limit exceeded" error (the SQL itself is in the DB log).
If your system has multiple servers make sure to look at the DB logs for the server your process has connected to, which may not be the current main server.
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.