Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 8533

Re: DBIF_RSQL_INVALID_CURSOR after secodary indexes created

$
0
0

Hi

 

I guess the way two months and the plants get selected is not optimal and takes too much memory and eventually dumps. Have you tried not filtering on the plants? Sometimes not filtering makes the query access even faster. You secondary index might not be ideal for the sql access path

hope it helps
Martin


Viewing all articles
Browse latest Browse all 8533

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>