Alert Log Shows Error ORA-01000: Maximum Open Cursors Exceeded in E-Business Suite (EBS) Modules
(Doc ID 2958381.1)
Last updated on JANUARY 22, 2025
Applies to:
Oracle Concurrent Processing - Version 12.2.4 and laterOracle Project Billing - Version 12.2.4 and later
Oracle General Ledger - Version 12.2.9 to 12.2.9 [Release 12.2]
Information in this document applies to any platform.
Symptoms
The below error is occurring multiple times in the alert log :
ORA-01000: Maximum Open Cursors Exceeded in Process .
ORA-01000: Maximum Open Cursors Exceeded in Process .
ORA-01000: Maximum Open Cursors Exceeded in Process .
ORA-01000: Maximum Open Cursors Exceeded in Process .
..
..
-Increasing open_cursors from 2000 to 4000 does not help.
-Because of this, scheduled concurrent jobs go into an UNKNOWN state when they hit the max open cursor issue.
These jobs then need to be updated to TERMINATED from the back-end and are eventually rescheduled.
-This issue can happen on any of the EBS modules.
-This also happens in R12.1.3.
-In R12.2, for Projects module, it happens after applying the following Projects G-Invoicing patch: 35335573:R12.PA.C: G-Invoicing Apr-23 Incremental patch to manage performance integration between G-Invoicing and Oracle Projects.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |