nd recreate them.
>
> Best Regards,
> K Gopalakrishnan
> Bangalore, INDIA
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Mohammad
> Rafiq
> Sent: Wednesday, February 13, 2002 9:54 AM
> To: Multiple rec
AIL PROTECTED]]On
> Behalf Of Mohammad
> Rafiq
> Sent: Wednesday, February 13, 2002 9:54 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Rollback Segment Problem
>
>
> In many cases you will have to take RB segments offline
> and drop them, then
> re-creat
d recreate them.
>
> Best Regards,
> K Gopalakrishnan
> Bangalore, INDIA
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Mohammad
> Rafiq
> Sent: Wednesday, February 13, 2002 9:54 AM
> To: Multiple recipients
Regards,
> K Gopalakrishnan
> Bangalore, INDIA
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Mohammad
> Rafiq
> Sent: Wednesday, February 13, 2002 9:54 AM
> To: Multiple recipients of list ORACLE-L
> Subject:
afiq
> Sent: Wednesday, February 13, 2002 9:54 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Rollback Segment Problem
>
>
> In many cases you will have to take RB segments offline
> and drop them, then
> re-create
>
,
> K Gopalakrishnan
> Bangalore, INDIA
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Mohammad
> Rafiq
> Sent: Wednesday, February 13, 2002 9:54 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Rol
recreate them.
>
> Best Regards,
> K Gopalakrishnan
> Bangalore, INDIA
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Mohammad
> Rafiq
> Sent: Wednesday, February 13, 2002 9:54 AM
> To: Multiple recipients
INDIA
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Mohammad
> Rafiq
> Sent: Wednesday, February 13, 2002 9:54 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Rollback Segment Problem
>
>
afiq
> Sent: Wednesday, February 13, 2002 9:54 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Rollback Segment Problem
>
>
> In many cases you will have to take RB segments offline
> and drop them, then
> re-create
>
DIA
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Mohammad
> Rafiq
> Sent: Wednesday, February 13, 2002 9:54 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Rollback Segment Problem
>
>
> In many ca
riginal Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Mohammad
> Rafiq
> Sent: Wednesday, February 13, 2002 9:54 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Rollback Segment Problem
>
>
> In many cases you
You never need to recreate the rollback segments (DROP and CREATE) unless
the rollback segment dies. THe rollback segment will die after approx 4M
(the number is not very accurate.. okay,, some number)transactions.
THis is the only case I need to drop and recreate them.
Best Regards,
K Gopalakris
Here you are absolutely right...
Regards
Rafiq
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
Date: Wed, 13 Feb 2002 11:59:53 -0800
Exactly. It depends pretty much on the application, how often it commits
transactions, segment sizes, of course, OLTP a
]]On Behalf Of Babich ,
> Sergey
> Sent: Wednesday, February 13, 2002 3:00 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Rollback Segment Problem
>
>
> Exactly. It depends pretty much on the application, how often it commits
> transactions, segment sizes, of
Exactly. It depends pretty much on the application, how often it commits
transactions, segment sizes, of course, OLTP amount etc. You can't always
wait for SMON to wake up and do its job. The point is COALESCING alone won't
always help and you have to defrag. Another point is ONE thing is reading
Thanks...even is not true completely...if you have seen responses of Sameer
Sarkar, originator of this thread...resolved his problem after coalesing his
rbs table_space...
I have to dealt with this situation on one of our databases because of some
codes which results in lot of shrinkage of rol
IN THIS CASE yes, but NOT BEFORE That was my point.
Thanks,
Best,
Sergey
-Original Message-
Sent: Wednesday, February 13, 2002 12:54 PM
To: Multiple recipients of list ORACLE-L
In many cases you will have to take RB segments offline and drop them, then
re-create
--Even in thi
ts of list ORACLE-L
> > Subject: RE: Rollback Segment Problem
> >
> >
> > Jerry,
> > Thanks for sharing script. We might have better systems as timing
> > was never
> > be a issue. I just tested my script on 2 systems and it ran between 34.5
> > mseconds
Samir,
For a long term solution, it is better to reorg rbs tablespace and rollback
segments with correct sizing based on usage...
You may use following script to get better info about rollback segments
usage
1 set linesize 120
2 column name format A15
3 column status format A7
4 co
In many cases you will have to take RB segments offline and drop them, then
re-create
--Even in this case you have to coalesce rbs tablespace before
recreating rollback segments using that particular tablespace to make all
released extents as contigous...Besides it is a good practice to re
Hi, guys,
Just my $0.02, coalescing free space will NEVER eliminate fragmentation. In
many cases you will have to take RB segments offline and drop them, then
re-create. In the interim period you might want to have a big rollback
segment(or a few) in another tablespace.
Best,
Sergey
-Origina
t
find contiguous free space it try coalesce itself.
Alex Hillman
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mohammad
> Rafiq
> Sent: Tuesday, February 12, 2002 4:53 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE:
Thanks a lot, Rafiqthe output from ur query after running it on the
database
showed the rollback segment to be highly fragmented.the total extents
were
7490 and the extents coalesced were only 440. The initial and next extents
have been set at 409K which seems to me as quite small.
Regard
Samir,
Thanks..Due to lot of activities of rollback segment resulting in shrinkage
make rbs tablesapce fragmented hence contigous space becomes a
issue...Possible solution to set a good size of optsize of rbs to avoid
shrinkages or frequent coalesing of rbs tablespace / or any other tablespace
Samir,
It is not coalesced automatically at shutdown and startup. It is to be
coalesced manually. It applies to any tablespace with pctincrease set as
0(zero). I have no idea of 9i but this is normal behaviour of ver 7.3.4 to
8.1.7...
Regards
Rafiq
Reply-To: [EMAIL PROTECTED]
To: Multiple
Rafiq,
Just a small questionr the rollback segment extents in the rollback
segment tablespace de-allocated when the database is shut down ??
In that case, does the fragmentation remain when the database is restarted
or r the blocks coalesced automatically ??
Regards,
Samir
Samir Sarkar
Or
Thanks a lot for ur help, Rafiq. I have acted as per ur recommendation
and asked the customer to try the delete job again.have not received
a feedback from them yet but sometimes they only revert back to me if they
have faced a problem again.if I do not hear anything by this evening,
I w
2002 4:53 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Rollback Segment Problem
>
>
> Jerry,
> Thanks for sharing script. We might have better systems as timing
> was never
> be a issue. I just tested my script on 2 systems and it ran between 34.5
> msecond
Jerry,
Thanks for sharing script. We might have better systems as timing was never
be a issue. I just tested my script on 2 systems and it ran between 34.5
mseconds to 4.65 seconds...and on the basis of it is results we coalesce all
such tablespaces. I prefer to keep pctincrease of tablespaces
Rafiq,
While your script provides a lot of good information, it sure is slow on my system. It
took 1:44 minutes while my script below took 420 mseconds. I was really surprised as
my script has a self-join. Then I checked out dba_free_space_coalesced. It sure is
complicated as it calls on two o
Is your tablespace fragmented as it is not finding contingous extent ..
TRy to coalesce your subject tablespace and try...
you can use following script to check whether coalesing is required or not..
If percent is < 100 then coalesce it..
select substr(tablespace_name,1,10)TS_NAME,total_extents
All,
The following is the pitiable scenario I am in and would really appreciate a
bit of help :
We were running a long running delete job which gave the following error :
Oracle8 Enterprise Edition Release
8.0.5.2.1 - Production
32 matches
Mail list logo
