Re: Temporary tablespace usage
From: Adric Norris <landstander668_at_gmail.com>
Date: Fri, 16 Dec 2011 16:50:02 -0600
Message-ID: <CAJueESq35TePzb8TTzR+T0L5U2Kud8F4fG7z3JRZwsvCg_mTjA_at_mail.gmail.com>
Unfortunately, this is purely an application issue... the LOB segments won't be released until the session terminates, *unless* they're explicitly closed. In our case, the only immediately viable solution was to recycle the application (or kill the relevant SID) since so many sessions were affected. The long-term solution was an application-side code change, to call DBMS_LOB.CLOSE at the appropriate times. On Fri, Dec 16, 2011 at 16:07, Raju Angani <angani_at_gmail.com> wrote:
Date: Fri, 16 Dec 2011 16:50:02 -0600
Message-ID: <CAJueESq35TePzb8TTzR+T0L5U2Kud8F4fG7z3JRZwsvCg_mTjA_at_mail.gmail.com>
Unfortunately, this is purely an application issue... the LOB segments won't be released until the session terminates, *unless* they're explicitly closed. In our case, the only immediately viable solution was to recycle the application (or kill the relevant SID) since so many sessions were affected. The long-term solution was an application-side code change, to call DBMS_LOB.CLOSE at the appropriate times. On Fri, Dec 16, 2011 at 16:07, Raju Angani <angani_at_gmail.com> wrote:
> Adric,
>
> you were spoton, when I added the segtype as you recommended, all
> those rows showed as LOB_DATA.
> Now, is there a way I can make a fix to shrink the temporary tablespace.
>
> Thank you
> RA
>
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Dec 16 2011 - 16:50:02 CST