have a good high number of open cursors parameter setted up. Then try running the query and see whether it goes successful. If it fails then you might have to increase the shared_pool_size and also make sure that you have a good size of temp table space, if your query were to do some kind of order by clause. Mostly, the OPEN_CURSORS parameter should fix it all. One other thing is that do an explain plan on your query and see how the execution plan goes and you might be able to modify it to use indices and etc
If you encounter any problems, pl post the problem and the error message...
I increased the OPEN_CURSORS to 500, and I still get the same error message.
The thing is, the Database was running this query fine on Friday, with not even a hint of a problem. Could it be because there are more instances on the AIX machine swallowing all the memory allocation?
I reset my INITODSD.ORA file to what is was before (except for OPEN_CURSORS):
Check your alert log file and let us know of the error that you were getting now after resetting the open_cursors. Also could you let us know of the database version and your db_block_size.
Bookmarks