Re: invalid status tablespace

From: Pete Sharman <psharman_at_us.oracle.com>
Date: Tue, 13 Apr 1999 08:57:18 -0700
Message-ID: <3713695E.367E87A1@us.oracle.com>

DId you drop the tablespaces first, or simply remove the datafiles? Another possibility - was there any referential integrity constraints across tablespaces?

As far as the rollback segments are concerned, a rough rule of thumb is create n/4 where n is the number of concurrent transactions. Sizing is dependent on the amount of data changed. The best way of checking this is to run the transaction load in a test environment and see how big the rollback segments grow. If that's not feasible, take a guess and monitor the growth in v$rollstat. In particular, look at the aveactive, hwmsize and rssize columns (+optsize if you've set OPTIMAL to some value).

HTH. Pete

nieuws net wrote:

> Hi everyone
>
> I've deleted 3 tablespaces a couple of weeks ago and removed the datafiles
> from disk, so far so good.
> When i yesterday did a
> SELECT
> TABLESPACE_NAME,STATUS
> FROM
> USER_TABLESPACES
> i saw the 3 deleted tablespaces with a status INVALID
> (the same query on dba_tablespaces did'nt show those tablespaces by the way)
> Anyone with a hint ?
>
> My second question is : Are there guidelines for sizing rollback segments ?
> How many and whats the size.
>
> Thanks
>
> gkor_at_rdw.nl

Regards

Pete

Peter Sharman                             Email: psharman_at_us.oracle.com
WISE Course Development Manager           Phone: +1.650.607.0109 (int'l)
Worldwide Internal Services Education            (650)607 0109 (local)

San Francisco

SQL> select standard_disclaimer, witty_remark 2 from company_requirements;

Opinions are mine and do not necessarily reflect those of Oracle Corporation

"Controlling application developers is like herding cats." Kevin Loney, ORACLE DBA Handbook
"Oh no it's not! It's much harder than that!" Bruce Pihlamae, long term ORACLE DBA

Received on Tue Apr 13 1999 - 10:57:18 CDT