ColdFusion · Database exception
What does ORA-01003: No Statement Parsed mean in ColdFusion?
Appears under load when a ColdFusion Oracle datasource is configured with an oversized prepared-statement cache per connection — a high Max Pooled Statements value multiplied across many pooled connections corrupts or evicts cached statement handles faster than Oracle can track them. It reads as an Oracle-side error but the real cause is CF's connection/statement pool sizing.
Appears under load when a ColdFusion Oracle datasource is configured with an oversized prepared-statement cache per connection — a high Max Pooled Statements value multiplied across many pooled connections corrupts or evicts cached statement handles faster than Oracle can track them. It reads as an Oracle-side error but the real cause is CF's connection/statement pool sizing.
Cap Max Pooled Statements at a modest number (tens, not hundreds) per datasource, enable Limit Connections with a sane maximum, and add a connection validation query so corrupted cached statements get discarded on reuse.