Re: fast growing RBSs

Yes, it is odd. We were on Oracle 8.0.5.0 on AIX; we've since gone to 8.0.5.1. I don't know if the problem persists. The work-around is still in place. I didn't report it to Oracle.

I suppose it is possible that there were uncommitted transactions. It's been quite some time, and I don't quite remember all of the details.

In article <937240398.1481.0.nnrp-11.9e984b29_at_news.demon.co.uk>,   "Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote:
> That's a very odd one.
>
> Which version of Oracle ? Did you report it as
> a bug, or just work around it.
>
> I can't think of any reason why a session
> connection should hold a rollback segment;
> as far as I am aware, a rollback segment knows
> nothing about session which owns the attached
> transaction. After all, if you have one session (from
> SQL*Plus say) and keep executing little updates
> and commit you should see the transactions cycling
> through the rollback segments in turn.
>
> Is it possible that your middle-tier was opening two
> sessions, and one of them was starting a transaction
> that was never committed ?
>
> --
>
> Jonathan Lewis
> Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk
>
> Joseph T wrote in message <7rfd9r$9pg$1_at_nnrp1.deja.com>...
>
> >I had a problem with growing RBSs. I found that the middle tier of
our
> >three-tier client-server setup would open sessions and never close
> >them. RBSs associated with these sessions would never shrink back to
> >OPTIMAL. I reconfigured the middle tier to periodically close and
> >re-open sessions, and the problem went away.
>
>

--
Joseph Thvedt
jthvedt_at_my-deja.com

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't. Received on Wed Sep 15 1999 - 12:53:50 CDT