Re: rman tablespace managment

There is no requirement for the catalog tablespace to be dictionary managed, but this is a classic example of the dangers of using Locally Managed tablespaces unwisely in ANY situation, not just RMAN.

The usual advice is that the catalog tablespace needs to be around (from memory) 50Mb or so. But if you create it locally managed with a uniform size of 5M, you'll get precisely 9 extents out of such a tablespace (not 10, because you have to allow for the 64Kb bitmap at the head of the tablespace).

The catalog has far more segments within it than that, though... (since I switched to 9i, which doesn't need a catalog, I haven't got one handy to check the numbers precisely I'm afraid), so obviously, when it tries to create the 10th segment, it will fail to find enough space to allocate its initial extent.

Have another go, using locally managed tablespace, but this time use a more sensible uniform size -say 64K. You should find it creates no problems.

Regards
HJR "Manuela Mueller" <520040906697-0001_at_t-online.de> wrote in message news:3BB9E222.267AC294_at_t-online.de...
> Dear all,
> RDBMS: Oracle EE 8.1.7, OS LINUX: RH 6.2
> in order to learn rman I set up a seperate recovery db, created a
> locally managed tablespace (uniform size 5M) for the recovery catalog.
> Created a user who owns the catalog schema granted him the necessary
> roles and unlimited quota on the tablespace that should contain the
> recovery catalog.
> All went fine until I tried to create the catalog in this tablespace.
>
> RMAN> create catalog tablespace 'RCVCAT';
>
> RMAN-06099: error occurred in source file: krmk.pc, line: 6600
> RMAN-06097: text of failing SQL statement: CREATE TABLE orl
> (
> dbinc_key NUMBER NOT NULL, -- database incarnation
> thread# NUMBER NOT NULL, -- thread number
> group# NUMBER NOT NULL, -- group number
> fname VARCHAR2(1024) NOT NULL, -- datafile name
> --CONSTRAINT orl_p PRIMARY KEY (dbinc_key, fname), -- key is too long
> CONSTRAINT orl_f1 FOREIGN KEY (dbinc_key, thread#)
> REFERENCES rt ON DELETE CASCADE
> )
> tablespace "RCVCAT"
>
> RMAN-06004: ORACLE error from recovery catalog database: ORA-01658:
> unable to create INITIAL extent for segment in tablespace RCVCAT
>
> I dropped the tablespace, created it as dictionary managed tablespace
> and created the catalog without any error messages.
> In the backup manual and backup & recovery handbook I found no hints,
> that the tablespace for the recovery catalog should be dictionary
> managed.
> Has anybody encountered the same feature or is it eventually OS-related?
> Any suggestions are welcome, ...have a nice day
> Manuela Mueller
Received on Tue Oct 02 2001 - 15:26:39 CDT