Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: ORA-1562, Rollback segments reached max
Hi,
Is it possible to know which rollback segment is reached capacity and how to check the capacity reached
But the old extents, inactive extents are deallocated by oracle itself
If I want to modify a rollback segment what I need to do to avoid crashing database
Thanks a lot!
Chris
Clark Mason wrote:
> If you find that one or more of your rollback segments has a large
> number of extents, you may want to use the "optimal" parameter so that
> Oracle will try to deallocate extents that are no longer needed by
> active transacations.
>
> <20001220.135408.197782_at_CTBTO.ORG>,
> Cong Tang <Cong.Tang_at_ctbto.org> wrote:
> > This is a multi-part message in MIME format.
> > --------------4403E2DB64A5A52ADAFB3FB8
> > Content-Type: text/plain; charset=us-ascii
> > Content-Transfer-Encoding: 7bit
> >
> > Hello,
> >
> > Sure it is a rollback segment issue. You don't have to shutdown the
> > database. Unfortunately, a transaction cannot span over two rollback
> > segments, so some changes were rolled back when the error occurred.
> >
> > There are two possibilities:
> > 1) Your rollback segments are small and the maximum number of extends
for a
> > rollback segment exceeded.
> > 2) There was no space left in the rollback tablespace.
> >
> > You can query DBA_FREE_SEGMENTS, DBA_TABLESPACES and DBA_FREE_SPACE to
> > verify this. To avoid this problem in the future, make sure that you
have
> > multiple and large rollback segments (e.g. INITIAL 1M NEXT 1M) and
the data
> > files belonging to the rollback tablespace is automactically extended.
> >
> > Cong
> >
> > hlk wrote:
> >
> > > Hi,
> > >
> > > I get these errors codes from oracache.log with -1562, -604
> > > and with an Oracle command "oerr ora 1562" and I got this
> > >
> > > 01562, 00000, "failed to extend rollback segment number %s"
> > > // *Cause: Failure occurred when trying to extend rollback segment
> > > // *Action: This is normally followed by another error message that
> > > caused
> > > // the failure. Shutdown, restart and then take appropriate
> > > action for
> > > // the error the caused the failure. If starting up the
system
> > > // again doesn't solve the problem, it is possible that
there is
> > >
> > > // an active transaction in the rollback segment and the
system
> > > // can't roll it back for some reasons. Check the trace file
> > > // generated by the PMON process for more information.
> > >
> > > It seems rollback segments issue, but I am not sure
> > > Can someone tells me why it means and how it can be resolved
> > >
> > > Thanks a lot !
> > >
> > > Chris
> >
> > --------------4403E2DB64A5A52ADAFB3FB8
> > Content-Type: text/x-vcard; charset=us-ascii;
> > name="Cong.Tang.vcf"
> > Content-Transfer-Encoding: 7bit
> > Content-Description: Card for Cong Tang
> > Content-Disposition: attachment;
> > filename="Cong.Tang.vcf"
> >
> > begin:vcard
> > n:Tang;Cong
> > tel;work:+43 1 26030 6288
> > x-mozilla-html:FALSE
> > org:Comprehensive Nuclear-Test-Ban Treaty Organization (CTBTO)
> > adr:;;;Vienna;;;Austria
> > version:2.1
> > email;internet:Cong.Tang_at_ctbto.org
> > title:Database Administrator
> > fn:Cong Tang
> > end:vcard
> >
> > --------------4403E2DB64A5A52ADAFB3FB8--
> >
> >
>
> Sent via Deja.com
> http://www.deja.com/
Received on Wed Dec 20 2000 - 17:19:32 CST