Re: [Q] Increasing size of tablespaces

From: Chas. Dye <ucdy_at_rvax.syntex.com>
Date: 22 Dec 1994 16:27:10 GMT
Message-ID: <3dc9cu$jmh_at_yoda.Syntex.Com>


You can:

  1. Drop the indexes in the index tablespace
  2. Alter the storage parameters on aforementioned tablespace
  3. Recreate the indexes.

Regards,
Chas. Dye
Charles.Dye_at_syntex.com

In article <3d9pf6$cn0_at_missun.cus.cul.ca>, dosadmin_at_glory.edm.isac.ca (DOS System Administrator) writes:
|>We are running an Oracle 7.0.15.4 database with about 10 million
|>records. It is heavily indexed to improve query performance.
|>
|>The data and indexes are stored in separate tablespaces. Recently
|>we started getting ORA-01547 errors (failed to allocate extent
|>size X in tablespace Y) for the tablespace holding the indexes.
|>The problem is that the tablespace was created with an initial
|>extent of 1M and next extent of 1M. This is too small, and the
|>tablespace has now reached the maximum number of extents allowed
|>under SunOS.
|>
|>Question: what is the quickest way to fix this problem? Doing
|>a full export, recreating the database, and then importing seems
|>like an option, but this would be *EXTREMELY* time consuming.
|>Is there a better way? What about dropping all the indexes
|>and primary keys, recreating the tablespace, and then re-indexing
|>everything? Any other ideas?
|>
|>--
|>Ken Bobey, ISA Corp. Internet: ken_at_edm.isac.ca
|>#835 10040-104 Street TEL: 403-420-8081 x8997 x5666
|>Edmonton, AB, Canada T5J 0Z2 FAX: 403-420-8037 x8026
|>
|>
Received on Thu Dec 22 1994 - 17:27:10 CET

Original text of this message