Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: URGENT - Can you coalesce a RBS tablespace?

RE: URGENT - Can you coalesce a RBS tablespace?

From: Goulet, Dick <>
Date: Tue, 6 Sep 2005 14:49:53 -0400
Message-ID: <>

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.

[] On Behalf Of Henslee, Jeff
Sent: Tuesday, September 06, 2005 2:40 PM To:
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-----

[]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 <> 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 

Received on Tue Sep 06 2005 - 13:52:10 CDT

Original text of this message