I have a series of python scripts linked to tools in ArcToolbox. (still running 10.0 at the moment, though plan to upgrade in the near future) Without going into great detail, 2 or 3 of these scripts are regularly triggering an Error popup that says "Underlying DBMS error [ORA-01002: fetch out of sequence]" and the tool is effectively paused until I click OK on it... sometimes take one click sometimes takes a dozen.
I searched online for any information about this and what I found talks about fetching from cursors where there are no more rows to fetch. But these errors pop up even when I'm not running a cursor. They sometimes occur in 'for' statements, and even something as ridiculously simplistic as adding a field to a table from a list of fields will cause it. And what's worse is that it doesn't happen with any predictable regularity. Running a script that creates 20 new fields in a table will not always cause the error to kick in for the same field every time. And the cherry on top is that running these scripts inside an IDE does not trigger the error, so I don't believe the code is in error. There's something screwed up in ArcMap yet again.
It's getting extremely frustrating having to click on error boxes for tools that should be standalones. Am I the only one experiencing these issues or does anybody else have similar experiences that they've been able to troubleshoot successfully?
(I'll also note that these scripts run solely on data in SDE, if that matters)
I searched online for any information about this and what I found talks about fetching from cursors where there are no more rows to fetch. But these errors pop up even when I'm not running a cursor. They sometimes occur in 'for' statements, and even something as ridiculously simplistic as adding a field to a table from a list of fields will cause it. And what's worse is that it doesn't happen with any predictable regularity. Running a script that creates 20 new fields in a table will not always cause the error to kick in for the same field every time. And the cherry on top is that running these scripts inside an IDE does not trigger the error, so I don't believe the code is in error. There's something screwed up in ArcMap yet again.
It's getting extremely frustrating having to click on error boxes for tools that should be standalones. Am I the only one experiencing these issues or does anybody else have similar experiences that they've been able to troubleshoot successfully?
(I'll also note that these scripts run solely on data in SDE, if that matters)