Skip to main content

Change open_cursors Value


The Oracle initialization parameter OPEN_CURSORS specifies the number of cursors a session can have open at any one time. The default value is 300.
If the session attempts to open a new cursor but already has the maximum number of cursors open, the Oracle error -1000 will be returned.
Your client application may hit the following error :
ORA-01000: maximum open cursors exceeded

You can do two things,
1) Change the inti.ora parameter open_cursors = <increased-no>
init.ora file location = ORACLE_HOME\dbs
A database restart is needed to affect the above change.
You can check the value by below sql.
SQL> show parameter OPEN_CURSORS;
Note:
If you are using a spfile you can do it through below statement.
alter system set open_cursors=xxx scope=both;


2) In your application code , use For ...Cursors, because that automatically closes the cursor.
    If you cannot use For..Cursor, take care to close the cursors. Otherwise the opened cursors will persist in memory and increase the open_cursors count unnecessarily.



Comments

Popular posts from this blog

Building Continuous Data Trust with Oracle GoldenGate Veridata 26c

Today I'll discus on how we can build continuous data trust with Oracle GoldenGate Veridata 26c! As we accelerate towards hybrid and multi cloud architectures , one challenge keep coming up. That is "H ow do you trust your data across all these platforms?" With increasing data movement, replication, and transformation, even small changes can lead to major business risks. This is where Oracle GoldenGate Veridata 26c comes in handy! Rather than just validating data occasionally, the focus now is on continuous data trust . What is Veridata? It is a tool to compare data across different systems. It ensures source and target databases are in sync. It works during , Data migration, Replication setups, Ongoing operations. What’s new in Veridata 26c? 1. Support for Modern Architectures Built for hybrid, multi-cloud, and lakehouse environments with support for heterogeneous databases. 2. Continuous Data Validation Enables ongoing validation to detect data drift and inconsisten...

Top 5 Performance Tuning Tricks Every Oracle DBA Should Know!

Performance tuning in Oracle Database often focuses on obvious areas like indexes, SQL rewrites etc. But some of the most impactful improvements can come from lesser known techniques. Here are 5 such tuning tricks that can make a real difference in production environments.   Use SQL Plan Baselines to Stabilize Performance Even properly tuned queries in Oracle Database can suddenly degrade when execution plans change due to statistics refreshes or system upgrades. Using SQL Plan Baselines helps maintain stable and efficient execution plans, preventing unexpected performance regressions especially in highly changing workloads. SELECT * FROM DBA_SQL_PLAN_BASELINES; So, don’t just capture baselines, but periodically change them to allow the optimizer to adopt better plans when appropriate. Use Automatic Indexing Automatic Indexing is a useful feature in Oracle Database that can improve performance with minimal effort.  It was introduced in Oracle Database 19c and enhance...

Bring AI to Data , A Smarter Way with Oracle!

  “Bring AI to Data” is a term I recently heard during the Oracle AI World in Singapore last week and it really caught my attention. It sounded simple but the idea behind it is quite powerful. So I thought it’s worth exploring a bit more! Normally, working with data and AI meant one thing, which is, moving data around. We would extract data from databases, send it to external tools or platforms, build machine learning models and then push the results back into the database. But this approach adds complexity, increases costs and introduces security risks. But now, Oracle is changing that model by bringing AI to where the data already is ! The concept of “Bring AI to Data” is straightforward but powerful. Instead of moving large volumes of data across systems, Oracle allows you to run AI and machine learning directly inside the database. This means that data do not have to leave its secure environment. This results faster processing, reduced data duplication, improved security ...