Oracle ORA-00036 Error: Causes and Solutions Complete Guide
The article discusses the Oracle ORA-00036 error, which occurs when the maximum number of recursive SQL levels is exceeded. It outlines the primary causes of this error, including circular trigger dependencies, infinite recursive PL/SQL procedures, and circular view references. Solutions and prevention tips are also provided to help users avoid encountering this error in the future.
- ▪ORA-00036 occurs when Oracle's internal recursive SQL call stack exceeds its maximum allowed depth, which defaults to 2000 levels.
- ▪Circular trigger dependencies, infinite recursive PL/SQL procedures, and circular view references are the top three causes of this error.
- ▪The article provides solutions such as disabling offending triggers, adding base cases in functions, and rewriting views to reference base tables directly.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/dbmserror/oracle-ora-00036-error-causes-and-solutions-complete-guide-34k7 |
| Publication time | Fri, 29 May 2026 07:06:47 +0000 |
| Retrieval time | 2026-05-29T07:19:58.503Z |
| Last seen | 2026-05-29T07:19:58.503Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | BIV-LY3ntCG6 · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3943064) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } umzzil nng Posted on May 29 • Originally published at oraerror.com Oracle ORA-00036 Error: Causes and Solutions Complete Guide #oracle #database #dba #sql ORA-00036: Maximum Number of Recursive SQL Levels Exceeded ORA-00036 occurs when Oracle's internal recursive SQL call stack exceeds its maximum allowed depth, which defaults to 2000 levels.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
