Fellow Oracles,

There is a nasty procedure in a nasty package which seems to cause this error quite frequently and I've run out of ideas as to why it happens.

The best bet was to come out here and consult with some Oracles which have been around for quite a good amount of time.

Anyone has ideas, or any little clue as to the instances which could possibly throw this error out.

The cursor query of the procedure uses two materialised views which get refreshed once in an hour. They donot have indexes.

Could it be that this error is caused when the procedure is called right at the time when the mat views refresh.

or could it be anything else?

ideas and suggestions are much appreciated.

Thanks in advance.