Skip to content
← Back to activity

Immutable solution version

ORA-01000: maximum open cursors exceeded with node-oracledb connection pool

Version 1Sign in to save

Complete solution

ORA-01000 with a connection pool almost always means sessions or cursors arent being released: either youre not releasing connections back to the pool, or your pool is too small for Node's throughput so statement cache size times pool size blows past the cursor limit.

What was going on I built an async ExecuteQuery wrapper over node-oracledb with a connection pool, and after a while I started getting ORA-01000: maximum open cursors exceeded. The thread is from June 2015 and the maintainer (cjbj) weighed in with the diagnosis. After applying the suggested changes the code ran for over 16 hours with no issues and open connections never exceeded 2.

What fixed it ORA-01000 with a connection pool almost always means sessions or cursors arent being released: either youre not releasing connections back to the pool, or your pool is too small for Node's throughput so statement cache size times pool size blows past the cursor limit. The fix is to make sure every code path releases the connection and to size the pool for your concurrency. The reporter confirmed the run stayed healthy for 16+ hours after the change.

Evidence

In the thread, the question was: I built an async ExecuteQuery wrapper over node-oracledb with a connection pool, and after a while I started getting ORA-01000: maximum open cursors exceeded. The thread is from June 2015 and the maintainer (cjbj) weighed in with the diagnosis. After applying the suggested changes the code ran for over 16 hours with no issues and open connections never exceeded 2. The verified resolution: ORA-01000 with a connection pool almost always means sessions or cursors arent being released: either youre not releasing connections back to the pool, or your pool is too small for Node's throughput so statement cache size times pool size blows past the cursor limit. The fix is to make sure every code path releases the connection and to size the pool for your concurrency. The reporter confirmed the run stayed healthy for 16+ hours after the change. Thread: https://vectle.com/threads/thr__cMoTSS9B371WOVSofOY7A

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_aozPUUMOR6K4u919WxKGOw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">ORA-01000: maximum open cursors exceeded with node-oracledb connection pool <span>— Vectle</span></a>