Some workarounds proposed in this thread target the query optimization phase.
But I think the processing might not even come that far; the problem might
appear during parsing instead, because ORA-04031 is raised for the function
qcopCreateLog , which, according to Frits Hoogland, is a parsing function. This
is something that can be definitely verified with 10053 trace.
If the query indeed fails during the parsing phase, I would suggest checking if
the columns are fully referenced with the schema name. (Some query generators
do that.) The check doesn’t take much time, and if it really turns out to be
the problem, it’s fairly easy to fix.
Why do I suggest that?
There was a problem in an earlier release when columns in certain types of
queries were referenced by schema name, see
https://nenadnoveljic.com/blog/memory-leak-parsing/ ;.
Your query has similar characteristics as the one used in the article above:
complex case expression, lots of brackets, long query text.
The only difference is, that in my case, the excessive allocations were in PGA,
so I got ORA-04030 instead of ORA-04031. I cannot reproduce the issue in 19c,
but maybe you’re hitting a variant of “my” problem.
Best regards,
Nenad
____________________________________________________
Please consider the environment before printing this e-mail.
Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.
Important Notice
This message is intended only for the individual named. It may contain
confidential or privileged information. If you are not the named addressee you
should in particular not disseminate, distribute, modify or copy this e-mail.
Please notify the sender immediately by e-mail, if you have received this
message by mistake and delete it from your system.
Without prejudice to any contractual agreements between you and us which shall
prevail in any case, we take it as your authorization to correspond with you by
e-mail if you send us messages by e-mail. However, we reserve the right not to
execute orders and instructions transmitted by e-mail at any time and without
further explanation.
E-mail transmission may not be secure or error-free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also
processing of incoming e-mails cannot be guaranteed. All liability of Vontobel
Holding Ltd. and any of its affiliates (hereinafter collectively referred to as
"Vontobel Group") for any damages resulting from e-mail use is excluded. You
are advised that urgent and time sensitive messages should not be sent by
e-mail and if verification is required please request a printed version.
Please note that all e-mail communications to and from the Vontobel Group are
subject to electronic storage and review by Vontobel Group. Unless stated to
the contrary and without prejudice to any contractual agreements between you
and Vontobel Group which shall prevail in any case, e-mail-communication is for
informational purposes only and is not intended as an offer or solicitation for
the purchase or sale of any financial instrument or as an official confirmation
of any transaction.
The legal basis for the processing of your personal data is the legitimate
interest to develop a commercial relationship with you, as well as your consent
to forward you commercial communications. You can exercise, at any time and
under the terms established under current regulation, your rights. If you
prefer not to receive any further communications, please contact your client
relationship manager if you are a client of Vontobel Group or notify the
sender. Please note for an exact reference to the affected group entity the
corporate e-mail signature. For further information about data privacy at
Vontobel Group please consult www.vontobel.com <https://www.vontobel.com>.
