Re: Looking for suggestions - how find cause of sql invalidations
From: Chris Taylor <christopherdtaylor1994_at_gmail.com>
Date: Tue, 18 Jul 2017 12:55:08 -0500
Message-ID: <CAP79kiQDXvGXg-a50qVQ6A=VXHv0EVn+3F4pvcbhxzA0OxwyGg_at_mail.gmail.com>
Date: Tue, 18 Jul 2017 12:55:08 -0500
Message-ID: <CAP79kiQDXvGXg-a50qVQ6A=VXHv0EVn+3F4pvcbhxzA0OxwyGg_at_mail.gmail.com>
Ok,here's the output from this script - anything jump out at you guys? I see PURGED_CURSOR=Y but I'm not understanding how to connect the dots.
https://pastebin.com/raw/wVzmmuSx
Chris
On Tue, Jul 18, 2017 at 11:50 AM, Sayan Malakshinov <xt.and.r_at_gmail.com> wrote:
> You can use also my script: https://github.com/xtender/xt_
> scripts/blob/master/sql_shared.sql
> it shows reasons with their parameters
>
> --
> Best regards,
> Sayan Malakshinov
> http://orasql.org
>
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Jul 18 2017 - 19:55:08 CEST