 | | | URGENT - Can you coalesce a RBS tablespace? | URGENT - Can you coalesce a RBS tablespace? 2005-09-06 - By Goulet, Dick
One thing that developers are very poor at is defining what a
transaction is. But pinning that down is one of the major things you
can do to eliminate this type of problem. Basically a transaction is a
logical unit of work that the application can recover from if it would
fail. I've seen applications that do a massive amount of work on one
table followed by a similarly massive amount of work on 10 more tables
and the developer calls the entire thing a transaction. And then they
wonder why they get rollback/undo errors!! Normally one or more of the
tables has a primary key that links the tables together. If possible
have them reorganize their job around working on one primary key entry &
calling that a transacti8on.
__ __
From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)] On Behalf Of Henslee, Jeff
Sent: Tuesday, September 06, 2005 2:40 PM
To: chiragdba@(protected)
Cc: Oracle-L Freelists
Subject: RE: URGENT - Can you coalesce a RBS tablespace?
I think things have slowed down a little bit. I am over the hump by
trying a number of suggestions from a number of you (and I thank you
all).
I have tried to shrink a number of the roll back segments - although I'm
not sure I was 100% successful - the segment size in OEM did not change
much at all. If I add the segments that were unusually large,
basically, they consume almost the entire datafile (1GB) -
I did try to kill a couple of older user connections that were very old
and stale.
I am also working with the developer and making sure that his code makes
better use of commits at the proper time (and more often). I think that
this is my best recourse. After discussions with a couple of users,
they appeared to be processing a rather large set of data in a big chunk
(rather than in smaller chunks). This processing is not "normally" how
it occurs (in big chunks that is) and therefore was not planed for when
the DB was originally created.
I did (against my original statement) add a small number of blocks to
the data file (200M) in order to get me over the hump. I am still trying
to chase down the "real" issue.
Thank you all so much for your suggestions and feedback.
I really appreciate all of the help I get from this list.
Thank you.
-- --Original Message-- --
From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)]On Behalf Of Chirag DBA
Sent: Tuesday, September 06, 2005 1:14 PM
To: Henslee, Jeff
Cc: Oracle-L Freelists
Subject: Re: URGENT - Can you coalesce a RBS tablespace?
so jeff
... does all this discussion has resolved yr problem?
U said it was URGENT and of course bouncing the DB is not a long
term answer.
Let us know if you r getting any error in trace files.
Regards - Chirag
On 9/6/05, Henslee, Jeff <jhenslee@(protected)> wrote:
We seem to be having troubles with some of our RBS
segments. We are unable to create new segments or extend existing ones.
This is an unusual pattern and we're trying to find a way to get people
back working again without having to add a datafile to the RBS area (if
at all possible) or restart the instance.
Options please?
Thank you.
Jeffrey C. Henslee (Chico)
Six Sigma Green Belt
Wausau Window and Wall Systems
(715) 846-3196
mailto:jhenslee@(protected)
--
http://www.freelists.org/webpage/oracle-l
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1505" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=198504418-06092005><FONT face=Arial
color=#0000ff size=2>One thing that developers are very poor at is defining
what
a transaction is. But pinning that down is one of the major things you
can
do to eliminate this type of problem. Basically a transaction is a
logical
unit of work that the application can recover from if it would fail. I've
seen applications that do a massive amount of work on one table followed by a
similarly massive amount of work on 10 more tables and the developer calls the
entire thing a transaction. And then they wonder why they get
rollback/undo errors!! Normally one or more of the tables has a primary
key that links the tables together. If possible have them reorganize
their
job around working on one primary key entry & calling that a
transacti8on.</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)] <B>On Behalf Of </B>Henslee,
Jeff<BR><B>Sent:</B> Tuesday, September 06, 2005 2:40 PM<BR><B>To:</B>
chiragdba@(protected)<BR><B>Cc:</B> Oracle-L Freelists<BR><B>Subject:</B> RE:
URGENT - Can you coalesce a RBS tablespace?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=199272818-06092005><FONT face=Georgia color=#0000ff>I think
things have slowed down a little bit. I am over the hump by trying a
number of suggestions from a number of you (and I thank you
all).</FONT></SPAN></DIV>
<DIV><SPAN class=199272818-06092005><FONT face=Georgia
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=199272818-06092005><FONT face=Georgia color=#0000ff>I have
tried to shrink a number of the roll back segments - although I'm not sure I
was
100% successful - the segment size in OEM did not change much at all. If
I
add the segments that were unusually large, basically, they consume almost the
entire datafile (1GB) - </FONT></SPAN></DIV>
<DIV><SPAN class=199272818-06092005><FONT face=Georgia
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=199272818-06092005><FONT face=Georgia color=#0000ff>I did try
to kill a couple of older user connections that were very old and stale.
</FONT></SPAN></DIV>
<DIV><SPAN class=199272818-06092005><FONT face=Georgia
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=199272818-06092005><FONT face=Georgia color=#0000ff>I am also
working with the developer and making sure that his code makes better use of
commits at the proper time (and more often). I think that this is my best
recourse. After discussions with a couple of users, they appeared to be
processing a rather large set of data in a big chunk (rather than in smaller
chunks). This processing is not "normally" how it occurs (in big chunks
that is) and therefore was not planed for when the DB was originally
created. </FONT></SPAN></DIV>
<DIV><SPAN class=199272818-06092005><FONT face=Georgia
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=199272818-06092005><FONT face=Georgia color=#0000ff>I did
(against my original statement) add a small number of blocks to the data file
(200M) in order to get me over the hump. I am still trying to chase down the
"real" issue. </FONT></SPAN></DIV>
<DIV><SPAN class=199272818-06092005><FONT face=Georgia
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=199272818-06092005><FONT face=Georgia color=#0000ff>Thank you
<U>all</U> so much for your suggestions and feedback.</FONT></SPAN></DIV>
<DIV><SPAN class=199272818-06092005><FONT face=Georgia
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=199272818-06092005><FONT face=Georgia color=#0000ff>I really
appreciate all of the help I get from this list.</FONT></SPAN></DIV>
<DIV><SPAN class=199272818-06092005><FONT face=Georgia
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=199272818-06092005><FONT face=Georgia color=#0000ff>Thank
you.</FONT></SPAN></DIV>
<BLOCKQUOTE>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-- --Original Message-- --<BR><B>From:</B>
oracle-l-bounce@(protected) [mailto:oracle-l-bounce@(protected)]<B>On
Behalf Of </B>Chirag DBA<BR><B>Sent:</B> Tuesday, September 06, 2005 1:14
PM<BR><B>To:</B> Henslee, Jeff<BR><B>Cc:</B> Oracle-L
Freelists<BR><B>Subject:</B> Re: URGENT - Can you coalesce a RBS
tablespace?<BR><BR></FONT></DIV>
<DIV>so jeff</DIV>
<DIV> </DIV>
<DIV>... does all this discussion has resolved yr problem?</DIV>
<DIV> </DIV>
<DIV>U said it was URGENT and of course bouncing the DB is not a long term
answer.</DIV>
<DIV> </DIV>
<DIV>Let us know if you r getting any error in trace files.</DIV>
<DIV> </DIV>
<DIV>Regards - Chirag <BR><BR> </DIV>
<DIV><SPAN class=gmail_quote>On 9/6/05, <B class=gmail_sendername>Henslee,
Jeff</B> <<A
href="mailto:jhenslee@(protected)">jhenslee@(protected)</A>>
wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px
solid">We
seem to be having troubles with some of our RBS segments. We are
unable to create new segments or extend existing ones. This is
an
unusual pattern and we're trying to find a way to get people back working
again without having to add a datafile to the RBS area (if at all possible)
or restart the instance. <BR><BR>Options please?<BR><BR>Thank
you.<BR><BR>Jeffrey C. Henslee (Chico)<BR>Six Sigma Green Belt<BR>Wausau
Window and Wall Systems<BR>(715) 846-3196<BR>mailto:<A
href="mailto:jhenslee@(protected)">jhenslee@(protected)
</A><BR><BR>--<BR><A
href="http://www.freelists.org/webpage/oracle-l">http://www.freelists.org
/webpage/oracle-l</A><BR></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>
|
|
|