Re: ORA-04068 on New Session
From: Sayan Malakshinov <xt.and.r_at_gmail.com>
Date: Wed, 10 Jan 2024 20:00:08 +0000
Message-ID: <CAOVevU4XRR7ocnA+D+hf-5t1CMAT9sVdF6t1CSnqHdAS66Sj=g_at_mail.gmail.com>
Date: Wed, 10 Jan 2024 20:00:08 +0000
Message-ID: <CAOVevU4XRR7ocnA+D+hf-5t1CMAT9sVdF6t1CSnqHdAS66Sj=g_at_mail.gmail.com>
Iirc, this kind of errors must be passed to a client side or explicitly reset their state using DBMS_SESSION.RESET_PACKAGE. So, just always use "raise" in "when others then". Don't ignore them and do not replace them with raise_application_error
On Wed, Jan 10, 2024, 19:18 Mladen Gogala <gogala.mladen_at_gmail.com> wrote:
> On 1/10/24 13:16, Dominic Brooks wrote:
>
> Global variables should be private in the UGA.
>
> What happens when connection pooling is utilized? Or when shared server is
> utilized? I believe that pooled and shared connections keep the global
> variables in the shared pool (SGA).
>
> --
> Mladen Gogala
> Database Consultant
> Tel: (347) 321-1217https://dbwhisperer.wordpress.com
>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Jan 10 2024 - 21:00:08 CET